Superpowers
ChatGPT pluginMake your agents better devs
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools531st of 537 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 528 | #6011 | 1,341places down | |
| 529 | #6012 | 1,341places down | |
| 530 | #6013 | 1,341places down | |
| 531 | #6014 | 1,341places down | |
| 532 | #6015 | 1,341places down | |
| 533 | #6017 | 1,341places down | |
| 534 | #6018 | 1,341places down |
Use Superpowers to guide agent work through brainstorming, implementation planning, test-driven development, systematic debugging, parallel execution, code review, and finish-the-branch workflows.
Example prompts
- “I've got an idea for something I'd like to build.”
- “Let's add a feature to this project.”
Skills
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
diagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Show all 15Show fewer
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
- Categories
- Made by
- Jesse Vincent · Website
- Sign-in
- On Install
- Capabilities
- Interactive, Read, Write
- Availability
- Available
- Version
- 6.4.2
- Keywords
- brainstorming, subagent-driven-development, skills, planning, tdd, debugging, code-review, workflow
- Created
- April 16, 2026
- More info