writing-planslisted

<!-- Derived from superpowers (https://github.com/obra/superpowers) 6.2.0, Copyright (c) 2025 Jesse Vincent, MIT license. Modified. See vendor/superpowers/UPSTREAM.md and NOTICE. --> # Writing Plans ## Overview Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well. **Announce at start:** "I'm using the writing-plans skill to create the implementation plan." **Where to save the plan:** - **In plan mode**, write to the plan file the harness assigned for this session (in Claude Code, `~/.claude/plans/<slug>.md` — it is the only file you are allowed to edit while planning). Do NOT create a second copy elsewhere. - **Outside plan mode**, save to `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`. - (User preferences for plan location override both defaults.) Whichever path applies, state it explicitly when you hand off — execution starts by reading that file. ## Scope Check If 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 sepa