| name | brainstorming |
| description | Explore user intent, requirements, and design before implementation. Use before any creative work or feature build. |
| disable-model-invocation | true |
| license | MIT |
| compatibility | claude-code opencode github-copilot devin pi cursor |
Brainstorming
Turn ideas into fully formed designs before writing code.
Hard gate
Do not write code, scaffold projects, or invoke implementation skills until a design is presented and approved.
Process
- Explore the current project context.
- Ask clarifying questions one at a time.
- Propose 2-3 approaches with trade-offs and a recommendation.
- Present the design and get approval.
- Write the design doc to
docs/specs/YYYY-MM-DD-<topic>-design.md.
- Run a self-review for placeholders, contradictions, ambiguity, and scope.
- Ask the user to review the spec.
- Transition to implementation via a planning step.
Principles
- One question at a time.
- Prefer multiple choice when possible.
- YAGNI: remove unnecessary features.
- Explore alternatives.
- Design for small, well-bounded units.
Design doc sections
- Problem and goals
- Scope
- Architecture
- Components and interfaces
- Data flow
- Error handling
- Testing approach
Notes
Even simple projects need a short design. The design can be a few sentences, but it must be explicit and approved.
