When should I trigger the brainstorming skill?

You should use it whenever a request is ambiguous, when you're starting a complex new feature, or when you need to weigh the pros and cons of different technical approaches.

Does this skill help prevent over-engineering?

Yes, it specifically employs YAGNI (You Aren't Gonna Need It) principles to resist unnecessary complexity and ensure the simplest effective solution is chosen.

How does this skill differ from implementation planning?

Brainstorming focuses on the 'WHAT'—clarifying the goal and the high-level approach. Planning focuses on the 'HOW'—the specific files, code changes, and steps needed to execute.

What is the output of a brainstorming session?

The primary output is a structured markdown design document saved to your repository, detailing the chosen approach, key decisions, and next steps for implementation.

Brainstorming & Design Discovery

Name: Brainstorming & Design Discovery
Author: gvkhosla

bygvkhosla

•

Productivity & Workflow

Facilitates structured discovery sessions to clarify requirements, explore architectural approaches, and document design decisions before implementation.

The Brainstorming skill acts as a pre-planning layer for Claude Code, ensuring that developers build the right thing before focusing on how to build it. It guides the user through a multi-phase process that assesses requirement clarity, probes for intent using targeted questioning, and presents structured trade-off analyses between different implementation approaches. By adhering to YAGNI principles and producing a standardized design document, this skill eliminates ambiguity and provides a solid foundation for subsequent coding tasks.

Key Features

01Seamless integration and handoff to planning workflows

0235 GitHub stars

03Structured multi-phase discovery to resolve requirement ambiguity

04Comparative approach analysis with pros, cons, and trade-offs

05One-at-a-time questioning to prevent user cognitive overload

06Automated design document generation in markdown format

Use Cases

01Refining vague feature requests into actionable technical requirements

02Documenting design decisions and success criteria for better project traceability

03Evaluating multiple architectural paths for a new component or refactor

Key Features

01Seamless integration and handoff to planning workflows

0235 GitHub stars

03Structured multi-phase discovery to resolve requirement ambiguity

04Comparative approach analysis with pros, cons, and trade-offs

05One-at-a-time questioning to prevent user cognitive overload

06Automated design document generation in markdown format

Use Cases

01Refining vague feature requests into actionable technical requirements

02Documenting design decisions and success criteria for better project traceability

03Evaluating multiple architectural paths for a new component or refactor