draftlisted

# Draft - Context-Driven Development Draft is a methodology for structured software development: **Context → Spec & Plan → Implement → Verify** ## Red Flags - STOP if you're: - Jumping straight to implementation without reading existing Draft context - Suggesting `/draft:implement` before a track has an approved spec and plan - Not checking `draft/tracks.md` for existing active tracks before creating new ones - Skipping the recommended command and going freeform - Ignoring existing `.ai-context.md`, `product.md`, `tech-stack.md`, or `workflow.md` context **Read context first. Follow the workflow.** --- ## Workflow Commands ### Canonical Workflow ``` init → plan → implement → review → upload ↑ | └────────────┘ (review auto-invoked at phase boundaries) ``` ### Primary Workflow (Parent) Commands These 7 canonical parent commands coordinate and orchestrate the entire development lifecycle, automatically routing to specialist subcommands when appropriate. ### Routed Core Workflows (5 routers) The 5 router commands provide intent-based dispatch into the 20+ specialist commands. Use the router form for discoverability; leaf commands remain supported for compatibility. | Router | Scope | Dispatches To (examples) | |--------|-------|--------------------------| | `/draft:plan` | Planning & architecture | new-track, decompose, adr, tech-debt, change | | `/draft:ops` | Operations & lifecycle | deploy-checklist, incident-response, standu