How does the Brainstorming skill help prevent over-engineering?

The skill ruthlessly applies YAGNI (You Ain't Gonna Need It) principles during the design phase and forces an exploration of multiple approaches to ensure the simplest effective solution is chosen.

Where are the design documents stored?

Validated designs are automatically written to your repository in the docs/plans/ directory using a standardized YYYY-MM-DD-topic-design.md format.

Why does the skill only ask one question at a time?

This incremental approach prevents cognitive overload and ensures that every constraint and requirement is clearly defined before the design is presented.

Does this skill integrate with implementation workflows?

Yes, once a design is finalized and committed, the skill can trigger implementation planning using git worktrees and detailed task breakdowns.

Can it handle existing projects or only new ones?

It is designed for both; it begins every session by analyzing your current project state, including files, documentation, and recent commits, to ensure designs are contextually relevant.

Brainstorming & Design Specification

Name: Brainstorming & Design Specification
Author: BbgnsurfTech

byBbgnsurfTech

•

生産性とワークフロー

Transforms abstract ideas into detailed technical specifications through a structured, iterative dialogue and trade-off analysis.

This skill facilitates a collaborative design process between the developer and Claude to ensure features are fully thought out before implementation begins. It guides users through project context discovery, explores multiple architectural approaches with pros and cons, and validates designs incrementally in small, digestible sections. By enforcing a 'one question at a time' rule and adhering to YAGNI principles, it eliminates ambiguity and over-engineering, resulting in a finalized, documented design plan committed directly to your repository.

主な機能

01Context-aware discovery via project file and history analysis

02Iterative questioning to refine intent without overwhelming the user

03Automated documentation generation and Git commitment of design specs

04Incremental design validation in 200-300 word sections

05Comparative analysis of 2-3 technical approaches with trade-offs

063 GitHub stars

ユースケース

01Converting high-level requirements into actionable technical documentation

02Architecting a new feature or complex component from scratch

03Refactoring existing functionality by exploring alternative implementation patterns

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add bbgnsurftech/claude-skills-collection brainstorming

For use in Claude.ai and ChatGPT

Download Skill