When should I use the Brainstorming skill?

Use it when you have a rough idea but the implementation is unclear, when multiple approaches exist and you need to choose, or when requirements are fuzzy.

How does the validation process work?

The skill presents designs in small, manageable sections (architecture, data flow, error handling) and asks for validation after each section to catch misunderstandings early.

How does this skill help avoid over-engineering?

It strictly applies the YAGNI (You Ain't Gonna Need It) principle during the design phase and forces a comparison of trade-offs to find the simplest viable solution.

Does it create documentation automatically?

Yes, once a design is validated, the skill writes a concise design document to your repository and commits it to Git for tracking.

Can I use it for simple bug fixes?

No, it is recommended to skip this skill for clear mechanical tasks or well-defined standard implementations to maintain workflow speed.

Brainstorming & Design Planner

Name: Brainstorming & Design Planner
Author: Light-Brands

byLight-Brands

Productivity & Workflow

Transforms rough conceptual ideas into structured technical designs through interactive dialogue and incremental validation.

About

The Brainstorming skill facilitates natural collaborative sessions to refine fuzzy requirements into fully-formed implementation plans. It prevents over-engineering by applying YAGNI principles, explores multiple architectural approaches with clear trade-offs, and validates designs incrementally to ensure alignment before any code is written. By guiding the user through a structured one-question-at-a-time dialogue and documenting final decisions in Git-tracked design files, it ensures that implementation is based on solid architectural foundations rather than assumptions.

Key Features

Comparative analysis of multiple architectural approaches with transparent trade-offs.
Incremental validation through focused, one-question-at-a-time dialogue.
Automated generation of Git-tracked design documentation in markdown format.
Structured transition from high-level design to concrete, actionable implementation tasks.
0 GitHub stars
Ruthless YAGNI-focused planning to eliminate unnecessary feature creep.

Use Cases

Mapping out data flow and state management for a new system component before writing code.
Evaluating whether to use an event-driven architecture versus direct integration for a new feature.
Clarifying ambiguous requirements and constraints before starting a complex refactoring project.

About

Key Features

Comparative analysis of multiple architectural approaches with transparent trade-offs.
Incremental validation through focused, one-question-at-a-time dialogue.
Automated generation of Git-tracked design documentation in markdown format.
Structured transition from high-level design to concrete, actionable implementation tasks.
0 GitHub stars
Ruthless YAGNI-focused planning to eliminate unnecessary feature creep.

Use Cases

Mapping out data flow and state management for a new system component before writing code.
Evaluating whether to use an event-driven architecture versus direct integration for a new feature.
Clarifying ambiguous requirements and constraints before starting a complex refactoring project.