How does this skill help with architectural decisions?

It explicitly proposes 2-3 different approaches with pros and cons, providing a recommendation to help you make informed architectural choices.

Why does it ask only one question at a time?

This incremental approach prevents information overload and ensures that every aspect of the project's purpose and constraints is thoroughly explored.

Where are the design documents stored?

The skill saves validated designs as Markdown files in the 'docs/plans/' directory and automatically commits them to your git repository.

When should I use the Brainstorming skill?

Use it at the start of a project or new feature development, before writing code, to refine rough ideas into fully-formed designs and specifications.

Does this skill automatically write code?

No, it is specifically designed for the planning phase. Once a design is finalized, it can transition to implementation skills like 'writing-plans'.

Brainstorming & Design Refinement

Name: Brainstorming & Design Refinement
Author: timbuchinger

bytimbuchinger

Productivity & Workflow

Refines rough ideas into fully-formed technical designs through collaborative questioning and incremental validation.

About

This skill transforms vague concepts into detailed technical specifications through a structured, interactive dialogue. It guides Claude to investigate project context, propose multiple architectural approaches with trade-offs, and present designs in digestible sections for iterative feedback. By prioritizing incremental validation and ruthless simplicity (YAGNI), it ensures that developers have a solid, agreed-upon blueprint and documentation before writing a single line of code or starting implementation plans.

Key Features

Proposes 2-3 distinct architectural approaches with detailed trade-offs
Interactive questioning to clarify project requirements and constraints
Automatic documentation of designs to version-controlled Markdown files
0 GitHub stars
Ruthless application of YAGNI principles to eliminate feature creep
Incremental design presentation in 200-300 word segments for validation

Use Cases

Translating a high-level feature request into a concrete technical architecture
Exploring alternative implementation strategies before committing to a specific stack
Creating standardized design documentation for team alignment and future reference

About

Key Features

Proposes 2-3 distinct architectural approaches with detailed trade-offs
Interactive questioning to clarify project requirements and constraints
Automatic documentation of designs to version-controlled Markdown files
0 GitHub stars
Ruthless application of YAGNI principles to eliminate feature creep
Incremental design presentation in 200-300 word segments for validation

Use Cases

Translating a high-level feature request into a concrete technical architecture
Exploring alternative implementation strategies before committing to a specific stack
Creating standardized design documentation for team alignment and future reference