Does it automatically save the designs?

Yes, once a design is validated, it writes a detailed document to your project's docs folder and commits it to git.

Does it help with the actual coding phase?

While it focuses on design, it can transition you to implementation by setting up git worktrees and creating detailed implementation plans.

How does this skill handle design presentations?

It presents designs in small sections of 200-300 words, checking for your approval after each section to ensure the direction is correct.

Why does it only ask one question at a time?

This incremental approach prevents information overload and ensures each specific aspect of the requirement is fully understood before moving on.

When should I use the brainstorming skill?

You should use it before starting any creative work, such as building new features or modifying behavior, to explore intent and requirements first.

Collaborative Design Brainstorming

Name: Collaborative Design Brainstorming
Author: julianromli

byjulianromli

•

101

Productivity & Workflow

Transforms initial ideas into detailed technical specifications through structured dialogue and incremental validation.

About

This skill facilitates a collaborative discovery process that ensures technical designs are fully vetted before implementation begins. By asking targeted questions, exploring multiple architectural approaches, and presenting designs in digestible segments, it helps developers align on requirements, avoid feature creep through YAGNI principles, and produce high-quality documentation. It bridges the gap between a vague concept and a concrete implementation plan, ensuring that every design choice is intentional and documented.

Key Features

Seamless transition to implementation planning and git worktree setup
Comparative analysis of 2-3 distinct architectural approaches with trade-off discussions
Interactive requirements gathering via targeted, one-at-a-time questioning
Incremental design presentation for continuous user validation and feedback
101 GitHub stars
Automatic generation of structured technical design documents in Markdown format

Use Cases

Refining vague user requirements into actionable technical specifications
Documenting complex system changes for team review and compliance
Architecting new features or complex components from scratch

About

Key Features

Seamless transition to implementation planning and git worktree setup
Comparative analysis of 2-3 distinct architectural approaches with trade-off discussions
Interactive requirements gathering via targeted, one-at-a-time questioning
Incremental design presentation for continuous user validation and feedback
101 GitHub stars
Automatic generation of structured technical design documents in Markdown format

Use Cases

Refining vague user requirements into actionable technical specifications
Documenting complex system changes for team review and compliance
Architecting new features or complex components from scratch