How does it help prevent over-engineering?

The skill actively applies YAGNI (You Aren't Gonna Need It) principles, favoring the simplest viable approach and challenging the need for hypothetical future requirements.

When should I use the brainstorming skill?

Use it when requirements are ambiguous, multiple valid solutions exist, or you need to explore technical trade-offs before starting the implementation phase.

What kind of output does this skill generate?

It produces a structured design document stored in your repository at docs/brainstorms/, summarizing the chosen approach, key decisions, and next steps.

Can I skip brainstorming for simple tasks?

Yes. If you have explicit requirements, a detailed spec, or a straightforward bug fix, you can signal Claude to skip brainstorming and proceed directly to planning.

Does this skill write the actual code?

No, this skill focuses on the 'What' and 'Why' of a feature. It creates a design document that serves as the blueprint for the planning and coding phases.

Brainstorming & Design Strategy

Name: Brainstorming & Design Strategy
Author: RBozydar

byRBozydar

0•

Productivity & Workflow

Guides users through structured brainstorming sessions to clarify project requirements and design decisions before implementation.

This skill provides a systematic framework for exploring user intent and evaluating architectural approaches before coding begins. By guiding the conversation through requirement assessment, multi-option exploration, and design documentation, it ensures developers avoid over-engineering and focus on the most effective solutions. It is particularly useful for ambiguous feature requests or complex tasks where trade-offs need explicit validation and documentation.

Key Features

01Automatic generation of persistent design documentation in Markdown

02Seamless handoff to implementation planning and development workflows

03Structured multi-phase process to move from vague ideas to concrete designs

04Comparative analysis of multiple architectural approaches with pros/cons

050 GitHub stars

06YAGNI principle enforcement to prevent premature complexity

Use Cases

01Evaluating technical trade-offs between different implementation strategies

02Clarifying vague or ambiguous feature requests before writing code

03Documenting high-level design decisions for team alignment and future reference

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rbozydar/rbw-claude-code brainstorming

For use in Claude.ai and ChatGPT

Download Skill