Where are the final designs stored?

Validated designs are automatically written to your project's `docs/plans/` directory with a timestamped filename and committed to your git repository.

How does this skill help prevent over-engineering?

The skill follows the YAGNI (You Ain't Gonna Need It) principle, intentionally removing unnecessary features and focusing on the simplest path to meet success criteria.

Does it provide implementation help after the design is done?

Yes, once a design is validated, it can trigger subsequent workflows like creating isolated git worktrees and detailed implementation plans.

When should I use the Brainstorming skill?

You should use it before any creative work, such as building new features, creating components, or modifying existing behavior, to ensure a solid design foundation.

Why does it only ask one question at a time?

This incremental approach prevents information overload and ensures that every design constraint and requirement is carefully considered before moving to the next step.

Brainstorming & Design

Name: Brainstorming & Design
Author: tianzecn

bytianzecn

•

생산성 및 워크플로

Transforms abstract ideas into fully-formed technical designs and specifications through a structured, iterative dialogue.

소개

This skill serves as a consultative design partner for developers using Claude Code, ensuring every new feature or system modification is thoroughly explored before implementation begins. It facilitates a disciplined discovery process by analyzing current project context, asking targeted questions one at a time, and proposing multiple architectural approaches with clear trade-offs. By validating designs incrementally and documenting the final output into version-controlled plans, it prevents over-engineering and ensures that implementation is guided by a clear, agreed-upon roadmap.

주요 기능

Context-aware project analysis using existing files, docs, and git history
Automated documentation of validated designs into version-controlled Markdown files
1 GitHub stars
Iterative single-question dialogue to refine requirements without cognitive overload
Incremental design presentation and validation in digestible sections
Comparative analysis of 2-3 architectural approaches with pros and cons

사용 사례

Evaluating architectural trade-offs for system refactors or new component designs
Scoping complex new features to define requirements and constraints before coding
Creating standardized design documentation and implementation plans for team review

소개

주요 기능

Context-aware project analysis using existing files, docs, and git history
Automated documentation of validated designs into version-controlled Markdown files
1 GitHub stars
Iterative single-question dialogue to refine requirements without cognitive overload
Incremental design presentation and validation in digestible sections
Comparative analysis of 2-3 architectural approaches with pros and cons

사용 사례

Evaluating architectural trade-offs for system refactors or new component designs
Scoping complex new features to define requirements and constraints before coding
Creating standardized design documentation and implementation plans for team review