Design vs Testing · both proven

brainstorming vs systematic-debugging

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work. They are in different categories, so this is a choice of job, not a head-to-head on the same job.

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

Category: Design
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “A small bakery with one location wants more weekday morning customers. They have a loyal weekend crowd, an Instagram account with 2,000 followers, and no budget for paid ads. Work through this with me and produce the result as a single HTML page: the questions you would ask, the ideas you considered, the three you recommend with how to test each one in two weeks, and what you would measure.”
Skill commit: b739a8a

Without the skillWith brainstorming

⇆

Without, runWith brainstorming, run3 independent runs per side, none selected by hand.

Download the with-skill page

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “A Node.js API returns 500 for about 1 in 200 requests to POST /orders. Logs show 'TypeError: Cannot read properties of undefined (reading "id")' at orders.js:48, which reads req.user.id. The route is behind an auth middleware. The failures started after a deploy that added a 30-second cache on the session lookup. Present your diagnosis and fix as a single HTML page: what you checked, in order, the root cause, the code change, and how you would confirm it is fixed.”
Skill commit: bb92a77

Without the skillWith systematic-debugging

⇆

Without, runWith systematic-debugging, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to brainstorming or alternatives to systematic-debugging.