How does this skill prevent overwhelming the user during planning?

The skill enforces a 'one question at a time' rule and prefers multiple-choice options, ensuring the brainstorming process remains focused and manageable.

What happens once a design is finalized?

The skill automatically writes the validated design to a markdown file in your 'docs/plans/' directory and commits it to Git for version control.

Does it help with the transition to coding?

Yes, once the design is documented, it offers to set up isolated Git worktrees and create detailed implementation plans to start the build.

Why does it propose multiple approaches?

By presenting 2-3 different options with trade-offs, it ensures that you choose the most efficient architecture for your specific project constraints.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: IvanLutsenko

byIvanLutsenko

生産性とワークフロー

Transforms initial ideas into comprehensive technical designs and specifications through a structured, interactive dialogue.

概要

The Brainstorming skill facilitates a collaborative process to refine project requirements and architectural designs before implementation begins. By analyzing existing project context and asking focused, single questions, it helps users explore multiple technical approaches with clear trade-off analysis. This skill ensures designs are validated incrementally in small sections and then automatically documented to your project's repository, promoting a 'think-first' development culture that reduces technical debt and feature creep.

主な機能

Interactive requirements gathering with focused, one-at-a-time questioning.
Comparative analysis of 2-3 different architectural approaches with clear trade-offs.
0 GitHub stars
Incremental design presentation (200-300 word segments) for step-by-step validation.
Strict adherence to YAGNI principles to eliminate unnecessary features early.
Automatic generation and Git-committing of standardized design documentation.

ユースケース

Validating user requirements and technical feasibility before starting the build phase.
Creating standardized design documents for team review and historical reference.
Defining the architecture for a new feature or component within an existing codebase.

概要

主な機能

Interactive requirements gathering with focused, one-at-a-time questioning.
Comparative analysis of 2-3 different architectural approaches with clear trade-offs.
0 GitHub stars
Incremental design presentation (200-300 word segments) for step-by-step validation.
Strict adherence to YAGNI principles to eliminate unnecessary features early.
Automatic generation and Git-committing of standardized design documentation.

ユースケース

Validating user requirements and technical feasibility before starting the build phase.
Creating standardized design documents for team review and historical reference.
Defining the architecture for a new feature or component within an existing codebase.