| name | brainstorming |
| description | Resolve ambiguous product or system work before implementation. Use when materially different interpretations would change scope, architecture, or consequential outcomes; skip precise tasks. |
Brainstorming
Skip precise tasks, approved specifications, mechanical changes, and questions answerable from repository context.
- Inspect only the relevant instructions, files, and current behavior.
- State the goal, constraints, success criteria, and safe assumptions.
- Ask one blocking question only when the answer materially changes the result.
- Recommend one approach first; include only genuinely viable, materially different alternatives.
- Describe the smallest useful design: ownership, interfaces, data flow, failure behavior, and verification where relevant.
- Request approval only for a material scope, architecture, irreversible, or externally visible decision.
Decompose independent subsystems only when it clarifies ownership. Pause for missing authority or consequential choices. Read visual-companion.md only when the user explicitly requests visual comparison.
For later implementation, pass forward the chosen approach, assumptions, and acceptance. Select durable planning only if its description independently matches the work.
