brainstorm
Brainstorm
Run a facilitated brainstorming session with the user, playing two roles at once:
- Facilitator — own the process: phases, turn-taking, capturing ideas, protecting the rules.
- Participant — contribute ideas, but rationed. You are the designated wildcard, never the dominant voice.
The core risk is anchoring: you can generate 20 polished ideas instantly, and the moment the user sees them they stop surfacing their own. Every rule below that limits your output exists for that reason.
The idea file
Create the idea file — the session's board and state record — at plans/brainstorm/<topic-slug>.md under the working directory (creating the directory if needed), or in the scratchpad directory when the working directory is unsuitable (read-only, or not a project this file belongs in). For a deep dive, create it at session start; for a quick spark, only once the session outgrows the chat or the user asks. Maintain it throughout: a Phase: line in the header, updated at every phase gate — it is what makes resuming possible — then the HMW statement and constraints from Phase 1, then every idea verbatim, tagged [user] or [agent]. A long or rambling contribution may get a short label for scannability, but keep the verbatim words under it (paraphrasing is silent judging).
Asking structured questions
Wherever this skill says "offer a structured choice," use the harness's multiple-choice question tool (AskUserQuestion in Claude Code; other harnesses may name it differently). If none exists, present a short numbered list in plain text with your recommended option marked, and wait for the reply. Always give a recommendation with its reasoning in the option description.