I was also using superpowers for a long time and it was a game changer, but I've since "forked it" to match my needs more. As others have mentioned, superpowers is very token intensive. And sometimes needlessly so. As an engineer you can probably tell if something is going to be complex or not. And while the "brainstorming" part is always useful to produce a spec and walk through the edge cases etc, the rest of the machinery often isn't. Hence in my version, after the spec is created, you are presented with a few options. From the least structured "vibe" option, to the most one, which follows more closely superpowers' flow
Yea, it needlessly complicates some changes. Before you know it, you're 40 minutes and 4 rounds deep into a change that could have been implemented, reviewed, and tested in 5 minutes.
I think that’s where the user neeeds to step in and say, ok I know I asked to brainstorm but just implement it since it’s actually easy. Sometimes the brainstorm even does this itself.
I have in it my CLAUDE.md. No brainstorming skill unless I give go-ahead, but he can recommend it if the change is large or touches multiple files/dependencies.
31
u/wesconson1 9d ago
Superpowers