Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
steering skill Trigger terms: steering, project memory, codebase analysis, auto-update context, generate steering, architecture patterns, tech stack analysis, project structure, analyze codebase, understand project Use when: User requests involve steering tasks.
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sprint but can extend to all tickets when needed. The skill uses the Jira CLI to retrieve ticket details, status, assignee, and descriptions.
Creates detailed implementation plans with atomic steps, model selection per step, dependency labels, and embedded TDD specifications
Ability to analyse, design, optimise, and improve systems that integrate people, processes, technology, and resources to meet defined performance, quality, cost, and safety requirements. Includes applying engineering, statistical, and systems methods to model workflows, identify inefficiencies, evaluate trade-offs, and implement improvements across operations and supply chains. Applies across manufacturing, services, logistics, healthcare, and infrastructure contexts and is independent of specific tools or industries, with human accountability retained for decisions, outcomes, and impacts.
Triages PR activity to identify what needs attention. Use when reviewing PR status, prioritizing work, checking for stale reviews, or when the user asks about PR health, what needs review, or what's blocking progress.
Draft outcome-oriented OKRs with leading indicators and initiatives tied to the product strategy.
Evaluates complexity (simple, medium, complex) based on estimated files/lines/time. Use after task classification.
기능 구현을 위한 테크스펙과 구현 계획 문서를 작성합니다. 스펙 주도 개발 워크플로우를 지원합니다.
Unterstützt dabei, aus vagen oder konkreten Vorhaben einen realistischen Projektplan mit Spezifikation, Task-Breakdown und passenden LLM-Prompts für Umsetzungsagenten zu entwickeln; verwenden, wenn Planung, Dokumentation und Prompt-Design für ein neues Vorhaben nötig sind.
Expert GitHub research including repository analysis, code search, contributor patterns, and project evaluation
Break down a spec section or milestone into actionable, session-sized tasks. Use when a milestone is too large, when starting implementation, when the user asks to break down work, or when refining task granularity.
Follow the team workflow expectations while working.
Store and retrieve long-term project context, architectural decisions, and learnings.
Split oversized task into smaller tasks with proper dependency management
Incident response documentation, timeline analysis, containment procedures, and IR reporting. Support the full incident lifecycle from detection to lessons learned. Use for security incidents, breach response, and IR planning.
Records a resolution for a human escalation.
Analyze current spec completion status and provide detailed progress report. Use when checking progress, identifying blockers, or planning what to work on next. More detailed than the /spec-flow:status command.
Use when executing implementation plans with independent tasks in the current session
Validate schedules against hard gates and score quality. Phase 3 of EROS pipeline. Invoked automatically after schedule generation completes.
Copilot agent that assists with systematic requirements review using Fagan Inspection and Perspective-Based Reading (PBR) techniques Trigger terms: requirements review, specification review, SRS review, Fagan inspection, perspective-based review, requirements validation, requirements verification, quality gate review, formal inspection, requirements checklist Use when: User requests involve requirements review, validation, or inspection tasks.
Полная реализация проекта по готовым спецификациям м первого раза(requirements.md, tasks.md, design.md). Использовать когда: нужно реализовать проект с нуля по спецификациям, выполнить все таски идеально. Скилл обеспечивает: идеальное выполнение с первого раза, работу по таскам, верификацию через субагентов, практическое тестирование на серверах, коммиты в git.
