writing-planslisted

> **Ported here, and some of what it names is not.** This skill comes from upstream, where it > sits beside sibling skills this port does not vendor. Any `superpowers:<name>` or > `elements-of-style:<name>` reference below that does not match a skill you actually have is > **not available here** — do not try to invoke it. Where one is named as a required step, do > the work it describes directly instead, or use the closest skill that is installed. Run > `ls ~/.claude/skills` to see what you have. # 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 at execution time. Under Conductor each workspace is already isolated. Otherwise, use `git worktree add` to set one up. **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 indep