How does it help with architectural decisions?

The skill is programmed to propose 2-3 different technical approaches for any given problem, highlighting the trade-offs of each to help you choose the best path.

Why does this skill only ask one question at a time?

To prevent information overload and ensure that every requirement is thoroughly explored and understood before moving to the next phase of the design.

Does this skill write implementation code?

Its primary focus is on planning and design, but it includes a post-design workflow that uses other tools to set up isolated git worktrees for implementation.

What principles does the brainstorming skill follow?

It follows principles of incremental validation, ruthless YAGNI (You Aren't Gonna Need It) to avoid bloat, and flexibility in clarifying requirements.

Where are the design documents stored?

Designs are automatically written to your repository in the docs/plans/ folder with a standardized naming convention and committed to git for versioning.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: Cygnusfear

byCygnusfear

Productivity & Workflow

Transforms vague ideas into detailed technical specifications through a structured, collaborative dialogue process.

About

The Brainstorming skill is a specialized capability designed to prevent premature implementation by forcing a disciplined discovery phase. It guides Claude to understand project context, ask targeted questions one at a time, and explore multiple architectural trade-offs before a single line of feature code is written. By breaking down complex designs into digestible sections for incremental validation and automatically documenting the results in git-tracked plan files, it ensures that developers and AI are perfectly aligned on requirements and constraints.

Key Features

Seamless transition from design to implementation via git worktrees
Comparative analysis of multiple technical approaches and trade-offs
Automated documentation generation in docs/plans/ directory
Structured requirements gathering via single-topic focused questioning
Incremental design validation in small, readable segments
0 GitHub stars

Use Cases

Architecting a new feature from a high-level concept
Evaluating different implementation strategies for a specific component
Documenting technical specifications before starting a complex refactor

About

Key Features

Seamless transition from design to implementation via git worktrees
Comparative analysis of multiple technical approaches and trade-offs
Automated documentation generation in docs/plans/ directory
Structured requirements gathering via single-topic focused questioning
Incremental design validation in small, readable segments
0 GitHub stars

Use Cases

Architecting a new feature from a high-level concept
Evaluating different implementation strategies for a specific component
Documenting technical specifications before starting a complex refactor