brainstormUse when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue (3-5 AUQ rounds) and writes a spec markdown file. Use BEFORE /plan feature when product intent needs validation; skip to /plan feature when scope is already clear. HARD-GATE prevents any code work until the design is user-approved.
Independent GitHub snapshot · Automated classification · Original documentation governs
name: brainstorm description: Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue (3-5 AUQ rounds) and writes a spec markdown file. Use BEFORE /plan feature when product intent needs validation; skip to /plan feature when scope is already clear. HARD-GATE prevents any code work until the design is user-approved. metadata: model: inherit color: cyan user-invocable: 'true' disable-model-invocation: 'true' argument-hint: '[topic-or-feature-slug]' allowed-tools:
Read skills/brainstorm/SKILL.md in full before taking any action, then follow its complete workflow.
The linked document is authoritative, including its prechecks, argument rules, and stop conditions.
Resolve this link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root; resolve relative links inside the canonical document from its own directory. Keep the user’s project as the target of project operations.
$ARGUMENTS means the trailing user input after the selected command skill, or an empty string when absent. Preserve flags, quoted text, and Unicode as data. Do not perform global substitution in the command document, shell expansion on the argument string, or execution of that string as shell code. When the workflow needs a command, pass its arguments through structured tool parameters or safely quoted individual arguments.
Regenerate with node scripts/generate-codex-skills.mjs.