How is the final design documented?

The skill automatically generates a detailed markdown design document, saves it to your project's documentation folder, and commits it to your git repository.

When should I use the Development Brainstorming skill?

Use it at the start of a project or feature when you have a rough idea but need a concrete technical design, architecture plan, or data flow map before writing code.

How does this skill prevent over-engineering?

It applies the YAGNI (You Ain't Gonna Need It) principle ruthlessly during the brainstorming phase to strip away unnecessary features and complexity.

Does this skill write the actual application code?

No, it is specifically designed for the planning phase. Once the design is validated and documented, it helps you transition to an implementation phase.

Development Brainstorming

Name: Development Brainstorming
Author: Jst-Well-Dan

byJst-Well-Dan

Productividad y Flujo de Trabajo

Refines rough technical ideas into production-ready designs through collaborative questioning and incremental validation.

Acerca de

This skill transforms ambiguous technical concepts into detailed software designs by guiding users through a structured brainstorming process. It avoids the pitfalls of mechanical coding by focusing on architecture, data flow, and trade-off analysis before implementation begins. Through a conversational approach that prioritizes one question at a time and presents multiple architectural options, it ensures that final technical specifications are ruthlessly minimalist, well-documented, and ready for immediate implementation.

Características Principales

Interactive Socratic questioning for iterative design refinement
Comparative analysis of multiple architectural approaches with trade-offs
Automatic design documentation and git-based versioning
Seamless transition to implementation planning and git worktrees
Incremental design validation in digestible 200-300 word sections
0 GitHub stars

Casos de Uso

Planning complex software architecture changes before writing code
Converting high-level product requirements into detailed technical specifications
Evaluating multiple technical approaches for a new feature implementation

Acerca de

Características Principales

Interactive Socratic questioning for iterative design refinement
Comparative analysis of multiple architectural approaches with trade-offs
Automatic design documentation and git-based versioning
Seamless transition to implementation planning and git worktrees
Incremental design validation in digestible 200-300 word sections
0 GitHub stars

Casos de Uso

Planning complex software architecture changes before writing code
Converting high-level product requirements into detailed technical specifications
Evaluating multiple technical approaches for a new feature implementation