writing-planslisted

If a CEP context package exists for the feature this plan covers, load it before the Overview below — see `.cep-contracts/CONSUMING-CONTEXT-PACKAGE.md` for how to detect, extract, and apply it. Prefer its already-extracted evidence, Implementation Decisions, and flagged gaps over re-deriving them from scratch when mapping File Structure and Task N blocks; if `institutional_memory_hits` are present, resolve them per that contract before finalizing the plan. # 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." **Context:** If working in an isolated worktree, it should have been created via the `superpowers:using-git-worktrees` skill at execution time. **Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md` - (User preferences for plan location override this default) ## Scope Check If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If