sdd-orchestrator
Use when the user is starting a project or wants to catch up on project progress - scans the specs/ folder, surfaces current status, proposes the next SDD phase, and routes to the appropriate workflow after confirmation.
generate-spec
Speckit ์ํฌํ๋ก์ฐ ํตํฉ ์คํ (specify โ plan โ tasks โ issues). Epic์์ Task Issue ์์ฑ๊น์ง ์์คํฑ ์ฒ๋ฆฌ. Use when (1) Epic ์์ฑ ํ Task ๋ถํด, (2) spec ๋ฌธ์ ์์ฑ, (3) Task Issue ์์ฑ.
issue-creator
ใฟในใฏใ็ดฐใใๅไฝใซๅๅฒใใฆ GitHub Issue ใไฝๆใใใใIssue ไฝๆใใIssue ใไฝใฃใฆใใใฟในใฏใ Issue ใซใใIssue ่ฟฝๅ ใใใใฑใใไฝๆใใIssue ใๅใใใใฟในใฏใๅๅฒใใฆ Issueใใชใฉใง่ตทๅใๅฎ่ฃ ๅฏ่ฝใช็ฒๅบฆใซใฟในใฏใๅๅฒใใฆ่คๆฐ Issue ใ็ๆใ
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with Shannon quantitative analysis, exact file paths, complete code examples, validation gates, and MCP requirements assuming engineer has minimal domain knowledge
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
alignment-workflow
Workflow formal para coleta de consenso em decisรตes organizacionais (ODRs). Gerencia ciclo de vida de ODRs desde criaรงรฃo atรฉ aprovaรงรฃo. Use quando: coletar inputs, rastrear aprovaรงรตes, escalar decisรตes.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
routing-map
SEMO ๋ผ์ฐํ ๊ตฌ์กฐ ์๊ฐํ. Use when (1) /SEMO:routing-map ์ปค๋งจ๋, (2) "๋ผ์ฐํ ๊ตฌ์กฐ", "SEMO ๊ตฌ์กฐ", "์ค์น๋ ํจํค์ง" ํค์๋, (3) Agent/Skill ์ ์ฒด ๋ชฉ๋ก ํ์ธ ์์ฒญ.
stakeholder-communication
Stakeholder management, executive communication, and organizational alignment for product leaders.
sitrep-reporting
Military-style SITuation REPort protocol for multi-agent coordination. Enforces structured status reporting with ๐ข๐ก๐ด codes, quantitative progress (0-100%), blockers, dependencies, ETAs, and authorization codes for secure handoffs. Prevents communication failures, lost context, and delayed blocker reporting. Use when: coordinating multiple agents, wave execution, reporting progress, requesting status updates, handing off deliverables.
jira-transitions
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
zeigarnik-effect
Las tareas incompletas se recuerdan mejor que las completadas. Use cuando diseรฑe progress indicators, onboarding, gamificaciรณn, o flujos que mantienen engagement.
implement-plan
Implement technical plans from thoughts/shared/plans with verification
tasks-planning
Use during Phase 4 of spec creation to break specification into organized task groups with dependencies - analyzes requirements to determine natural groupings, presents structure for validation, and creates detailed actionable tasks
issue-orchestrator
Orquesta el workflow de completado de issues en Linear, usando subagentes para mรบltiples issues, creando PRs cuando hay Git y moviendo estados. Usar cuando el usuario pide completar una o varias issues, coordinar subagentes o consolidar resultados.
technical-spike
Conduct objective-driven investigation to reduce uncertainty. Use when there's an unknown blocking estimation or implementation, when technical-pm identifies uncertainty, or when someone says "we need to investigate first".
kano-agent-backlog-skill
Local-first, multi-product backlog management with agent collaboration discipline.
agile-retrospective
When facilitating sprint retrospectives or team improvement sessions.
file-todos
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
daily-standups
Master daily standup facilitation with focus, time management, and effective patterns for team synchronization and impediment identification.
prioritization-framework
Apply RICE, ICE, or MoSCoW scoring to prioritize features. Use when deciding what to build first, during backlog grooming, or when product-manager needs to rank items.