writing-planslisted

# Writing Plans ## Contents - [Overview](#overview) - [Scope Check](#scope-check) - [File Structure](#file-structure) - [Bite-Sized Task Units](#bite-sized-task-units) - [Plan Document Header](#plan-document-header) - [Task Structure](#task-structure) - [No Placeholders](#no-placeholders) - [Things to Remember](#things-to-remember) - [Self-Review](#self-review) - [Execution Handoff](#execution-handoff) ## Overview Write a comprehensive implementation plan assuming the engineer has no context on the codebase. Document everything they need to know. For each task: the files to touch, the code, the tests, the docs worth checking, and how to test. Give the whole plan as bite-sized tasks. DRY, YAGNI, TDD, and frequent commits. Assume the engineer is a capable developer but knows almost nothing about our toolset or problem domain. Assume they do not know good test design well. ○ Declare at the start: "I will write the implementation plan with the writing-plans skill." ○ Context: this skill must run in the dedicated worktree created by the brainstorming skill. ○ Plan storage location: `.tmp/implementation-plans/YYYY-MM-DD-<feature-name>.md` - If the user specifies a different location, that specification overrides the default. - The plan document is not canonical docs. It is a scratch/handoff artifact produced before execution. Move only the content you intend to promote into policy or contract into a separate `docs/policies/` document. ## Scope Check If the spec covers se