Superpowers
Superpowers is a Claude Code and Codex plugin that gives the agent a library of process skills (brainstorming, writing plans, executing plans, debugging).
There are two pause points in the Superpowers workflow where PlanBridge fits well: design sections during brainstorming, and spec review. You can trigger PlanBridge manually or automatically.
Manual
Section titled “Manual”Trigger PlanBridge yourself with the planbridge-last or planbridge-open slash command. Use planbridge-last for the section the agent just wrote, and planbridge-open for saved spec files.
During brainstorming
Section titled “During brainstorming”The brainstorming skill walks the agent through clarifying questions and presents the design back to you in sections, in the terminal. A section can run hundreds of lines, which is hard to give targeted feedback on by typing back into the harness.
Pull the most recent section into PlanBridge:
/planbridge-last$planbridge-lastThe agent opens the section in PlanBridge for your review and markup, then revises based on the annotations you submit.
Reviewing the spec
Section titled “Reviewing the spec”Once you approve the design, the brainstorming skill writes a spec file to docs/superpowers/specs/ and pauses for review. A better spec means cleaner code generation.
/planbridge-open the spec you just wrote$planbridge-open the spec you just wroteSame loop: annotate inline, submit, and the agent revises the spec or moves on to writing the plan.
Automatic
Section titled “Automatic”If you want PlanBridge to fire at both pause points without you asking, append a snippet to your global agent instructions. Run the command for your harness:
echo '## Superpowers + PlanBridge
When using the Superpowers `brainstorming` skill, use PlanBridge at these pause points:
- When presenting design sections for approval (the "Present design" step, covering architecture, components, data flow, error handling, testing), run `/planbridge-last` instead of asking for text approval.- When writing a spec file under `docs/superpowers/specs/`, run `/planbridge-open the spec you just wrote` instead of asking me to review it as text.
Treat the returned annotations as my review feedback. Clarifying questions and approach proposals stay in the terminal.' >> ~/.claude/CLAUDE.mdecho '## Superpowers + PlanBridge
When using the Superpowers `brainstorming` skill, use PlanBridge at these pause points:
- When presenting design sections for approval (the "Present design" step, covering architecture, components, data flow, error handling, testing), run `$planbridge-last` instead of asking for text approval.- When writing a spec file under `docs/superpowers/specs/`, run `$planbridge-open the spec you just wrote` instead of asking me to review it as text.
Treat the returned annotations as my review feedback. Clarifying questions and approach proposals stay in the terminal.' >> ~/.codex/AGENTS.mdFuture Improvements
Section titled “Future Improvements”Do you love superpowers? We’d love to hear your feedback! We have a few ideas for how we might improve the PlanBridge ↔ Superpowers integration in the future.
Please check out the PlanBridge#143 issue and weigh in!