plan-write

# plan-write ## Overview Write a comprehensive implementation plan assuming the executing engineer has zero context for the codebase and questionable taste. Document everything they need to know: which files to touch for each task, the actual code, tests, docs to check, exact commands. Break the work into bite-sized tasks of 2–5 minutes each. DRY. YAGNI. TDD. Frequent commits. Assume a skilled developer who knows almost nothing about the toolset, the problem domain, or good test design. **Announce at start:** "Writing the implementation plan." ## When to invoke Only after a spec has been written, self-reviewed, and explicitly approved by the user (the output of brainstorm-lean). Never before. ## Prerequisites - A spec file exists at `docs/specs/YYYY-MM-DD-<topic>-design.md` or a user-specified path. - The user has approved that spec in writing. - No implementation has started yet. If any prerequisite is missing, stop and redirect: either run brainstorm-lean first or ask the user to confirm the spec path. ## Save plans to `docs/plans/YYYY-MM-DD-<feature-name>.md` User preferences for plan location override this default. ## Compression policy The plan doc is **not compressed**. Downstream execution agents read this file verbatim and make edits based on what it says. Every path, every code block, every command must be exact. Compressing prose to save tokens here causes silent bugs later. The *announcement* to the user ("Writing the implementation plan.") is compre...