writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Install
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/writing-plans ~/.claude/skills/writing-plansFrom README
Writing Plans Overview Write 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. 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.
More from this repo
systematic-debugging
Used when encountering any bug, test failure, or unexpected behavior, before proposing fixes
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying...
diagnosing-superpowers
Used when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans,...