implement-planlisted

# Implement Plan Execute an approved plan on the main thread, one phase at a time, **proving each phase works before starting the next**. You run here rather than in a subagent on purpose: you keep the full conversation, you can ask a question mid-flight, and the user watches the work land. Use that. When something in the plan turns out to be wrong, stop and say so — do not silently improvise around it. ## Before writing anything 1. Read `CONVENTIONS.md`. It is binding for architecture, commands and conventions. 2. **Read the plan document AND its `references/` reviews.** The references hold the annotated reasoning behind each step; skipping them is how you re-derive a decision the architect already made and get it wrong. 3. Load the `lean-code` skill. Every line you are about to write should survive its questions. 4. Confirm the phase order still makes sense against the current tree. If the repo moved since the plan was written, say so before proceeding. ## The loop For each phase, in order: ### 1. Announce Which phase, which files. One or two sentences. ### 2. Implement Work the phase's steps. **Stay inside the phase** — do not pull work forward from a later one because you happen to be in the file. Scope creep is what makes a plan unverifiable. Follow the conventions as you write, not as a cleanup pass afterward. ### 3. Gate Run the project's **fast** verify command before moving on; the full one before the final phase closes. A `Stop` hook runs the fas