change

# Course Correction You are handling a mid-track requirement change using Draft's Context-Driven Development methodology. ## Red Flags - STOP if you're: - Applying changes to spec.md or plan.md without showing the user what will change first - Invalidating `[x]` completed tasks without flagging them explicitly - Proceeding past the CHECKPOINT without user confirmation - Editing files when the user said "no" or "edit" **Show impact before applying. Always confirm.** --- ## Step 0: Verify Draft Context ```bash ls draft/tracks.md 2>/dev/null ``` If `draft/` does not exist: **STOP** — "No Draft context found. Run `/draft:init` first." --- ## Step 1: Parse Arguments Extract from `$ARGUMENTS`: - **Change description** — free text describing what needs to change (required) - **Track specifier** — optional `track <id>` prefix to target a specific track ### Default Behavior If no `track <id>` specified: - Auto-detect the active `[~]` In Progress track from `draft/tracks.md` - If no `[~]` track, find the first `[ ]` Pending track - Display: `Auto-detected track: <id> - <name>` before proceeding If no change description provided: - Error: "Usage: `/draft:change <description>` or `/draft:change track <id> <description>`" --- ## Step 2: Load Context 1. Read `draft/tracks/<id>/spec.md` — extract requirements and acceptance criteria 2. Read `draft/tracks/<id>/plan.md` — extract all tasks with their current status (`[ ]`, `[~]`, `[x]`, `[!]`) 3. Read `draft/tracks/<id>/meta...