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.