Does it automatically save the design work?

Yes, once a design is validated, the skill writes a markdown document to your docs/plans folder and commits it to git.

What is the 'one question at a time' rule?

To prevent overwhelming the user, the skill is programmed to ask only one specific question per message, ensuring high-quality answers and clear focus.

When should I use the Brainstorming skill?

Use this skill at the beginning of a new project or feature, before writing code or implementation plans, to refine ideas into a fully-formed design.

How does the skill handle different architectural options?

It proposes 2-3 different approaches with specific trade-offs and provides a recommendation based on your project's current state and constraints.

Can this skill help with implementation?

While its primary focus is design, it includes hooks to transition into implementation using git worktrees and detailed plan-writing skills.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: nimeshgurung

bynimeshgurung

Productividad y Flujo de Trabajo

Refines abstract ideas into structured technical designs through interactive dialogue and incremental validation.

Acerca de

The Brainstorming & Design Planner skill bridges the gap between initial concepts and implementation-ready specifications within Claude Code. It facilitates a natural, collaborative dialogue by asking focused, one-at-a-time questions to explore project constraints and architectural trade-offs. By proposing multiple approaches and validating designs in bite-sized sections, it ensures that every feature is necessary and that the final documentation is clear, concise, and version-controlled. This skill is essential for developers who want to avoid 'mechanical' coding errors by establishing a solid design foundation first.

Características Principales

Interactive discovery through focused, one-at-a-time questioning to prevent information overload.
Incremental design validation in 200-300 word sections to ensure alignment at every step.
Automated documentation generation stored directly in the repository's docs/plans directory.
Ruthless YAGNI focus to eliminate unnecessary features and complexity early in the process.
0 GitHub stars
Comparative analysis of 2-3 different architectural approaches with clear trade-offs.

Casos de Uso

Transforming a vague feature request into a concrete technical specification and implementation plan.
Exploring architectural alternatives and trade-offs before committing to a specific stack or pattern.
Documenting complex data flows and component interactions for new repository modules.

Acerca de

Características Principales

Interactive discovery through focused, one-at-a-time questioning to prevent information overload.
Incremental design validation in 200-300 word sections to ensure alignment at every step.
Automated documentation generation stored directly in the repository's docs/plans directory.
Ruthless YAGNI focus to eliminate unnecessary features and complexity early in the process.
0 GitHub stars
Comparative analysis of 2-3 different architectural approaches with clear trade-offs.

Casos de Uso

Transforming a vague feature request into a concrete technical specification and implementation plan.
Exploring architectural alternatives and trade-offs before committing to a specific stack or pattern.
Documenting complex data flows and component interactions for new repository modules.