메뉴
Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
Performs an exhaustive 14-dimension bug hunt across the codebase using Draft context (architecture, tech-stack, product) for false-positive elimination. Generates a severity-ranked report with code evidence, data flow traces, and suggested fixes. Optionally writes regression tests. Use when the user asks to find bugs, audit code for defects, scan for vulnerabilities, or says 'hunt bugs', 'find bugs', or 'code audit'.
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.
Structured debugging session. Reproduce, isolate, diagnose, and fix bugs using systematic investigation. Invoked by /draft:new-track for bug tracks or directly for ad-hoc debugging.
Decompose project or track into modules with dependency mapping. Project scope updates architecture.md and derives .ai-context.md. Track scope generates hld.md (always) and lld.md (when --lld or High-complexity module triggers it) — design-mandated artifacts that drive implement, deploy-checklist, and upload sign-off.
Single-module production readiness audit (ACID, resilience, observability). Use to audit one service/module end-to-end — NOT for diff/PR review (use review / quick-review) or bug-finding sweeps (use bughunt).
| name | plan |
| description | Primary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes. |
/draft:plan is the consolidated entry point for all planning and upfront architecture work in the Context-Driven Development lifecycle.
The router parses intent from natural language and dispatches to the correct leaf skill. Ambiguous requests surface a short menu of options.
| User Intent Keywords | Dispatches To | Purpose |
|---|---|---|
| new feature, new track, start X, add Y, plan a refactor, fix the Z bug | /draft:new-track | Collaborative spec + plan creation for track |
| decompose, break into modules, dependency map | /draft:decompose | Module decomposition + graph |
| adr, architecture decision, record decision, design decision | /draft:adr | ADR authoring and evaluation |
| tech debt, technical debt, catalog debt, debt analysis | /draft:tech-debt | 6-dimension debt scan + prioritization |
| change, scope changed, requirements changed, update spec, mid-track pivot | /draft:change | Structured change impact & plan update |
User: "start a new feature for user profile editing"
→ dispatches to /draft:new-track "user profile editing"
User: "decompose the payment module"
→ dispatches to /draft:decompose "payment module"
User: "document our decision to use event sourcing"
→ dispatches to /draft:adr "Use event sourcing for order processing"
User: "find and prioritize our technical debt"
→ dispatches to /draft:tech-debt
User: "the requirements changed, we need to support multi-tenancy now"
→ dispatches to /draft:change "add multi-tenancy support"
/draft:plan augments but does not replace the core /draft:new-track and /draft:implement flow. Many planning activities are launched via /draft:plan for discoverability, then flow into the primary track lifecycle.
Direct leaf commands remain available during the transition period (see MIGRATION).
All planning dispatches should result in updated draft/tracks/<id>/spec.md or plan.md (or new ADR/debt artifacts) with proper metadata headers and citations back to product/tech-stack context.
