writing-planslisted

# Writing Plans ## Overview Create implementation plans for an engineer with zero codebase context. Each plan includes: - Exact file paths for every operation - Complete code (not "add validation here") - Test-first approach with verification commands - Bite-sized steps (2-5 min each) Principles: DRY, YAGNI, TDD, frequent commits. **Announce at start:** "I'm using the `writing-plans` skill to create the implementation plan." **Context:** Run in dedicated worktree. If none exists, use `using-git-worktrees` skill first. **Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md` ## Before Writing 1. Read spec/requirements completely 2. Explore project structure (`view .`) 3. Identify tech stack (package.json, pyproject.toml, etc.) 4. Note existing patterns in similar files 5. Check docs/ for existing conventions ## Bite-Sized Task Granularity Each step is one action (2-5 minutes), independently verifiable: - "Write the failing test" — step - "Run it to confirm failure" — step - "Implement minimal code to pass" — step - "Run tests to confirm pass" — step - "Commit" — step ## Plan Document Header Every plan MUST start with this header: ~~~markdown # [Feature Name] Implementation Plan **Goal:** [One sentence describing what this builds] **Architecture:** [2-3 sentences about approach] **Tech Stack:** [Key technologies/libraries] --- ~~~ ## Task Structure ~~~markdown ### Task N: [Component Name] **Files:** - Create: `exact/path/to/file.py` - Modify: `exact/pa