brainstorm_skill

Overview

This skill delivers structured, interactive idea refinement using a Socratic questioning methodology combined with multi-perspective analysis and proactive research. It helps turn rough concepts into well-defined, implementable descriptions and identifies gaps, risks, and enhancement opportunities. Use it to prepare ideas for implementation planning or to decide whether architectural decisions need formal documentation.

How this skill works

On invocation the skill captures the core concept, goals, constraints, and project context, then runs iterative Socratic questioning until you signal readiness. It spawns targeted research agents (web research always, codebase research when code context is detected), applies Six Thinking Hats, SCAMPER, and a premortem, and then synthesizes findings into actionable insights. If clear architectural decisions arise, it prepares ADR content and can hand off to create-plan for implementation planning.

When to use it

• You have a rough idea and want to surface hidden assumptions and gaps.
• You need to evaluate options and choose between architectural or technical approaches.
• You want a multi-perspective review (risks, benefits, creative alternatives).
• You’re preparing an idea for implementation planning or ADR documentation.
• You need focused research on patterns, best practices, and comparable projects.

Best practices

• Provide an initial description with stated goals and any constraints to speed phase 1.
• Answer Socratic questions candidly; the process relies on iterative clarification.
• Flag any references to files, modules, or the codebase to enable codebase research.
• Don’t rush: allow multiple Q/A rounds before moving to research and synthesis.
• Use the synthesized output directly to drive create-plan or to create ADRs when decisions crystallize.

Example use cases

• Refining a new feature idea before writing a proposal or ticket.
• Exploring trade-offs between two implementation approaches for a shared service.
• Finding missing requirements and edge cases for an MVP.
• Preparing an architectural decision for documentation as an ADR.
• Assessing reuse opportunities by comparing the idea to existing codebase patterns.