Does it automatically document the design?

Yes, once a design is validated, the skill writes the specification to a dated Markdown file in your docs folder and commits it to Git.

How does this skill help avoid scope creep?

It ruthlessly applies the YAGNI principle during the design phase and requires user validation of each section before proceeding further.

How does the validation process work?

Instead of presenting a massive document, it breaks the design into 200-300 word sections and asks for your approval after each one.

When should I use the Brainstorming skill?

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

Can it help me choose between different technologies?

Absolutely. The skill is designed to propose 2-3 different approaches with specific trade-offs and provide a recommendation based on your project's context.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: eyadsibai

byeyadsibai

Productivity & Workflow

Transforms abstract ideas into validated technical specifications through structured dialogue and incremental validation.

About

The Brainstorming skill is a pre-implementation framework designed to align user intent with technical reality before coding begins. It guides the interaction through a disciplined process of one-at-a-time questioning, exploration of multiple architectural approaches, and modular design presentation. By enforcing 'YAGNI' (You Ain't Gonna Need It) principles and requiring incremental validation of design sections, it ensures that every feature is necessary and well-architected. The skill concludes by automatically documenting the agreed-upon design and committing it to the repository, creating a clear audit trail for the development lifecycle.

Key Features

Structured incremental questioning to prevent information overload
Bite-sized design validation sessions (200-300 words per section)
Multi-approach proposals with detailed trade-offs and recommendations
Integrated handoff to implementation via git worktrees and writing plans
0 GitHub stars
Automatic Markdown documentation and Git commits for design specs

Use Cases

Enforcing architectural consistency and YAGNI principles in new modules
Evaluating multiple implementation strategies before committing to code
Refining vague feature requests into concrete, documented technical architectures

About

Key Features

Structured incremental questioning to prevent information overload
Bite-sized design validation sessions (200-300 words per section)
Multi-approach proposals with detailed trade-offs and recommendations
Integrated handoff to implementation via git worktrees and writing plans
0 GitHub stars
Automatic Markdown documentation and Git commits for design specs

Use Cases

Enforcing architectural consistency and YAGNI principles in new modules
Evaluating multiple implementation strategies before committing to code
Refining vague feature requests into concrete, documented technical architectures