brainstorming

superbeads:brainstorming

Announce: Using superbeads:brainstorming.

Thin wrapper over superpowers:brainstorming. Runs its full dialogue unchanged and intercepts three specific steps inside that dialogue. Do not restate the contract or the field mapping here — see skills/using-superbeads/SKILL.md.

Override active from the start. The three intercept points below SUPERSEDE superpowers' corresponding steps. While running superpowers:brainstorming: do NOT write any spec file under docs/superpowers/, do NOT ask the user to review a file, and do NOT invoke superpowers:writing-plans. These are replaced by the beads steps below.

Step 1 — Run superpowers:brainstorming

Invoke superpowers:brainstorming via the Skill tool. Execute its full checklist as written:

• Explore project context
• Offer visual companion (if visual questions ahead)
• Ask clarifying questions one at a time
• Propose 2-3 approaches with trade-offs and recommendation
• Present design sections; get user approval after each
• (intercept) Write design doc → see Step 2
• (intercept) User reviews written spec → see Step 3
• (intercept) Invoke writing-plans → see Step 4

Step 2 — Intercept: persist spec → epic (replaces "Write design doc")

Do NOT write to docs/superpowers/. Instead, immediately after the user approves the design (at the point superpowers would write the design doc, before its spec self-review), run /superbeads-materialize MODE A to create the beads epic from the approved design content. Fields are mapped per using-superbeads.

Step 3 — Intercept: review gate → bd show (replaces "User reviews written spec")

Direct the user to review the persisted record:

"Epic created. Run bd show <epic-id> to review it. Let me know if you want changes before we move to the implementation plan."

Wait for approval. If changes are requested, update the epic via /superbeads-materialize and re-check the epic for completeness and consistency. Only proceed once the user approves.

Step 4 — Intercept: handoff → superbeads:writing-plans (replaces "Invoke writing-plans")

Do NOT invoke superpowers:writing-plans. Invoke superbeads:writing-plans for epic <epic-id> (the epic just created in Step 2) — pass that id explicitly so the writing-plans skill can attach child tasks to the correct epic.

Scratch safety-net

If superpowers:brainstorming writes a scratch file to docs/superpowers/ despite this override, /superbeads-materialize ingests it and deletes it. See using-superbeads for the procedure.