Where are the brainstormed designs stored?

Validated designs are automatically written to a timestamped Markdown file in the docs/plans/ directory and committed to your git repository.

How does it handle complex architectural decisions?

The skill proposes 2-3 different approaches with specific trade-offs and recommendations, allowing you to choose the best path forward based on your needs.

What is the primary benefit of the Brainstorming skill?

It ensures that user intent and project constraints are fully explored and documented before implementation, reducing rework and miscommunication.

Does this skill work with existing codebases?

Yes, it begins every session by checking the current project state, including files and recent commits, to ensure designs are compatible with your existing work.

Why does it only ask one question at a time?

This method prevents cognitive overload and ensures that each requirement is thoroughly explored and validated before moving to the next topic.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: lgbarn

bylgbarn

Collaboration Tools

Transforms raw ideas into structured technical designs and validated specifications through iterative, collaborative dialogue.

About

The Brainstorming skill serves as a critical pre-implementation phase for any creative or technical task within Claude Code. It guides the AI to systematically explore user intent, analyze existing project context, and propose multiple architectural approaches with clear trade-offs. By enforcing a 'one question at a time' rule and incremental validation of design sections, it ensures that requirements are fully understood and documented in your repository before a single line of implementation code is written, effectively preventing feature creep and technical debt.

Key Features

Automated documentation and git commitment of validated design plans
Incremental design presentation with 200-300 word validation check-ins
Single-question iteration to prevent information overload during discovery
Context-aware analysis of project files, documentation, and git history
Comparative architectural proposals featuring 2-3 distinct approaches
0 GitHub stars

Use Cases

Generating and version-controlling detailed design specifications
Refining project scope and exploring trade-offs between different tech stacks
Defining technical requirements and architecture for new features

About

Key Features

Automated documentation and git commitment of validated design plans
Incremental design presentation with 200-300 word validation check-ins
Single-question iteration to prevent information overload during discovery
Context-aware analysis of project files, documentation, and git history
Comparative architectural proposals featuring 2-3 distinct approaches
0 GitHub stars

Use Cases

Generating and version-controlling detailed design specifications
Refining project scope and exploring trade-offs between different tech stacks
Defining technical requirements and architecture for new features