Where are the resulting designs stored?

Validated designs are written to the plans/ directory as Markdown files and automatically committed to your git repository for tracking.

Does it write code immediately?

No, it is specifically designed for the 'pre-code' phase to ensure the design is sound and all stakeholders agree on the approach before implementation starts.

How does it prevent over-engineering?

The skill ruthlessly applies YAGNI (You Ain't Gonna Need It) principles to strip away unnecessary features and focuses on the most efficient path to success.

What does the brainstorm-ideas skill do?

It facilitates a collaborative dialogue to refine raw ideas into structured software designs, architecture plans, and formal documentation before you start coding.

Collaborative Idea Architect

Name: Collaborative Idea Architect
Author: mixomat

bymixomat

Productivity & Workflow

Refines rough concepts into fully-formed technical designs through iterative questioning, trade-off analysis, and incremental validation.

About

The brainstorm-ideas skill transforms vague project concepts into structured software specifications by engaging users in a natural, collaborative dialogue. It prevents premature implementation by first understanding project context, exploring multiple architectural approaches, and validating designs section-by-section. By applying YAGNI principles and formalizing outcomes into version-controlled design documents, it ensures that developers have a clear, validated roadmap and high-level consensus before a single line of production code is written.

Key Features

Comparative analysis of 2-3 architectural approaches with clear trade-offs
Strict adherence to YAGNI principles to eliminate unnecessary feature creep
Incremental design presentation with sectional validation checkpoints
0 GitHub stars
Context-aware questioning to uncover project constraints and success criteria
Automatic generation of timestamped Markdown design documentation

Use Cases

Refining a vague product idea into a concrete technical specification
Defining the system architecture for a new microservice or feature
Evaluating different implementation strategies for complex logic before coding

About

Key Features

Comparative analysis of 2-3 architectural approaches with clear trade-offs
Strict adherence to YAGNI principles to eliminate unnecessary feature creep
Incremental design presentation with sectional validation checkpoints
0 GitHub stars
Context-aware questioning to uncover project constraints and success criteria
Automatic generation of timestamped Markdown design documentation

Use Cases

Refining a vague product idea into a concrete technical specification
Defining the system architecture for a new microservice or feature
Evaluating different implementation strategies for complex logic before coding