codex-planlisted

# Codex Plan (staged task resolver) ## Quick Start `/codex-plan <task>` — produce a staged plan, show it to the user for approval, then execute it stage by stage using `/codex-check` and `/codex-debate` at the tiers the plan assigns. The plan is the deliverable of the first step. Never start implementing before the user has seen and approved it. **No pre-interview.** Steps 1–6 are autonomous document work — do them without asking the user anything. Questions that come up while drafting go INTO the plan as marked decision points and are asked together with the plan presentation: one consolidated approval round, not a conversation before the work starts. ## Procedure ### 1. Classify the ground List explicitly which parts of the task ride **proven rails** (tools, templates, and patterns that already passed a review gate in this project) and which parts are **new ground** (anything an existing template or gated tool does not cover). This classification drives everything below. ### 2. Gather lessons before writing the plan Search, in this order: - project docs: manual chapters, decision log, declared-divergence registry, prior plan documents of the same kind; - final reports of previous `/codex-debate` runs — every finding that was FIXED there is a lesson that can recur; - project memory files, if present. Convert each relevant lesson into a **hard requirement** in the plan, phrased as a constraint with a concrete check, not as advice. ("Every appearance anchor must be