brainstorm
Installation
SKILL.md
Brainstorm: Pre-Creation Design Exploration
Explore the problem space, clarify requirements, and converge on a design direction before creating
issues. This skill produces a spec document — capturing intent, trade-offs, the chosen approach, and
enough detail for both issue creation (/pm) and implementation planning (/cdt).
When to Use
Use this skill when:
- The work is ambiguous — user knows what they want but not how
- Multiple valid approaches exist and trade-offs need discussion
- Scope is unclear — could be one issue or an epic with sub-issues
- The problem domain is unfamiliar and needs exploration first
- A request is large enough that jumping straight to issue creation would produce a vague ticket
Do NOT use for:
- Clear, well-scoped bugs (go directly to
/pm) - Simple chores or dependency updates
- Work that already has a design document or spec
Related skills
More from rube-de/cc-skills
doppler
>-
33council
Consult external AI council (Gemini, Codex, Qwen, GLM-5.1) for thorough reviews and consensus-driven decisions. Use ONLY when explicitly invoked with "/council" or when user says "consult the council", "invoke council", or "council review". Do NOT auto-trigger on generic phrases like "thorough review".
2update
>-
1perf
>-
1dlc
>-
1temporal
>-
1