mkbrainstorminglisted

# Brainstorming Explore technical approaches with structured ideation, challenge, convergence, and plan-creator handoff. **Differentiator:** office-hours = "should we build this?", brainstorming = "how should we build this?" ## When to Use - Multiple architecturally-distinct approaches exist for a known requirement - Trade-off analysis between candidate solutions is needed - Novel problem with no obvious pattern in the codebase - Pre-mortem / failure-mode exploration before committing to a design - Constraint-rich problem (budget, time, stack) where the solution space is narrow **NOT this skill if:** you are stuck on a specific existing approach with forced assumptions — use `mk:problem-solving`. **NOT this skill if:** you want to deepen an existing verdict or plan — use `mk:elicit`. ## When NOT to Use | Situation | Use instead | | ----------------------------------------------------- | -------------------------------- | | "Is this worth building?" — product validation | `mk:office-hours` | | Plan already exists, want to challenge scope | `mk:plan-ceo-review` | | Existing brainstorm, verdict, or plan needs deeper reasoning | `mk:elicit` | | Broad codebase inventory before planning | `mk:scout` | | High-stakes multi-perspective architecture debate | `mk:party` | | Bug investigation / root cause