When should I use the Brainstorming skill?

Use this skill at the beginning of a project or feature development phase, before writing any code, to refine your initial ideas into a solid, validated design.

How does it help with software architecture?

The skill proposes 2-3 different architectural approaches for every idea, providing trade-offs and a specific recommendation based on your project context.

Why does the skill ask questions one at a time?

This incremental approach prevents overwhelm and ensures that every constraint, success criterion, and purpose is fully understood before the design phase begins.

What happens after the design is finished?

After documentation, the skill can transition into implementation by setting up isolated git worktrees and creating detailed execution plans.

Does this skill generate documentation?

Yes, once a design is validated, the skill automatically writes a detailed markdown plan to your docs folder and commits it to your Git repository.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: Krosebrook

byKrosebrook

•

Collaboration Tools

Transforms raw project ideas into detailed, validated technical designs through iterative questioning and structured architectural exploration.

About

The Brainstorming skill facilitates the critical pre-implementation phase by guiding developers through a structured dialogue to turn vague concepts into concrete technical specifications. By analyzing the current project context and asking focused, one-at-a-time questions, it helps users explore multiple architectural approaches and trade-offs while adhering to YAGNI principles. The skill ensures high-quality outcomes by presenting designs in digestible increments for validation and automatically generating professional documentation that is committed directly to the repository.

Key Features

Iterative one-at-a-time questioning to prevent information overload
Incremental design validation in manageable 200-300 word sections
Automated Git-integrated documentation for design plans
1 GitHub stars
Comparative architectural proposals highlighting trade-offs and recommendations
Context-aware project state analysis for informed suggestions

Use Cases

Defining the architecture for a new feature or microservice
Refining rough project ideas into structured technical requirements
Generating standardized design documentation for team review

About

Key Features

Iterative one-at-a-time questioning to prevent information overload
Incremental design validation in manageable 200-300 word sections
Automated Git-integrated documentation for design plans
1 GitHub stars
Comparative architectural proposals highlighting trade-offs and recommendations
Context-aware project state analysis for informed suggestions

Use Cases

Defining the architecture for a new feature or microservice
Refining rough project ideas into structured technical requirements
Generating standardized design documentation for team review