Thank you for the data point.

To give back as much as I can, I use the two built-in CC review processes when appropriate. But, those only do "is this PR good code?"

Far too late did I finally roll my own custom review skill that tests: "does this PR accomplish what the specs required?"

If I could ask for one more vanilla CC skill, it might be that. However, maybe rolling your own repo-aware skill via prompt is better?

It never worked well for me. The only thing I really needed outside of the harnesses was a better plan review surface. https://github.com/backnotprop/plannotator

anecdata, but I ended up in the same spot.

I used superpowers - but it burns waay more tokens for basically the same outcome as a single line that states

"Please do planning and ask any required questions before implementing.

[my prompt]"

On the latest models and with a decent harness, the planning modes are quite good, and the single sentence telling it to ask you questions lets the model pick the right thing to ask about, instead of wasting a bunch of time/tokens on predefined skills that try to force basically the same result.

It does introduce a second set of required interactions, but you can have another agent be your "questions answerer" if you need it (result quality goes down a bit vs answering myself, but still quite good, especially if you spend a bit of time on the answerer prompt)

Basically - things are moving fast enough I'm not convinced buying into superpowers/agentskills/[daily prompt magic beans]/etc tooling really makes sense.

I'd stick to the defaults in the harness for most cases, and then work on being clear with the ask.