Where are the design documents saved?

Validated designs are automatically written to your repository in the `docs/plans/` directory with standardized naming conventions and committed to Git.

Does this skill write implementation code?

No, it is a pre-implementation skill focused on design and specifications. However, it provides a direct hand-off to implementation planning skills once the design is validated.

When should I use the Brainstorming skill?

Use this skill at the very beginning of a project or feature development phase, specifically before any code is written, to ensure a solid architectural foundation.

How does it help avoid over-engineering?

The skill follows the YAGNI (You Ain't Gonna Need It) principle, intentionally identifying and removing unnecessary features during the design phase.

Collaborative Brainstorming & Design

Name: Collaborative Brainstorming & Design
Author: seanGSISG

byseanGSISG

Productivity & Workflow

Refines rough concepts into production-ready technical designs through structured dialogue and incremental validation.

About

This skill transforms abstract ideas into concrete technical specifications by engaging the user in a collaborative discovery process. Instead of rushing to code, it systematically explores project requirements, evaluates multiple architectural approaches, and produces detailed design documentation. It ensures clarity through iterative questioning and section-by-section validation, ultimately generating a formal design document in your repository that seamlessly transitions into implementation planning.

Key Features

Iterative discovery process using one-question-at-a-time to prevent information overload
Incremental design presentation with validation checkpoints every 200-300 words
Automatic generation of standardized design documents committed directly to Git
Direct integration with research subagents and implementation planning workflows
0 GitHub stars
Comparative analysis of 2-3 architectural approaches with explicit trade-offs and recommendations

Use Cases

Creating standardized design documentation for team reviews and long-term project history
Architecting a new feature from a vague user request or high-level concept
Evaluating different technical solutions and trade-offs before starting the implementation phase

About

Key Features

Iterative discovery process using one-question-at-a-time to prevent information overload
Incremental design presentation with validation checkpoints every 200-300 words
Automatic generation of standardized design documents committed directly to Git
Direct integration with research subagents and implementation planning workflows
0 GitHub stars
Comparative analysis of 2-3 architectural approaches with explicit trade-offs and recommendations

Use Cases

Creating standardized design documentation for team reviews and long-term project history
Architecting a new feature from a vague user request or high-level concept
Evaluating different technical solutions and trade-offs before starting the implementation phase