phase-04-development-planning
Create work breakdown structure, resource planning, risk management, quality/testing planning, security/compliance planning, DevOps/CI/CD planning, and Sprint 0 setup.
Create work breakdown structure, resource planning, risk management, quality/testing planning, security/compliance planning, DevOps/CI/CD planning, and Sprint 0 setup.
In scaling companies, once you master a role you must hand it off and move to a bigger, messier challenge. Holding on buries you; giving away allows you to tackle bigger challenges.
Complete strategic problem-solving methodology from "Cracked It!" by Garrette, Phelps & Sibony. Use when users need to solve complex ill-defined business problems, structure and analyze strategic issues, develop and validate solutions, or present recommendations persuasively. Covers the complete 4S Method (State, Structure, Solve, Sell) from problem definition through solution delivery. Use for strategy consulting, business analysis, decision-making, and solving wicked problems that resist simple frameworks.
Generate comprehensive lab member rosters in both markdown and CSV formats. Analyzes member profiles, git history, and alumni information to create detailed rosters with role transitions, team assignments, and career tracking. Use when user mentions roster, team list, lab members, or updating member information.
Use for implementation plans - dispatches fresh subagent per task with quality scoring (0.00-1.00), code review gates, Serena pattern learning, and MCP tracking
ใฟในใฏไพ้ ผๆใฎ็่งฃ็ขบ่ชใทในใใ ๏ผ5W1H๏ผใplaybook ไฝๆๅใซใฆใผใถใผใฎๆๅณใ็ขบ่ชใใใชในใฏๅๆใจไธๆ็นใฎๆดใๅบใใ่กใใpm SubAgent ใใๅผใณๅบใใใใ
Expert Go developer specializing in idiomatic patterns, concurrency, error handling, and clean package design. This skill should be used PROACTIVELY when working on any Go code - implementing features, designing APIs, debugging issues, or reviewing code quality. Use unless a more specific subagent role applies.
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
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.
Speckit ์ํฌํ๋ก์ฐ ํตํฉ ์คํ (specify โ plan โ tasks โ issues). Epic์์ Task Issue ์์ฑ๊น์ง ์์คํฑ ์ฒ๋ฆฌ. Use when (1) Epic ์์ฑ ํ Task ๋ถํด, (2) spec ๋ฌธ์ ์์ฑ, (3) Task Issue ์์ฑ.
ใฟในใฏใ็ดฐใใๅไฝใซๅๅฒใใฆ GitHub Issue ใไฝๆใใใใIssue ไฝๆใใIssue ใไฝใฃใฆใใใฟในใฏใ Issue ใซใใIssue ่ฟฝๅ ใใใใฑใใไฝๆใใIssue ใๅใใใใฟในใฏใๅๅฒใใฆ Issueใใชใฉใง่ตทๅใๅฎ่ฃ ๅฏ่ฝใช็ฒๅบฆใซใฟในใฏใๅๅฒใใฆ่คๆฐ Issue ใ็ๆใ
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
SEMO ๋ผ์ฐํ ๊ตฌ์กฐ ์๊ฐํ. Use when (1) /SEMO:routing-map ์ปค๋งจ๋, (2) "๋ผ์ฐํ ๊ตฌ์กฐ", "SEMO ๊ตฌ์กฐ", "์ค์น๋ ํจํค์ง" ํค์๋, (3) Agent/Skill ์ ์ฒด ๋ชฉ๋ก ํ์ธ ์์ฒญ.
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.
Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting resolutions.
Las tareas incompletas se recuerdan mejor que las completadas. Use cuando diseรฑe progress indicators, onboarding, gamificaciรณn, o flujos que mantienen engagement.
Implement technical plans from thoughts/shared/plans with verification
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
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.