> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plannotator.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Superpowers Planning Framework Profile

> A source-backed profile of Superpowers: brainstorming, reviewed design, repository plans, code-level task grain, TDD, execution, and verification.

Superpowers is a skills-based software-development method that moves from brainstorming to a reviewed design, a detailed repository plan, implementation, review, and branch completion. Its distinctive planning choice is code-level precision: tasks name files, interfaces, verification commands, expected output, and commits.

**Source stamp:** [`obra/superpowers` at `d884ae04`](https://github.com/obra/superpowers/tree/d884ae04edebef577e82ff7c4e143debd0bbec99), reviewed July 18, 2026. Repository license: MIT.

## Artifact tree

```text theme={null}
docs/superpowers/
  specs/
    YYYY-MM-DD-topic-design.md
  plans/
    YYYY-MM-DD-feature.md
```

The [brainstorming skill](https://github.com/obra/superpowers/blob/d884ae04edebef577e82ff7c4e143debd0bbec99/skills/brainstorming/SKILL.md) produces the design. The [writing-plans skill](https://github.com/obra/superpowers/blob/d884ae04edebef577e82ff7c4e143debd0bbec99/skills/writing-plans/SKILL.md) produces the implementation plan. The project publishes [real specs](https://github.com/obra/superpowers/tree/d884ae04edebef577e82ff7c4e143debd0bbec99/docs/superpowers/specs) and [real plans](https://github.com/obra/superpowers/tree/d884ae04edebef577e82ff7c4e143debd0bbec99/docs/superpowers/plans) in the same format.

## Workflow and task grain

1. Explore the problem through questions and alternative approaches.
2. Present the design in reviewable sections and obtain agreement.
3. Write an implementation plan that another engineer or agent can execute.
4. Execute with the method's testing and review skills.
5. Verify the result before completion and finish the branch deliberately.

A plan task includes exact files, consumed and produced interfaces, a failing test or verification setup, implementation instructions, a command with expected output, and a commit. The source targets short steps and rejects vague placeholders such as “add validation.”

## Review and handoff conventions

The main human checkpoint is design acceptance before implementation planning. The written plan is intended to survive into a separate execution session. Verification and review are separate procedures, not a sentence at the end of the plan.

## Inspect the same-case output

Inspect the [generated Superpowers design for reliable webhook delivery](https://github.com/plannotator/spec-planning-frameworks/tree/main/examples/superpowers/raw). The design completed, but two implementation-plan attempts stalled. The repository does not present the missing plan as complete.

## Choose Superpowers when

* the team wants one repeatable path from design through execution;
* an implementation-ready repository plan is valuable;
* exact file and verification instructions reduce ambiguity; and
* the team accepts a method that shapes more than the planning document.

Choose a different model when planning should stay in an issue tracker, when the problem is still too uncertain for code-level tasks, or when a broader product-delivery program is the real need.

See [Superpowers vs GSD](/compare/superpowers-vs-gsd) and the Plannotator-authored [AI coding plan template](/templates/ai-coding-plan).

*Reviewed July 19, 2026. Researched and maintained by the Plannotator documentation team. Superpowers is named for identification; Plannotator is not affiliated with or endorsed by its maintainers.*