69 lines
1.5 KiB
Markdown
69 lines
1.5 KiB
Markdown
---
|
|
name: brainstorming
|
|
description: Use when creating or developing anything new. Refines rough ideas into fully-formed designs through Socratic questioning before writing code.
|
|
category: meta
|
|
token_budget: 1200
|
|
---
|
|
|
|
# Skill: Brainstorming
|
|
|
|
## The Golden Rule
|
|
**No code until the design is solid.** Brainstorming transforms vague ideas into clear specifications.
|
|
|
|
## Process
|
|
|
|
### Phase 1: Understand the Goal
|
|
Ask clarifying questions:
|
|
- What problem are we solving?
|
|
- Who is the user?
|
|
- What does success look like?
|
|
- What are the constraints?
|
|
|
|
### Phase 2: Explore Alternatives
|
|
For every approach, consider:
|
|
- What are 3 alternative ways to solve this?
|
|
- What are the tradeoffs of each?
|
|
- Which aligns best with existing patterns?
|
|
|
|
### Phase 3: Challenge Assumptions
|
|
Question everything:
|
|
- Why this approach over others?
|
|
- What could go wrong?
|
|
- What are we assuming that might not be true?
|
|
- Is there a simpler way?
|
|
|
|
### Phase 4: Converge
|
|
Synthesize insights into a clear design:
|
|
- Core components
|
|
- Key interfaces
|
|
- Data flow
|
|
- Error handling strategy
|
|
|
|
## Anti-Patterns to Avoid
|
|
- Jumping to code before understanding
|
|
- Accepting first idea without alternatives
|
|
- Skipping tradeoff analysis
|
|
- Assuming requirements are complete
|
|
|
|
## Output Format
|
|
```markdown
|
|
## Problem Statement
|
|
[One sentence]
|
|
|
|
## Proposed Solution
|
|
[2-3 sentences]
|
|
|
|
## Alternatives Considered
|
|
1. [Alternative] - [Why rejected]
|
|
2. [Alternative] - [Why rejected]
|
|
|
|
## Key Design Decisions
|
|
- [Decision 1]
|
|
- [Decision 2]
|
|
|
|
## Next Steps
|
|
1. [First implementation step]
|
|
```
|
|
|
|
## Token Budget: 1200 tokens max
|