brainstorming

Refines ideas into validated designs through structured one-question-at-a-time dialogue.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill brainstorming-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Tgoldi/claude-skills/tree/main/brainstorming
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill brainstorming-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into implementation without clarifying intent leads to wasted effort and misaligned features. This Skill turns vague ideas into fully formed, validated designs and specs through collaborative dialogue before any code is written. ## Core Features & Use Cases - Guided Requirement Discovery: Explores purpose, constraints, and success criteria by asking one question at a time, preferring multiple-choice formats. - Approach Comparison: Proposes 2-3 alternative approaches with trade-offs and a reasoned recommendation. - Incremental Design Validation: Presents the design in 200-300 word sections covering architecture, components, data flow, error handling, and testing, checking each section with you. - Use Case: Before building a new feature, run this Skill to clarify requirements, compare implementation approaches, and produce a committed design document at docs/plans/YYYY-MM-DD-<topic>-design.md. ## Quick Start Ask the assistant to brainstorm and design the new feature you have in mind before writing any code.

Frequently Asked Questions about brainstorming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature idea into a design before coding?

Start a brainstorming session that explores your intent, constraints, and success criteria one question at a time. The process proposes 2-3 approaches with trade-offs, then presents a validated design in small sections covering architecture, data flow, and testing.

What should a software design document include?

A solid design document covers architecture, components, data flow, error handling, and testing. This Skill writes the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md and commits it to git for traceability.

When should I brainstorm requirements before implementation?

Use it before any creative work: creating features, building components, adding functionality, or modifying behavior. Clarifying purpose and success criteria upfront prevents rework from misunderstood requirements.

Does this brainstorming skill write code or just plan?

It only produces the design and documentation. After validation, it optionally hands off to implementation workflows like git worktree setup and detailed implementation plan writing.

What are the limitations of conversational design exploration?

The process depends on your answers, so vague input yields shallow designs. It also defers technical validation to later implementation steps and does not prototype or test actual code.