메뉴
Primary router for authoring and documentation workflows. Analyzes intent and dispatches primarily to documentation (technical docs, readme, runbook, api, onboarding). Use when the user needs to generate or update project documentation.
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 | docs |
| description | Primary router for authoring and documentation workflows. Analyzes intent and dispatches primarily to documentation (technical docs, readme, runbook, api, onboarding). Use when the user needs to generate or update project documentation. |
/draft:docs provides a single namespace for all documentation generation and maintenance tasks.
Currently focused on the documentation specialist. Future expansion may include additional authoring helpers under the same router.
| User Intent Keywords | Dispatches To | Purpose |
|---|---|---|
| write docs, documentation, readme, runbook, api docs, onboarding guide, generate docs | /draft:documentation | Technical documentation authoring (readme, runbook, api, onboarding) |
User: "write a README for the new service"
→ dispatches to /draft:documentation readme
User: "generate an API reference and runbook for the billing module"
→ dispatches to /draft:documentation api runbook
User: "create onboarding guide for new engineers"
→ dispatches to /draft:documentation onboarding
The documentation command reads heavily from draft/architecture.md, draft/.ai-context.md, draft/product.md, and draft/tech-stack.md (plus graph artifacts when present).
Prefer /draft:docs going forward for all authoring requests. The legacy direct form remains for compatibility (see migration guidance).
