Brainstorm Skill

Brainstorm Skill

A divergent-then-convergent dialogue cadence for ideas whose direction is still being formed. Compresses the conversation into one ElaborationRound of decision-point Q&A — same shape as a structured elaboration round, but the questions, options and answers are synthesized at the end of the conversation rather than asked up front.

This skill is a producer of one elaboration round; the scheduler decision (validate vs. follow-up) belongs to the calling idea skill.

Tool namespace: Chorus tools are exposed by the connected MCP server under a mcp__chorus__ prefix on dsh (e.g. mcp__chorus__chorus_get_idea). Bare names are used below for readability — prepend mcp__chorus__ when invoking. See chorus for the full rule.

dsh interaction model: in an interactive session, use ask_user_question for the one-question-at-a-time cadence. When CHORUS_DAEMON_HEADLESS=1, persist the decision points through a Chorus elaboration round and an @mention comment, then end the turn.

When invoked

Only as a sub-step of the idea skill, only after the user has explicitly opted in (via the idea skill's plain-text Brainstorm prompt). Never run standalone, never run without user opt-in. The expected entry point is the idea skill's "Step 4.5: Brainstorm Mode (Optional Prelude)" — see the idea skill for the surrounding flow.

Research boundary

Reuse the calling Idea's findings and follow research-chorus (shared rules); switching into brainstorm does not grant a second investigation. If the goal needed focusing first, after the user selects a direction and before synthesis, apply the caller's optional research decision once with that focus. Return any findings alongside the synthesized round for the Idea caller to persist. Research does not choose the user's direction, remove the opt-in/selection gate, write files/comments, or resolve elaboration.

Hard rules

1. One question at a time. Each prompt MUST contain exactly one question. Wait for the user's reply before asking the next.
2. Multi-choice preferred. Frame each question as 2-4 options where possible. In interactive dsh, pass those options to ask_user_question. Open-ended is acceptable when options would be premature, but lean toward concrete choices.
3. Propose 2-3 directions before stopping divergence. Once the requirement direction is clear enough to enumerate, present 2-3 distinct approaches in a single prompt. Mark exactly one as the recommended option and say why (the dominant tradeoff).
4. Explicit user approval required to exit divergence. Do NOT proceed to synthesis until the user has selected one of the proposed directions in their reply.
5. No files written. Do NOT write any markdown, design doc, scratch file, or any other file to disk. The conversation produces an ElaborationRound and nothing else on disk.
6. No comments posted. Do NOT call chorus_add_comment from this skill. Comments belong to the idea skill or the user, not to the brainstorm step.
7. No design-doc handoff. Do NOT invoke writing-plans, writing-skills, or any skill whose purpose is to produce a design document. The brainstorm output is the synthesized round — there is no separate doc.
8. No validate_elaboration call. Do NOT call chorus_pm_validate_elaboration from this skill. Whether to resolve the elaboration or open a follow-up round (chorus_pm_start_elaboration again) is the calling idea skill's decision, not this skill's.

Step-by-step

1. Gather context

Before asking the first divergent question, read the idea and surrounding project state. Mirror the idea skill's gather-context list: