Why does it ask only one question at a time?

This incremental approach prevents cognitive overload and ensures that each aspect of the requirement is thoroughly explored before moving to the next.

When should I use the brainstorming skill?

Use it at the start of any creative task, such as building new components, adding functionality, or modifying core logic, to ensure all requirements are clear.

How does it help with documentation?

Once a design is validated, the skill automatically generates a dated markdown file in your project's docs folder and commits it to your repository.

Can it suggest different implementation paths?

Yes, it is specifically designed to propose 2-3 different approaches with trade-offs, recommending the most efficient path based on your project context.

Does it write code immediately?

No, its primary purpose is to finalize the design and plan. Once the design is committed, it can transition into an implementation phase using separate planning skills.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: unclecatvn

byunclecatvn

•

Productivity & Workflow

Guides users through a structured discovery and design process to transform raw ideas into production-ready specifications.

About

The Brainstorming skill bridges the gap between vague ideas and concrete implementation by facilitating a natural, collaborative dialogue. It forces a pause before coding to explore user intent, analyze project context, and compare alternative architectural approaches. By asking focused, one-at-a-time questions and presenting designs in digestible sections, it ensures every requirement is validated and documented before a single line of feature code is written, reducing technical debt and scope creep.

Key Features

1 GitHub stars
Comparative approach analysis presenting multiple architectural trade-offs
Automated documentation and git-based versioning for approved designs
Context-aware discovery via project file and git history analysis
Iterative refinement using focused, one-question-at-a-time dialogue
Incremental design validation with 200-300 word section previews

Use Cases

Refining complex feature requests into actionable technical specifications
Evaluating architectural trade-offs between different implementation strategies
Generating structured design documentation for team alignment

About

Key Features

1 GitHub stars
Comparative approach analysis presenting multiple architectural trade-offs
Automated documentation and git-based versioning for approved designs
Context-aware discovery via project file and git history analysis
Iterative refinement using focused, one-question-at-a-time dialogue
Incremental design validation with 200-300 word section previews

Use Cases

Refining complex feature requests into actionable technical specifications
Evaluating architectural trade-offs between different implementation strategies
Generating structured design documentation for team alignment