writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Install
With your agent
Install OMGSkills skill "obra/superpowers:writing-plans" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/writing-plans ~/.claude/skills/writing-plans
From 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
executing-plans
Used when executing an implementation plan in the current session as the implementer yourself — your human partner...
subagent-driven-development
Used when executing implementation plans with independent tasks in the current session
