Superpowers’ brainstorming skill now asks why first and stops asking filler questions

Superpowers rewrote its brainstorming skill. It now asks a question only when the answer changes what gets built, asks why first, and offers a short design when nothing is left open. In version 7, every message ended in a question.

Users said 7.0.1 re-asked what they had already settled. One request wanted a lower bound only, with no until flag. In seven of seven runs, Opus still asked when the statements close.

The old rule ended every message with a question. Now the agent asks only when the answer would change the result. Otherwise it states its call for you to correct. Steps like where files go are now its own call.

If you haven’t said why, it asks that first, as an open question. When a spec gave Ctrl+K to two features, the old skill just asked which keeps it. Now it sketches both, with trade-offs and a pick.

When your request leaves nothing open, the first message ends with the approach, why the others don’t fit, and the design in a few lines. One approval covers all of it, and only the first message gets this shortcut.

Against 7.0.1, filler questions fell by almost half. The reason behind a request came out every time, where 6.4.2 managed just over half. Fully specified requests were approved after one message, like the old skill.

It still over-asks. An owner who handed over the how on login rate limiting got the most technical questions. One Opus run still asked about statement close dates. The offer to just dive in stays, on purpose.

It merged into the dev branch on November 2nd, after release 7.0.1. It was tested in Claude Code with Opus 5.5 and Sonnet 5.5. If version 7’s questions pushed you toward 6.4.2, I’d wait for the next release instead.