Skip to content
Coding

Writing Plans

Convert an agreed specification into implementation tasks with exact files, interfaces, and checks.

Install with Skills CLI
npx skills add obra/superpowers --skill writing-plans

What it does

A broad feature description leaves an implementer to guess at interfaces and completion criteria. This skill turns an existing specification into a plan that another developer or agent can follow without reconstructing all earlier decisions.

What changes after install

  • Maps file responsibilities and shared interfaces before defining tasks.
  • Breaks work into independently testable deliverables.
  • Specifies commands and expected outcomes that demonstrate completion.

Install

Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.

Install with Skills CLI
npx skills add obra/superpowers --skill writing-plans

Before using Writing Plans

  • Start with an agreed design or specification and access to the codebase, so the plan can identify real file paths and verification commands.

Read the reviewed setup instructions for the selected workflow.

When to use it

  • Planning a multi-file change after the design is settled.
  • Preparing a handoff to an implementer who has not seen the original discussion.

When not to use it

  • Replacing missing product requirements with an elaborate implementation checklist.

Begin with an agreed behavior

For a password-reset feature, a useful input includes the intended user flow, token lifetime, failure messages, existing authentication architecture, and any constraints on email delivery. Writing Plans should translate those decisions into implementation work. It should not silently invent them because the original request was brief.

The source asks the planner to identify which files will change, what each file is responsible for, and the exact interfaces between tasks. This matters when one task produces a function or data structure that a later task consumes. A good plan makes that dependency explicit so a new implementer does not have to guess at names or types.

Review the plan as a handoff

Each task should produce something that can be checked on its own. Look for concrete tests, commands, and expected outcomes. “Add validation” is less useful than specifying which input should be rejected and what the caller should observe. The upstream workflow favors a test-first sequence and keeps project-wide constraints visible throughout the plan.

The plan is a repository document, not a substitute for reading the current code. If the repository changes substantially before execution, verify that the paths and assumptions still apply.

Choose the companion deliberately

Brainstorming is useful while the intended behavior is still uncertain. Once the task sequence and acceptance checks are agreed, hand the written plan and its specification to Executing Plans. These are separate skills within the larger collection, and references between them may require installing the companions. SkillDex reviewed the source but did not execute a planned feature with this skill.

FAQ

Should I use this before deciding what to build?
Resolve the important product and design decisions first. This skill expects a specification or clear requirements.
Does it run the implementation?
No. It creates the plan; the Superpowers collection provides separate execution workflows.