How does the incremental validation work?

Instead of presenting a massive document at the end, the skill shares small sections of the design (200-300 words) and asks for feedback after each part to ensure the direction is correct.

Where does the skill save the design documentation?

The skill automatically creates and incrementally updates a design file located at .claude/docs/plans/ -design.md within your repository.

Can I transition from design to implementation easily?

Yes. Once the brainstorming process is complete and you've approved the design, the skill will prompt you to transition to the 'writing-plans' skill for executable step-by-step instructions.

When should I use the Brainstorming skill versus standard coding?

Use this skill at the start of a project or feature when you have a rough idea but haven't settled on the architecture. It is for design and discovery, not for writing implementation plans or code.

Brainstorming & Design

Name: Brainstorming & Design
Author: udecode

byudecode

•

1,108

Productividad y Flujo de Trabajo

Transforms rough conceptual ideas into structured technical designs through collaborative questioning and incremental documentation.

Acerca de

The Brainstorming skill is a specialized tool for the early stages of software development, designed to bridge the gap between a vague idea and a concrete implementation plan. It guides users through a structured discovery process, asking targeted questions and proposing multiple architectural approaches while maintaining a living design document. By focusing strictly on high-level conceptualization and trade-off analysis, it ensures that technical decisions are validated and documented before any code is written, preventing architectural debt and scope creep.

Características Principales

Collaborative questioning using structured tools for efficiency
Section-by-section design validation to ensure alignment
1,108 GitHub stars
Incremental design documentation in dedicated plan files
Multi-approach exploration with detailed trade-off analysis
Strict separation between conceptual design and implementation details

Casos de Uso

Evaluating different technology stacks and data flow patterns
Refining ambiguous project requirements into technical specs
Architecting new features before defining file structures

Acerca de

Características Principales

Collaborative questioning using structured tools for efficiency
Section-by-section design validation to ensure alignment
1,108 GitHub stars
Incremental design documentation in dedicated plan files
Multi-approach exploration with detailed trade-off analysis
Strict separation between conceptual design and implementation details

Casos de Uso

Evaluating different technology stacks and data flow patterns
Refining ambiguous project requirements into technical specs
Architecting new features before defining file structures