writing-plans

1# Writing Plans
2 
3## Overview
4 
5Write implementation plans for an engineer who has not seen this codebase or this spec. Assume they write idiomatic code in the project's language once they know the exact interface and the exact test, and that they will make a reasonable choice wherever the plan leaves one open. What they cannot know is what you decided: which files, which names and signatures, which values from the spec, which tests prove each task. Document those. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
6 
7**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."
8 
9**Context:** If working in an isolated worktree, it should have been created via the `superpowers:using-git-worktrees` skill at execution time.
10 
11**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
12- (User preferences for plan location override this default)
13 
14## Scope Check
15 
16If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
17 
18## File Structure
19 
20Before defining tasks, map out which files will be created or modified and what each one is responsible for. This is where decomposition decisions get locked in.
21…