Skip to main content
Choose Superpowers when you want a defined path from reviewed design to a detailed, code-level implementation plan and execution. Choose GSD Core when the larger problem is carrying project, milestone, phase, execution, verification, and handoff state across many sessions. Sources: obra/superpowers at d884ae04 and open-gsd/gsd-core at 50efae13, reviewed July 18, 2026. Both repositories use MIT licenses.

​
The practical difference

​
Choose Superpowers when

  • one feature or change is ready for design refinement;
  • the team wants implementation steps precise enough for a separate agent session;
  • test-first execution and verification are part of the desired method; and
  • repository plans should name exact code boundaries.
The official writing-plans skill shows the expected task precision.

​
Choose GSD Core when

  • work spans multiple phases, milestones, or context windows;
  • research, decisions, current state, execution summaries, verification, and UAT all need durable files;
  • the next session must be able to resume from a documented frontier; and
  • the team will actively remove or update stale state.
The official planning-artifacts reference defines that state tree.

​
Inspect both same-case outputs

​
Can you combine them?

A team could use GSD to organize a milestone and use a detailed repository plan for one phase. That combination is an inference, not an official lifecycle published by either source. If you combine them, name which artifact controls current state and avoid duplicating the same plan in two places. For a neutral starting point, use the AI coding plan template. Read the full Superpowers and GSD Core profiles before adopting either method. Reviewed July 19, 2026. Researched and maintained by the Plannotator documentation team. The compared projects are not affiliated with or endorsed by Plannotator.
Last modified on July 20, 2026