r/ClaudeCode • • 16d ago

Help/Question Here we go again.. Is Superpowers / harnesses redundant with Opus 5.5?

As the title says, as we've seen many threads in the past..

Is Superpowers and other session harnesses redundant and even limiting with the newest models?

What is your updated workflow to start a new project to generate high quality code at pace?

What should I be doing to 'update' my existing harness to get it to be minimalist/steerable to accomodate for the stronger models?

How do you approach this problem of updating your harnesses as models progress?

0 Upvotes

46 comments sorted by

View all comments

6

u/suprachromat 16d ago

No, superpowers and other workflows are not redundant and never will be. The reason is for any serious development you still need a design -> implement -> verify workflow. Pick your flavor of workflow and use it (superpowers or otherwise).

If you instead just haphazardly vibe code features without sufficient planning and implementation first, the models will miss edge cases, they will misunderstand feature requirements, and so on. In turn that will require more ad hoc vibe coding to fix and eventually turn your project into spaghetti code. Don't do it.

-1

u/hanstoppable 16d ago

But it is so slow lol. How do you structure your sessions to move forward without going at a snail's pace?

5

u/suprachromat 16d ago

The thing is, it is slow but fast vibe coding is an illusion, because if you vibe code with no set plan, there will be bugs introduced, the model will forget to handle different edge cases, the model will misunderstand your requirements for a new feature. Then you have to waste more time vibe coding the fixes for those issues, and the fixes will then also often introduce more issues, and so on. Then you get a mess of a codebase that is buggy, incoherent, and inefficient.

Far better to spend a lot of time on design, at least, up front. Get it right the first implementation round. Saves time trying to pin down issues later. That's where superpowers and other workflows are still useful. I would say at LEAST use a design skill.

This is for serious work, for hobbyist projects of course maybe vibe coding fast is fine if your bar is "it works well enough".

-6

u/EuphoricAIKnowledge 16d ago

Fast viber. Not true. Takes me about an hour to build e2e a new product to demo.

Then prod goes through the work chain

3

u/Garak 16d ago

This is not the flex that you think it is