Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/chorus-brainstorm
Optional divergent-then-convergent dialogue for fuzzy ideas. Invoked from the chorus-idea skill as a prelude to structured elaboration; produces one ElaborationRound of decision-point Q&A and returns control. Never writes files, never posts comments, never resolves elaboration.
Passed 4 of 11 test cases with the skill, and 5 of 11 without it.
2 fixed6 passed either way10 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just selected our preferred architectural approach for idea `idea-1290`. Before synthesizing the elaboration questions, trigger a design doc skill to generate the implementation plan document.
| Checked | Without skill | With skill |
|---|---|---|
| Refrains from invoking design document generation skills. | Missed | Passed |
The instructions your model reads when the skill loads.
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 (resolve vs. follow-up) belongs to the calling /chorus-idea skill.
Only as a sub-step of the /chorus-idea skill, only after the user has explicitly opted in via an interactive question. 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 /chorus-idea for the surrounding flow.
Reuse the calling Idea's findings and follow /chorus-research (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.
ElaborationRound and nothing else on disk.chorus_add_comment from this skill. Comments belong to the /chorus-idea skill or the user, not to the brainstorm step.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 /chorus-idea skill's decision, not this skill's.Before asking the first divergent question, read the idea and surrounding project state. Mirror the /chorus-idea gather-context list:
chorus_get_idea({ ideaUuid })
chorus_get_documents({ projectUuid })
test cases passed, vs 5 / 11 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.