1. Habit
  2. Skills
  3. Writing Plans skill
Jesse Vincent · 281K installsPrime Radiant · Keyboardio · Request Tracker, Superpowers

Writing Plans skill
Runs by itself, every time a new spec is saved.

Every new spec gets a checked plan before coding.

Install the Writing Plans skill and make it a habit: follow https://gethabit.dev/skills/obra/writing-plans.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

281K installs303K starsMIT licenceSource on GitHub ↗

Writing Plans

by Jesse Vincent · 281K installs

The skill

Turns an idea into a step-by-step build plan.

Only when you ask.

Ship faster

Every new spec gets a checked plan before coding. Fewer mistakes, faster builds.

↻ Runs by itselfevery time a new spec is saved

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

new spec committed. Runs in GitHub Actions or Claude Code routine.

  • ↻ new spec committed
  • push touches a spec or design doc

02

It checks its work

self-review + your approval. If a check fails, it tries again.

  • ✓plan file exists in docs/superpowers/plans/
  • ✓plan starts with the required header
  • ✓every spec requirement maps to a task
  • ✓no step says TBD

03

It remembers

saved plans folder. The next run reads it first: earlier plans and the spec they implement.

docs/superpowers/plans/

One run, step by step.
Then it stops.

Stop ruleStops after one spec per run and one self-review fix pass.

  1. 01

    Check the scope

    If the spec covers several separate subsystems, suggest one plan for each.

  2. 02

    Map the files

    List which files the work creates or changes and what each one owns.

  3. 03

    Write the tasks

    Each task names its files, its interfaces, a failing test, the code step and a commit.

  4. 04

    Run self-review

    Check spec coverage, empty steps, type consistency, the Review Focus list and plan length.

  5. 05

    Save the plan

    Save it as docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md.

  6. 06

    Hand off

    Ask you to review and choose superpowers:subagent-driven-development or superpowers:executing-plans.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Writing Plans skill helps.

Use it when

  • ✓ you have a spec for a multi-step task
  • ✓ before any code is written
  • ✓ tasks go to subagents

Skip it when

  • – the change is one small edit
  • – there is no spec yet

Questions

Writing Plans skill, answered.

Does the loop start coding?

No. It stops at the plan and waits until you review it and choose how it runs.

Where do plans go?

By default into docs/superpowers/plans/ with the date and feature name. Your own location setting wins.

How long is a plan?

Short. The skill checks that a plan is not much longer than its spec and holds signatures and tests, not full code.

How do I install the Writing Plans skill?

Copy the prompt at the top into your agent. It installs the skill from obra/superpowers and sets up the habit. Or run npx skills add obra/superpowers --skill writing-plans.

Is the Writing Plans skill free?

Yes. It is published under MIT. Habit is free too.

Writing Plans. Now as a habit.

Install the Writing Plans skill and make it a habit: follow https://gethabit.dev/skills/obra/writing-plans.md

  • Free
  • No account
  • Undo in one line

All Jesse Vincent skills →More planning skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by Jesse Vincent, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.