cm-brainstorm-idealisted

# Brainstorm Idea — Strategic Analysis Gate ## TL;DR - **Use before** cm-planning for complex/ambiguous initiatives - **Frameworks**: Design Thinking + 9 Windows (TRIZ) + Double Diamond - **Output**: 2-3 qualified options + recommendation - **Writes**: handoff/intent.json > **Understand deeply. Evaluate multi-dimensionally. Propose qualified options. Then — and only then — plan.** > This skill is the BRIDGE between an existing product and its next evolution. ## When to Use **ALWAYS when:** - User requests complex changes to an existing product - Initiatives or enhancements that touch multiple system areas - User jumps straight into hard/complex tasks without analysis - Post `cm-project-bootstrap` — product exists, needs improvement - Feature requests that could be solved in fundamentally different ways - "What should we do next?" / "What to improve?" / "Enhancement" / "Initiative" **Skip when:** - Simple bug fixes (use `cm-debugging`) - New project from scratch (use `cm-project-bootstrap`) - Task is already clearly defined and scoped (go to `cm-planning`) - Quick one-off changes (< 30 min work) ## Gate Function ``` User requests complex task → Is the problem clearly understood and qualified? → NO → Run cm-brainstorm-idea FIRST → YES → Go to cm-planning directly ``` When downstream skills detect an unqualified complex request, they should REDIRECT here: ``` cm-planning detects ambiguity → "Problem not clear. Run cm-brainstorm-idea first." cm-execution gets va