new-track

# Create New Track Create a new track (feature, bug fix, or refactor) for Context-Driven Development. This is a **collaborative process** — be an active participant providing guidance, fact-checking, and expertise grounded in vetted sources. **Feature Description:** $ARGUMENTS ## Red Flags - STOP if you're: - Creating a track without reading existing Draft context (product.md, tech-stack.md, .ai-context.md) - Asking questions without contributing expertise or trade-off analysis - Rushing through intake without probing deeper with "why" - Generating spec/plan without user confirmation at checkpoints - Skipping risk identification - Not citing sources when giving architectural advice **Collaborative understanding, not speed.** --- ## Pre-Check 1. Verify Draft is initialized: ```bash ls draft/product.md draft/tech-stack.md draft/workflow.md draft/tracks.md 2>/dev/null ``` If missing, tell user: "Project not initialized. Run `/draft:init` first." 2. Check for `--quick` flag in `$ARGUMENTS`: - If present: **strip `--quick` from `$ARGUMENTS` now** (before Step 1) and store the cleaned text as the working description for all subsequent steps. Proceed to Step 1, then go directly to **Step 1.5: Quick Mode**. - Quick mode is for: hotfixes, tiny isolated changes, work scoped to 1-3 hours 3. Load full project context (these documents ARE the big picture — every track must be grounded in them): - Read `draft/product.md` — product vision, users, goals, constraints, guideli...