# Structured Brainstorming

## Purpose

Turn rough ideas into decision-ready options by comparing them systematically, narrowing intelligently, and shaping the chosen direction into actionable next steps.

## When to use

- Many ideas exist and the team needs a clear recommendation
- A promising concept needs scoping before implementation
- Tradeoffs need to be surfaced explicitly
- The next step is choosing, sequencing, or planning rather than generating more ideas

## Inputs to gather

- Candidate ideas or possible approaches
- Decision criteria such as impact, effort, risk, speed, or strategic fit
- Constraints on time, team, technical feasibility, or audience needs
- Any assumptions that materially change the choice

## How to work

- Define the decision criteria before ranking options.
- Compare options on the criteria that actually matter for the request.
- Remove weak options quickly once the reason is clear.
- Turn the selected direction into a scoped set of next steps or a buildable outline.
- Keep the analysis proportional; do not over-formalize simple decisions.

## Output expectations

- Clear comparison of options
- Recommended direction with reasoning
- A scoped next-step plan or action outline

## Quality checklist

- Decision criteria are explicit and relevant.
- The recommendation follows from the comparison rather than preference alone.
- The chosen path is actionable, not just inspirational.
- Key assumptions are visible.

## Handoff notes

- Note what would most likely change the recommendation.
- Pair with feature implementation, repo exploration, or messaging skills when moving from choice to execution.