Brainstorm
Run a compact diverge-to-converge loop.
Workflow
- Frame: goal, constraints, audience, success criteria, assumptions.
- Baseline: state the simplest honest solution first. Every option must beat it; the baseline stays a candidate.
- Diverge: distinct options across practical, high-leverage, and unusual angles.
- Challenge: weak assumptions, failure modes, tradeoffs, rejections. Always: reject speculative generality (each abstraction, layer, flag, and data copy needs a current caller) and verify load-bearing "needed" claims in the consuming code, not doc assertions.
- Compare: only relevant criteria, plus deletion cost (how easily the option can be removed later). Ties go to the smaller option.
- Converge: strongest 3 picks with rationale and a next step. Self-review first: for each new constant, object, layer, and flag ask "why do we need this?" Cut answers that are only messaging or future-proofing.
Formats
Use Quick by default. Use Deep only for ambiguous or high-stakes decisions. Ask at most one clarifying question only if missing context would materially change the brainstorm; otherwise state assumptions and proceed.
- Quick: clusters, challenges, 3 picks.
- Deep: assumptions, clusters, evaluation table, recommendation.
- Naming: tone groups, fit, ambiguity, pronunciation.
- Technical: approaches, tradeoffs, risks, validation.
- Content: angles, hooks, audiences, outlines.
Avoid filler, near-duplicates, generic best practices, premature recommendations, and scope without a current caller. If asked for more ideas, explore a new axis before listing variants.
1---2name: brainstorm-23description: AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions.4---56# Brainstorm78Run a compact diverge-to-converge loop.910## Workflow11121. Frame: goal, constraints, audience, success criteria, assumptions.132. Baseline: state the simplest honest solution first. Every option must beat it; the baseline stays a candidate.143. Diverge: distinct options across practical, high-leverage, and unusual angles.154. Challenge: weak assumptions, failure modes, tradeoffs, rejections. Always: reject speculative generality (each abstraction, layer, flag, and data copy needs a current caller) and verify load-bearing "needed" claims in the consuming code, not doc assertions.165. Compare: only relevant criteria, plus deletion cost (how easily the option can be removed later). Ties go to the smaller option.176. Converge: strongest 3 picks with rationale and a next step. Self-review first: for each new constant, object, layer, and flag ask "why do we need this?" Cut answers that are only messaging or future-proofing.1819## Formats2021Use Quick by default. Use Deep only for ambiguous or high-stakes decisions. Ask at most one clarifying question only if missing context would materially change the brainstorm; otherwise state assumptions and proceed.2223- Quick: clusters, challenges, 3 picks.24- Deep: assumptions, clusters, evaluation table, recommendation.25- Naming: tone groups, fit, ambiguity, pronunciation.26- Technical: approaches, tradeoffs, risks, validation.27- Content: angles, hooks, audiences, outlines.2829Avoid filler, near-duplicates, generic best practices, premature recommendations, and scope without a current caller. If asked for more ideas, explore a new axis before listing variants.
gabrielmoreira