Writing Plans
Writing & Docsby obra
3/3 audits passMIT
Use when you have a spec or requirements for a multi-step task, before touching code
Writing Plans, published by obra in the superpowers repository under MIT, tells a coding agent how to turn a spec into an implementation plan before touching code. It assumes the engineer has zero context for the codebase, so the plan names exact files to create or modify, the code, the tests and how to run them. It starts with a scope check (split independent subsystems into separate plans), maps the file structure first, right-sizes tasks so each carries its own test cycle, and breaks each task into two-to-five-minute steps: write the failing test, run it, implement minimally, run again, commit.
Every plan opens with a fixed header: goal, architecture, tech stack, a link to the spec, global constraints copied verbatim, and a review focus listing likely failure modes the tests do not yet exercise. Each task declares the interfaces it consumes and produces. Plans are saved to docs/superpowers/plans, and the agent then offers subagent-driven or native execution. It is for developers using Claude Code and similar agents; it plans work rather than writing the implementation itself.
It is mainly useful to coding agents like Claude Code; BusinessMCP can import it as a playbook, but it adds little to business-data questions.
What you can do with it
- Turn a feature spec into bite-sized, test-first tasks
- Map files and interfaces before splitting work across subagents
- Record global constraints and review focus at the top of a plan
- Hand a plan to a fresh agent with no codebase context
Run it on your business data
Imported into BusinessMCP, Writing Plans becomes a playbook your AI business analyst applies to your company knowledge and connected documents.
Use Writing Plans in BusinessMCPInstall it in a coding agent
One command adds Writing Plans to your project.
npx skills add https://github.com/obra/superpowers --skill writing-plansHow we vetted it
- Source
- obra/superpowers at 5bf4e78
- Licence
- MIT
- Security audits (skills.sh)
- Gen Agent Trust Hub: Pass · Socket: Pass · Snyk: Pass
- Bundled scripts
- None, instructions only
Checked 2026-09-25 against its skills.sh listing. How we vet skills
Related skills
All skillsTest-Driven Development
Use when implementing any feature or bugfix, before writing implementation code
Brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Create PRD
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning.
Frequently asked questions
How do I install Writing Plans?
Run `npx skills add obra/superpowers --skill writing-plans` to add it to a Claude Code or other skills-compatible agent. You can also import it from the BusinessMCP dashboard, where it becomes a playbook in your workspace.
Where does it save plans?
By default to docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md, though user preferences for plan location override that.
How big is each step in a plan?
Each step is one action of roughly two to five minutes, such as writing the failing test, running it, implementing the minimal code, re-running tests and committing.
Run Writing Plans against your whole business
Free plan, no credit card.
Use Writing Plans in BusinessMCP