When should I use the brainstorming skill?

Use it at the start of a new feature or project to refine rough ideas into clear designs and specs before you begin writing implementation code.

How does it help with architectural decision-making?

The skill proposes 2-3 different technical approaches with specific trade-offs and recommendations, helping you choose the path that fits your constraints.

What is the benefit of incremental validation?

By presenting the design in small sections (200-300 words), it ensures you and the AI are aligned at every step, preventing large-scale misunderstandings.

Does this skill generate the final implementation code?

It focuses on the design and documentation phase. Once a design is validated, it can hand off to other skills to create implementation plans and code.

Where are the design documents stored?

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

AI Brainstorming & Design

Name: AI Brainstorming & Design
Author: dsifry

bydsifry

•

Productivity & Workflow

Refines raw ideas into technical specifications and architectural designs through iterative questioning and collaborative feedback.

About

The Brainstorming skill transforms ambiguous concepts into production-ready designs by facilitating a structured, conversational planning process. It prevents the friction of starting new features by analyzing existing project context, exploring multiple architectural approaches with trade-offs, and incrementally validating design sections to ensure alignment with your goals. By emphasizing one-at-a-time questioning and ruthless adherence to YAGNI principles, it helps developers build lean, well-documented systems before a single line of code is written.

Key Features

Incremental design validation in bite-sized sections
Automatic technical documentation and Git integration
Iterative, single-question dialogue to avoid information overload
Context-aware project analysis and discovery
Comparative architectural trade-off analysis for multiple approaches
29 GitHub stars

Use Cases

Fleshing out a new feature idea into a technical specification
Converting vague product requirements into detailed implementation plans
Evaluating different architectural approaches for a complex problem

About

Key Features

Incremental design validation in bite-sized sections
Automatic technical documentation and Git integration
Iterative, single-question dialogue to avoid information overload
Context-aware project analysis and discovery
Comparative architectural trade-off analysis for multiple approaches
29 GitHub stars

Use Cases

Fleshing out a new feature idea into a technical specification
Converting vague product requirements into detailed implementation plans
Evaluating different architectural approaches for a complex problem