brainstorm
Collaborative Brainstorming
Turn uncertainty into a useful choice or a focused experiment. Explore only the questions that could change the design. A clear implementation request already supplies direction; act on it without manufacturing a brainstorm or approval gate.
The user's instructions take precedence over this skill's guidelines. Preserve their constraints and existing authorization. Resolve routine design details with judgment; ask only when missing information materially changes the outcome and cannot be inferred.
Choose the Work Shape
| Situation | Useful output |
|---|---|
| The user wants open exploration | Distinct directions with concrete tradeoffs and unresolved questions |
| The problem is clear but the mechanism is uncertain | A recommendation and the evidence that would overturn it |
| One assumption determines feasibility | A small test of that assumption before elaborating designs |
| The approach is selected and implementation is authorized | Continue into implementation |
| The user asks why something happens | Diagnose the cause before designing a fix |
Ground the Question
Read the relevant code, artifact, or workflow and recall prior decisions. When Sibyl is configured, use its installed skill for current commands (sibyl context "<decision>" --intent plan). Memory supplies leads; inspect current evidence before reusing a volatile claim.