Superpowers Repository Assessment
📊 How to Read This Report
Maintainers: Focus on Repository Health and Strategic Assessment.
Contributors: Start with Top Opportunities (ranked by merge probability).
Founders: Read Maintainer Intelligence and Positioning Strategy.
Executive Summary
obra/superpowers is a flagship agentic skills framework with 128k stars and 10.5k forks, created by Jesse Vincent (@obra). It provides a complete software development workflow for coding agents across 6+ platforms (Claude Code, Cursor, Codex, OpenCode, GitHub Copilot CLI, Gemini CLI).
Active
Last Commit: Today
✅ Verdict: PURSUE with Careful Preparation
This is a Reach-tier project requiring A-game contributions that demonstrate deep system understanding. The 12% merge rate means Jesse is highly selective, but any merged PR is a major credibility signal.
Recommended first contribution: Issue #1049 (Platform-neutral worktree skill) — 45-90 minutes, 70-80% merge probability.
Repository Health
Overall Health Score: 🟡 5/7 (Yellow-Green)
| Dimension |
Score |
Evidence |
| Activity |
✅ Green |
Last commit: today (Apr 4, 2026) |
| Merge Rate |
🟡 Yellow |
12% (50/412) — very selective |
| Response Time |
✅ Green |
Same-day issue labeling |
| Issue Triage |
✅ Green |
New issues labeled within hours |
| Release Cadence |
✅ Green |
Active plugin updates |
| Contributor Diversity |
🟡 Yellow |
Jesse + community, single gatekeeper |
| Documentation |
❌ Red |
No CONTRIBUTING.md (issue #1031) |
Merge Rate Analysis: The Critical Metric
Of 412 closed PRs:
- 50 merged (12%) — Jesse's quality bar
- 362 closed without merge (88%) — Most contributions rejected
Interpretation: Jesse has a clear vision and rejects anything that doesn't fit the multi-platform architecture, shows signs of "agentic slop," ignores existing patterns, expands scope unnecessarily, or doesn't demonstrate system understanding.
Top Opportunities (Ranked)
Methodology: Opportunity Score = (Impact × Merge_Probability) / Effort
#1. Issue #1049: Platform-Neutral Worktree Skill ⭐⭐⭐
Score: 8.0 (Excellent)
Problem: The using-git-worktrees skill hardcodes a check for CLAUDE.md when deciding where worktrees should be created. This makes the skill feel Claude-specific even though Superpowers supports 6+ platforms.
Proposed Solution: Replace CLAUDE.md check with platform-neutral instruction file detection (check CLAUDE.md, AGENTS.md, or other platform-specific files in priority order).
| Impact: |
4/5 — Affects core workflow skill used by all platforms |
| Merge Probability: |
4/5 — Well-articulated issue, aligns with project goals |
| Effort: |
2/5 — Single skill file, ~20-50 lines, 45-90 minutes |
Why Jesse Will Merge This:
- Directly supports multi-platform architecture
- User did the analysis for us
- Clear, bounded scope
- Low risk of breaking existing behavior
Link: Issue #1049
#2. Issue #1045: Enable Gemini CLI Subagent Support ⭐⭐
Score: 6.0 (Good)
Problem: Documentation says Gemini CLI doesn't support subagents, but v0.36+ does. Need to copy subagent prompts to /agents folder and update docs.
| Impact: |
3/5 — Enables feature parity for Gemini users |
| Merge Probability: |
4/5 — User provided clear implementation path |
| Effort: |
2/5 — Copy 3 files, update docs, 30-60 minutes |
Link: Issue #1045
Maintainer Intelligence
Jesse Vincent (@obra)
Background:
- Founder, Prime Radiant (company behind Superpowers)
- Creator of Keyboardio mechanical keyboards
- Long-time open source contributor
- Technical blog: blog.fsck.com
Recent Activity:
- Published "Agentic slop PRs" blog post (Mar 31, 2026)
- Active daily commits on superpowers
- Responsive to issues (same-day labeling)
- Selective merging (12% rate)
What He Values:
- Multi-platform support — Skills must work across Claude/Cursor/Codex/etc.
- Workflow quality — TDD, systematic debugging, proper process
- Simplicity — YAGNI principle, avoid complexity
- Evidence-based changes — Don't claim, demonstrate
- Human oversight — Clear signs of human thought, not pure AI output
What He Rejects:
- Agentic slop — AI-generated PRs without review
- Scope creep — PRs that try to do too much
- Platform-specific hacks — Breaks multi-platform model
- Template violations — Ignoring PR process
- Lack of testing — No evidence the change works
Strategic Assessment
Should We Contribute to Superpowers?
YES, but with careful preparation.
This is a Reach-tier project:
- 128k stars = flagship open source
- Any merged PR is a major credibility signal
- But 12% merge rate requires A-game work
- Need to demonstrate system understanding, not just code output
What Makes a Successful Superpowers Contribution
- Understand the multi-platform vision — Every change must work (or explicitly opt-out) across platforms
- Show human thought — Jesse is allergic to agentic slop; PR must feel human-reviewed
- Start small — First contribution should be focused, clear, low-risk
- Provide evidence — Screenshots, test output, before/after comparisons
- Follow patterns — Read existing PRs that merged successfully
Recommended First Contribution
Issue #1049: Platform-Neutral Worktree Skill
Why this is the right first move:
- Aligns with Jesse's multi-platform vision
- Low risk — small change, backward compatible
- High visibility — affects core workflow
- Clear scope — well-defined problem and solution
- Shows understanding — demonstrates we read skills and understand architecture
- Not trivial — requires thought about platform conventions
Time investment: 45-90 minutes
Story value: "Fixed platform-specific hardcoding in Superpowers core workflow"
Merge probability: 70-80%
Recommendations
Immediate Actions
- ✅ Pursue #1049 — Platform-neutral worktree skill
- Read the skill file
- Understand platform conventions
- Propose minimal change
- Test across platforms if possible
- Submit with clear evidence
- 🔍 Research #1045 — Check for duplicate PRs on Gemini subagents
- 📖 Read Jesse's blog — Understand his philosophy (especially "Agentic slop PRs" post)
- 👀 Study merged PRs — Pattern recognition for successful contributions
Long-Term Positioning
Goal: Become a recognized Superpowers contributor
Path:
- 3-5 merged PRs in platform compatibility area
- Help with documentation as we learn the system
- Engage in issues to show system understanding
- Eventually propose a skill once we understand workflow deeply
Outcome:
- Credibility in agent tooling space
- Relationship with Jesse (potential collaboration)
- Deep knowledge of agent workflow systems
- Story: "Core contributor to Superpowers"