Amplifier Bundle Superpowers
https://github.com/obra/amplifier-bundle-superpowers- Category
- AI Agents
- Rank
- No. 1569Tools index
Previous survey · No. 1576 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- obra
- GitHub
- 71 stars
- Date
About
Superpowers workflow system for Amplifier — disciplined software development with TDD, systematic debugging, and structured planning. Ported from obra/superpowers.
What it does
It turns feature work into a staged conversation between specialized Amplifier agents and a human operator. Recipes gather requirements, produce a design, create an isolated worktree, write test-first tasks, execute them in batches or through fresh agents, verify results, and present branch completion choices. Approval gates pause costly or destructive transitions.
Why it's ranked here
The package offers unusually explicit control over agent-led development. Approval gates, isolated worktrees, test-first task structure, and separate specification and quality reviews address common failure modes directly. However, rigid rules, repeated manual approvals, moving upstream dependencies, and internal documentation inconsistencies make it better suited to deliberate feature work than quick maintenance.
What's good
The strongest feature is traceability. Design approval precedes planning, plans specify exact tests and commands, execution reports include verification output, and completion requires passing tests. The alternative agent workflow gives each task fresh context, then checks specification compliance before code quality. Failed tests trigger structured debugging before asking a human to decide.
Tradeoffs
This workflow carries substantial ceremony. Tiny changes still face strict test-first rules, planning, isolation, and checkpoints. Batch execution processes one batch per run, so longer plans require repeated commands. The finish flow can merge, push, or delete branches after approval. Some generated document instructions embed a fixed date, while bundled dependencies track mutable main branches.
How to use it well
Use it for feature work where requirements need refinement, implementation spans several tasks, and a human can review decisions between stages. Choose batch execution for controlled progress or fresh-agent execution for per-task isolation and two-stage review. It does not replace Amplifier itself, project-specific tests, architecture judgment, or repository hosting and review infrastructure.
Technical notes+
bundle.md is a thin Amplifier bundle that includes microsoft/amplifier-foundation, microsoft/amplifier-recipes, and behaviors/superpowers.yaml from Git main branches. behaviors/superpowers.yaml registers agents/superpowers-expert.md and includes context/instructions.md plus context/philosophy.md. Workflow definitions live under recipes/; recipes/brainstorming.yaml and recipes/writing-plans.yaml use mandatory approval stages, while recipes/executing-plans.yaml handles one batch per execution. recipes/subagent-development.yaml uses foreach task iteration and sequential specification and quality reviews. Several recipe prompts hard-code 2026-01-09 when naming generated planning documents.
Observed
- License
- MIT
- Interface
- Amplifier CLI bundle and declarative recipe workflows
- Packaging
- Loaded from a Git repository URL as a complete bundle or composable behavior
- Implementation surface
- Markdown context and agent definitions with YAML bundle, behavior, and recipe configuration
- Dependencies
- Includes Amplifier Foundation and Amplifier Recipes bundles
- Provider support
- Repository documentation states multi-provider support
- Structure
- Seven listed recipes, three reference skills, and one expert agent
Read from README.md, docs/ANALYSIS_SUMMARY.md, bundle.md, context/philosophy.md, context/instructions.md, behaviors/superpowers.yaml, recipes/brainstorming.yaml, recipes/finish-branch.yaml, recipes/writing-plans.yaml, agents/superpowers-expert.md, recipes/executing-plans.yaml, recipes/git-worktree-setup.yaml, recipes/subagent-development.yaml.
What it can do
Execute test-driven development workflow
Code requirements and specifications → Test cases and corresponding implementation code
Perform systematic debugging
Buggy code and error reports → Identified issues and debugging steps
Generate structured development plans
Project requirements and goals → Step-by-step development roadmap
Orchestrate disciplined software workflows
Development tasks and dependencies → Organized workflow execution sequence
Integrate with Amplifier system
Amplifier project data → Enhanced project capabilities and workflows
Tags
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.