Can I return to an earlier phase if my requirements change?

Yes, the skill is designed for non-linear progression. You can move back to the Understanding or Exploration phases at any time if new constraints are discovered.

When should I use the Brainstorming skill?

Activate this skill at the very start of a project or feature when requirements are high-level, or when you need to compare multiple technical approaches before writing code.

Does this skill provide implementation code?

This skill specifically focuses on the design and validation phase. Once the design is finalized and validated, you can then proceed to implementation tasks.

How are architectural trade-offs presented?

The skill typically proposes 2-3 different approaches and presents them in a structured table format, comparing pros, cons, and implementation complexity.

How does the Socratic questioning process work?

The skill asks one focused question at a time to uncover purpose, constraints, and success criteria, ensuring you aren't overwhelmed by information requests.

Brainstorming & Design

Name: Brainstorming & Design
Author: yonatangross

byyonatangross

•

Productivity & Workflow

Transforms rough project ideas into fully-formed architectural designs through structured Socratic questioning and multi-path exploration.

About

This skill provides a systematic framework for the pre-coding phase of software development, turning vague 'I have an idea' prompts into actionable technical specifications. By guiding users through a disciplined three-phase process—Understanding, Exploration, and Presentation—it ensures that project goals, constraints, and success criteria are fully defined before implementation begins. The skill excels at identifying hidden requirements and presenting multiple architectural approaches with clear trade-off comparisons, helping developers avoid over-engineering while ensuring the chosen solution aligns perfectly with the intended outcome.

Key Features

Integrated decision tools for selecting between mutually exclusive technical options.
Multi-path architectural exploration with detailed trade-off matrices.
2 GitHub stars
Structured Socratic questioning to uncover purpose and technical constraints.
Incremental design validation in digestible 200-300 word sections.
Non-linear workflow that adapts as new project requirements emerge.

Use Cases

Converting high-level feature requests into detailed system architectures.
Evaluating trade-offs between different technologies like WebSockets vs. SSE.
Refining vague requirements into structured implementation plans.

About

Key Features

Integrated decision tools for selecting between mutually exclusive technical options.
Multi-path architectural exploration with detailed trade-off matrices.
2 GitHub stars
Structured Socratic questioning to uncover purpose and technical constraints.
Incremental design validation in digestible 200-300 word sections.
Non-linear workflow that adapts as new project requirements emerge.

Use Cases

Converting high-level feature requests into detailed system architectures.
Evaluating trade-offs between different technologies like WebSockets vs. SSE.
Refining vague requirements into structured implementation plans.