writing-plans: a Claude Code skill by Jesse Vincent
For developers who give Claude a spec and want a test-first build plan before any code is written. Skip it for small fixes you could make in one step.
- Score
- 84of 100
- Rank
- #32of 239
- Installs
- 3Kon skills.sh
- Security
- Clear 5 scanners
- Updated
- 2026
- Context
- ~24tokens always
Install
npx skills add https://github.com/obra/superpowers --skill writing-plans
Run it in your terminal. View the source
Using the Claude app rather than Claude Code? You can add a skill there too. How to add it in the app
What does writing-plans do?
writing-plans is a Claude skill that turns a spec into an implementation plan before code is touched, part of the Superpowers set. Claude maps which files will be created or changed, then splits the work into tasks that each end in something testable. Every task lists exact file paths, the interfaces it uses and produces, and checkbox steps: write the failing test, run it, implement the signature, run it again, commit. The plan opens with a header naming the goal, architecture, tech stack, global constraints and a review focus list. Claude checks coverage and type names, saves the plan under docs/superpowers/plans, and asks you to pick subagent-driven or native execution.
When should you use writing-plans?
Use it when
- You have a written spec for a feature with several parts
- Another agent or teammate will carry out the work
- You want test-first steps with exact commands
Skip it when
- The change is small enough to just make
- There is no spec or list of requirements yet
What it needs and what it can touch
You need
- The Superpowers executing-plans or subagent-driven-development skill to carry out the plan
What it can do
- Writes a plan file to docs/superpowers/plans in your project
From reading its instructions, not from running it.
Why it scores 84
Strongest on upkeep (100 of 100), weakest on trust (65).
Is writing-plans safe to install?
Every scanner that checked it passed it. Scanners often miss what other scanners catch, and a skill can change after a scan. Read its source before you install it.
| Scanner | Result | Date |
|---|---|---|
| Gen Agent Trust Hub | Passed | Sep 26, 2026 |
| Socket | Passed | Sep 26, 2026 |
| Snyk | Low risk | Sep 26, 2026 |
| Runlayer | Passed | Mar 12, 2026 |
| ZeroLeaks | Low risk | Apr 16, 2026 |
Details
- Installs
- 300,251
- Repository stars
- 315,837
- Last repository change
- Tokens always loaded
- about 24
- Tokens when used
- about 2,547
- License
- MIT
- Data confidence
- High
Did it do the job for you?
Alternatives to writing-plans
All skills for this job-
Get spec-driven-implementationspec-driven-implementation
For teams building large features who want PRODUCT.md and TECH.md specs checked in before and during coding.
-
Get write-product-spec
write-product-spec
For teams that want a behavior-first PRODUCT.md spec written before a feature is built.
-
Get Compound EngineeringCompound Engineering
For developers who want Claude to plan, build, review and ship work in fixed stages with saved plans.
-
Get Elephant Goldfish ModelElephant Goldfish Model
For engineers who write design docs before building and want fresh-eyed agent reviewers.
writing-plans