Superpowers: 14 Key Features
Superpowers is not a loose skill set but a gated engineering pipeline for development. Learn how its 14 skills enforce process, quality, and review.
“AI Disruption” Publication 10,300 Subscriptions 20% Discount Offer Link.
Superpowers have heated up again recently. After the Fable 5 refactor, token consumption dropped significantly, and performance improved, so discussions in the community picked up again.
I learned about this Skill early on, but I always assumed it was a Skill Kit—just a toolbox of “14 independent tools” that you could pick and choose from in production as needed. Only recently, after reading through all 14 skills, did I realize that my understanding was wrong. On the surface, it looks like a set of Skills, but it actually embeds several strongly constrained pipelines. Each skill is a gate on that line.
This post breaks down its implementation and talks about the techniques. I call this the “method”—that is, how this pipeline collaborates and what each checkpoint is responsible for blocking.
Conclusion First
It can be compressed into one sentence:
Superpowers’ 14 skills are not scattered feature points, but an engineering system woven around the full software development lifecycle. It has one hard-coded main line, plus three cross-cutting disciplines that can be inserted at any time, along with review and isolation mechanisms. When you invoke any one of them, you are often pulled through the entire set of dependencies on that line.
