Why does it only ask one question at a time?

This incremental approach prevents cognitive overload and ensures that each requirement or constraint is fully explored before moving to the next topic.

How does the Brainstorming skill prevent scope creep?

It employs the YAGNI (You Ain't Gonna Need It) principle to ruthlessly identify and remove unnecessary features during the design phase.

Where are the design documents stored?

Validated designs are automatically written to your project's `docs/plans/` directory with standardized naming conventions and committed to git.

Does this skill write code directly?

No, it is specifically designed for the pre-implementation phase to ensure a solid plan exists, though it integrates with other skills to begin coding once the plan is finished.

What happens after the design is finalized?

The skill can transition into implementation by setting up isolated git worktrees and creating detailed step-by-step implementation plans.

Brainstorming & Design Navigator

Name: Brainstorming & Design Navigator
Author: dkyazzentwatwa

bydkyazzentwatwa

•

생산성 및 워크플로

Facilitates collaborative technical design and requirement refinement through structured dialogue before code implementation.

소개

The Brainstorming skill transforms abstract ideas into concrete technical specifications by engaging in a focused, iterative dialogue. It prevents premature implementation by first analyzing the current project context and then guiding the user through a one-question-at-a-time refinement process. By presenting multiple architectural approaches with trade-offs and validating designs in bite-sized sections, it ensures that every feature is necessary (YAGNI), well-documented, and aligned with user intent before a single line of production code is written.

주요 기능

Context-aware project analysis of files, docs, and git history
29 GitHub stars
Multi-approach trade-off analysis for objective decision making
Incremental design validation in 200-300 word sections
Automated documentation generation and git-integrated plan tracking
Iterative single-question refinement to prevent information overload

사용 사례

Documenting complex system changes in a standardized design format
Refining vague feature requests into actionable technical specifications
Evaluating different architectural patterns before starting a new component

소개

주요 기능

Context-aware project analysis of files, docs, and git history
29 GitHub stars
Multi-approach trade-off analysis for objective decision making
Incremental design validation in 200-300 word sections
Automated documentation generation and git-integrated plan tracking
Iterative single-question refinement to prevent information overload

사용 사례

Documenting complex system changes in a standardized design format
Refining vague feature requests into actionable technical specifications
Evaluating different architectural patterns before starting a new component