brainstorm-chorus

# 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. --- ## Hard rules 1. **One question at a time.** Each prompt MUST contain exactly one question. Wait for the user's rep...