writing-planslisted

# Writing Plans Write an implementation plan for an engineer with zero context for this codebase and questionable test taste. Decompose into bite-sized, independently verifiable tasks. DRY, YAGNI, TDD, frequent commits. Pairs with `/generate-prp` (research-driven blueprint) and `/writing-plans`. Save to `docs/superpowers/plans/YYYY-MM-DD-<feature>.md` (user preference overrides). Worktree, if isolated, comes from `using-git-worktrees` at execution time. Announce: "Using the writing-plans skill to create the implementation plan." ## Scope - One plan per independent subsystem — each must produce working, testable software alone. If the spec spans several, suggest splitting into separate plans. ## File structure (decide before tasks) - Map every file to create/modify and its single responsibility — this locks in decomposition. - One responsibility per file; prefer small focused files; files that change together live together (split by responsibility, not layer). - Follow established codebase patterns. Restructure a file only when it's grown unwieldy AND you're already modifying it. ## Task right-sizing - A task = the smallest unit that carries its own test cycle and is worth a fresh reviewer's gate. - Fold setup/config/scaffolding/docs into the task whose deliverable needs them. Split only where a reviewer could reject one task while approving its neighbor. - Each task ends with an independently testable deliverable. ## Step granularity Each step is one 2-5 min action