superpowers vs gstack: which Claude Code skill framework?
Both are A-tier. obra/superpowers (83/100) wins on trigger design and universal process skills that fire automatically. garrytan/gstack (80/100) wins on workflow breadth: ship, QA, deploy, and multi-perspective review pipelines. Pick superpowers for discipline, gstack for coverage, or run both. Scored 2026-07-07, methodology v1.0.
Side-by-side scorecard
| Dimension | superpowers | gstack |
|---|---|---|
| Reliability | 84 | 80 |
| Skill Leverage | 90 | 86 |
| Documentation | 82 | 78 |
| Maintenance | 92 | 88 |
| Safety / Governance | 74 | 72 |
| Evaluation Readiness | 66 | 70 |
| Composability | 84 | 76 |
| Adoption (capped) | 92 | 88 |
| Overall | 83 · A-tier | 80 · A-tier |
Choose superpowers if
- You want process guarantees on every task without remembering to invoke anything.
- Your failure mode is agents declaring false success or skipping verification.
- You value trigger precision and boundary discipline as first-class craft.
Choose gstack if
- You want an opinionated pipeline from plan review to landed PR.
- You work solo and want the review structure a team would provide.
- Browser-based QA loops matter to your product surface.
The entries
A process-first skill framework for Claude Code: brainstorming, test-driven development, systematic debugging, and verification skills that…
An opinionated 23-skill suite that staffs a solo developer's agent with the roles a startup would hire: CEO review, design review,…
Frequently asked questions
Should I use superpowers or gstack?
Use superpowers if you want always-on process discipline (TDD, debugging, verification) that auto-triggers across every task. Use gstack if you want explicit, operator-driven workflow coverage from plan review through ship and QA. Many teams run both; they overlap less than their categories suggest.
Can superpowers and gstack be used together?
Yes. superpowers skills auto-trigger on process (how work happens); gstack skills are slash-commands for pipelines (what happens next). The known friction point is review: both ship review workflows, so teams should pick one as canonical.