Brainstorming Into a GitHub Issue

Core principle

REQUIRED SUB-SKILL: run superpowers:brainstorming (v7) as written. This skill is the "human partner's preference" v7 allows: the written design lives in a GitHub issue, not docs/. It adds only what v7 lacks: persistence to the issue, resume from the issue alone (any session, any harness), the [DRAFT] title prefix ("still being brainstormed"), and splits. Do not restate or reinterpret v7's dialogue, playbacks, sizing, spikes, visual companion, design shape, or builder check — follow them.

Exact gh commands, body shapes, and the ## Brainstorm state section: issue-lifecycle.md.

Entry

No number given:

1. Search open issues by keywords.
2. Search [DRAFT] in:title.
3. Plausible match → show it and ask: adopt #N or start fresh? Never reuse or duplicate silently.
4. No match (or "fresh") → create the [DRAFT] issue, ending in a state section, before the first question; its Next: is the opening question.
5. Send v7's opening message — unless v7's first check finds a quick, clear task: then write the request as the issue, size it quick task, and hand over instead (no opening question; build only when asked).

Number given: load it with gh issue view N --json title,body,comments, then route: