Stats
Actions
Tags
From draft
Dispatches planning intents to specialized skills for features, decomposition, ADRs, tech debt, and scope changes. Use as the entry point for structured planning workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/draft:planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`/draft:plan` is the consolidated entry point for all planning and upfront architecture work in the Context-Driven Development lifecycle.
/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.
npx claudepluginhub drafthq/draft --plugin draftCreates specs and phased file-level implementation plans for features, bugs, refactors by researching codebase with search, graph queries, and context files.
Starts a new feature, bug fix, or refactor track with collaborative intake, structured questions, and progressive refinement before generating spec.md and plan.md.
Analyzes feature requests, maintains PRDs, and decomposes into tracks with work breakdowns and execution order. For new feature planning, architecture changes, requirements analysis, or plan adjustments.