spec-bugfix-plan

# /spec-bugfix-plan - Bugfix Planning Phase **Phase 1 (bugfix).** Investigates root cause, creates lean fix plan, gets approval. **Input:** Bug description (new) or plan path (continue unapproved) **Output:** Approved bugfix plan at `docs/plans/YYYY-MM-DD-<slug>.md` with `Type: Bugfix` **Next:** On approval → `Skill(skill='spec-implement', args='<plan-path>')` --- ## Iron Law ``` NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST ``` If you haven't completed Step 1.2, you cannot propose fixes. Symptom fixes are failure. --- ## Critical Constraints - **NEVER write code during planning** — planning and implementation are separate phases - **NEVER assume — verify by reading files.** Trace the bug to actual file:line. - **Right-size the plan** — small bugs get lean plans. Don't over-engineer. - **Plan file is source of truth** — survives across auto-compaction cycles - **ALWAYS use `AskUserQuestion` tool** for clarifications — never list numbered questions in plain text - **⛔ If `PILOT_PLAN_QUESTIONS_ENABLED` is `"false"` (from Step 0),** skip all `AskUserQuestion` calls (Steps 1.2.1, 1.2.5 escalation, 1.3 approach selection). Make reasonable default assumptions (including selecting the recommended fix approach) and document them in the plan. Continue autonomously. > **NOTE: During `/spec`, use the structured workflow below — not CC's native plan mode.** --- ## Step 0: Read Toggle Configuration **⛔ Run FIRST, before any other step.** Read all toggle env vars in a single...