How does this skill prevent overwhelming the user?

It follows a strict 'one question at a time' rule and uses multiple-choice formats whenever possible to simplify complex decision-making.

When should I use the Brainstorming skill?

Use it when implementation paths are unclear, multiple approaches exist, or requirements are incomplete and need validation before coding begins.

Does it produce actual documentation?

Yes, once a design is validated, it automatically writes a concise design document to your project's docs/plans directory and commits it to git.

Can I use this for simple bug fixes?

It is recommended to skip this skill for mechanical tasks or simple fixes with obvious solutions, as it is optimized for high-level design and architectural decisions.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: Light-Brands

byLight-Brands

Herramientas de Diseño

Transforms vague project concepts into structured technical designs through iterative dialogue and comparative architectural analysis.

Acerca de

The Brainstorming skill is designed to bridge the gap between initial ideas and final implementation by facilitating a high-level design phase. It prevents premature coding by guiding users through a Socratic discovery process, exploring multiple architectural alternatives with clear trade-offs, and incrementally validating design sections. By emphasizing YAGNI principles and structured decision-making, it helps developers establish a solid foundation for complex features, ensuring that the final implementation aligns perfectly with project constraints and success criteria.

Características Principales

Socratic inquiry for deep requirement gathering and constraint discovery
Incremental validation of data flow, state management, and error handling
Comparative analysis of multiple architectural approaches with pros/cons
Automated generation of standardized design documents and implementation plans
0 GitHub stars
Git-integrated workflow for tracking design decisions and rationale

Casos de Uso

Validating complex design decisions to ensure maintainability and performance
Turning fuzzy requirements into a concrete technical architecture before coding
Choosing between competing implementation patterns for a new system feature

Acerca de

Características Principales

Socratic inquiry for deep requirement gathering and constraint discovery
Incremental validation of data flow, state management, and error handling
Comparative analysis of multiple architectural approaches with pros/cons
Automated generation of standardized design documents and implementation plans
0 GitHub stars
Git-integrated workflow for tracking design decisions and rationale

Casos de Uso

Validating complex design decisions to ensure maintainability and performance
Turning fuzzy requirements into a concrete technical architecture before coding
Choosing between competing implementation patterns for a new system feature