plan-mode

# Plan Mode Prevent premature implementation. **Understand → plan → get approval → implement → validate.** Do not skip the gate just because a change looks small. The full protocol — investigation steps, issue classification, the question and plan templates, validation, and special cases — lives in [`PROTOCOL.md`](PROTOCOL.md). **Read it before planning or implementing.** ## Default behavior 1. Investigate project context (read-only). 2. Analyze the task: goal, current vs desired behavior, acceptance criteria, scope, edge cases. 3. Classify open issues as **ambiguity / contradiction / blocker / risk / assumption**. 4. Ask the smallest set of focused questions that unblocks planning. 5. Produce a consistent, evidence-based, step-by-step plan. 6. Wait for explicit approval. 7. Implement only the approved plan. 8. Validate, then report what was and was not checked. ## The gate (core rule) During Plan Mode, **do not mutate the project**: no editing files, scaffolding, patches, package installs, lockfile updates, migrations, deploys, destructive scripts, or "trying an implementation" to learn the code. **Allowed:** read files, search the repo, inspect structure, review tests / docs / configs / API contracts / schemas / migrations, run read-only or non-mutating diagnostic commands, and consult external docs when project context is insufficient. If a tool or command might mutate state, ask first or avoid it. ## Surfacing blockers Surface ambiguities, contradictions, and bl...