deep-planlisted

# Deep Plan Audit-grade planning: **evidence first, design later, never guess.** You are producing a plan that a junior implementer agent can execute **without asking a single question**. That is the bar. Everything below exists to reach it. ## The Prime Directive > **No claim without evidence. No design before research.** Every statement in your plan is one of: | Tag | Meaning | Required proof | |-----|---------|----------------| | `VERIFIED` | You read it yourself, this session | `file:line`, vendor path, or URL + version | | `UNVERIFIED` | You could not confirm it | Explicit label + what would confirm it | | `CORRECTED` | You previously believed it and were wrong | The old belief AND the new evidence | If you cannot cite it, you cannot claim it. Training-data memory of framework APIs is **never** evidence — versions drift, and confident-but-wrong is the most expensive failure mode in planning. ## Before you start 1. Read [references/protocol.md](references/protocol.md) in full — the phase protocol is mandatory and executed in order. 2. Switch to **Plan mode** if the tool supports it. Do not edit project files; the only file you write is the plan document. 3. Expect high token/time cost. That is the price of a plan an implementer can execute without guessing. **Preflight:** if the project root is not a git repository, git-based research (trajectory, recent changes) cannot run — note `UNVERIFIED: no git history` in your Findings and rely on file timestamps