When should I use the Brainstorming skill?

You should use it before any creative work, such as building new features, modifying core behavior, or starting a new component to ensure requirements are clear.

Does it save the designs it generates?

Yes, it automatically writes validated designs to your project's `docs/plans/` directory with a timestamped filename and commits them to git.

How does this skill handle complex designs?

It breaks complex designs into 200-300 word sections and validates each part with you incrementally to ensure the plan remains accurate and manageable.

Can I jump straight into coding after the brainstorm?

Yes, the skill includes a workflow to transition directly into implementation using git worktrees and detailed implementation plans.

How many approaches does it suggest?

The skill is designed to propose 2-3 different approaches for every design, highlighting the pros and cons of each to help you make an informed decision.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: lastdays03

bylastdays03

Productivity & Workflow

Transforms raw ideas into structured design specifications and technical plans through a guided, step-by-step collaborative dialogue.

About

The Brainstorming skill provides a structured framework for the ideation phase of development, ensuring that user intent is fully understood before a single line of code is written. By employing Socratic questioning, comparative trade-off analysis, and incremental design validation, it helps developers explore multiple architectural approaches and ruthlessly eliminate unnecessary features. Once a consensus is reached, the skill automatically generates standardized design documentation, commits it to the repository, and prepares the environment for seamless implementation using git worktrees.

Key Features

0 GitHub stars
Comparative analysis of 2-3 distinct technical approaches with trade-offs.
Seamless transition from design to implementation with git worktree integration.
Guided Socratic questioning to refine requirements one step at a time.
Incremental design validation in small, digestible sections.
Automated Markdown documentation generation for technical specs.

Use Cases

Refining a vague feature request into a concrete architectural plan.
Evaluating different libraries or data flow patterns before building a new component.
Generating standardized technical documentation for team-wide design reviews.

About

Key Features

0 GitHub stars
Comparative analysis of 2-3 distinct technical approaches with trade-offs.
Seamless transition from design to implementation with git worktree integration.
Guided Socratic questioning to refine requirements one step at a time.
Incremental design validation in small, digestible sections.
Automated Markdown documentation generation for technical specs.

Use Cases

Refining a vague feature request into a concrete architectural plan.
Evaluating different libraries or data flow patterns before building a new component.
Generating standardized technical documentation for team-wide design reviews.