oma-brainstorm

1# Brainstorm - Design-First Ideation
2 
3## Scheduling
4 
5### Goal
6Explore user intent, constraints, and alternative approaches before planning or implementation, then preserve an approved design for downstream planning.
7 
8### Intent signature
9- User says they have an idea, want to brainstorm, compare approaches, explore concepts, or design before planning.
10- Request is ambiguous enough that implementation or task planning would be premature.
11 
12### When to use
13- Exploring a new feature idea before planning
14- Understanding user intent and constraints before committing to an approach
15- Comparing multiple design approaches with trade-offs
16- When the user says "I have an idea" or "let's design something"
17- Before invoking `/plan` for complex or ambiguous requests
18 
19### When NOT to use
20- Requirements are already clear and well-defined -> use `oma-pm` directly
21- Implementing actual code -> delegate to specialized agents
22- Performing code reviews -> use `oma-qa`
23- Debugging existing issues -> use `oma-debug`
24 
25### Expected inputs
26- Early idea, ambiguous goal, product concept, design question, or set of constraints
27- Existing project context when the idea must fit a codebase or product direction
28- User preferences and approval gates
29 
30### Expected outputs
31- Clarified intent and constraints
32- Viable approaches as prose briefs (scenario, mechanism, residual risk), with comparison and recommendation when alternatives aid the decision
33- Section-by-section approved design document
34…