writing-plans

A skill in obra/superpowers · 321,873 stars on GitHub

Use when you have a spec or requirements for a multi-step task, before touching code

Security grade of this SKILL.md: SAFE · how we grade

How to install writing-plans

npx skills add obra/superpowers --skill writing-plans -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

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. Save plans to: docs/superpowers/plans/YYYY-MM-DD- .md (User preferences for plan location override this default).

Other skills in obra/superpowers

  • brainstorming You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
  • diagnosing-superpowers Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
  • dispatching-parallel-agents Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  • executing-plans Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, o…
  • finishing-a-development-branch Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
  • receiving-code-review Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
  • requesting-code-review Use when completing tasks, implementing major features, or before merging to verify work meets requirements
  • subagent-driven-development Use when executing implementation plans with independent tasks in the current session
  • systematic-debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  • test-driven-development Use when implementing any feature or bugfix, before writing implementation code
  • using-git-worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
  • using-superpowers Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
  • verification-before-completion Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and…
  • writing-skills Use when creating new skills, editing existing skills, or verifying skills work before deployment