brainstorming

Refine rough ideas into design sections with one-question-at-a-time dialogue.

Updated Aug 27, 2026

Search Tags:#design #collaboration #brainstorm #incremental-design #design-thinking #rapid-prototyping #question-led

Ready to run

npx skills add https://github.com/czottmann/claude-code-stuff --skill brainstorming-czottmann

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/czottmann/claude-code-stuff/tree/main/skills/brainstorming
Command: npx skills add https://github.com/czottmann/claude-code-stuff --skill brainstorming-czottmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn rough ideas into fully formed designs through guided, one-question-at-a-time collaboration. Writing code is not part of brainstorming; the goal is to converge on a solid design before implementation.

Core Features & Use Cases

Guided questioning: Ask one clarifying question per message to refine scope.
Multiple approaches: Propose 2-3 design options with trade-offs.
Incremental design: Present the design in small sections (200-300 words) and validate step by step.

Quick Start

Start by describing the project context, then respond with a single clarifying question. After receiving input, present the next section of the design and ask for feedback.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I refine rough ideas into a solid design before coding?▼

Brainstorming turns rough ideas into fully formed designs through guided, one-question-at-a-time collaboration. It applies during early project ideation to refine purpose, constraints, and success criteria by exploring 2-3 design approaches incrementally, with design sections presented in 200–300 words, before any implementation begins.

What's the best way to structure collaborative design sessions?▼

Structure design sessions by asking one clarifying question per message to refine scope, then present the next design section and request feedback. This incremental approach validates assumptions step by step and converges on a solid design through dialogue rather than jumping directly to code.

How do I explore multiple design approaches before committing to one?▼

Present 2-3 design options with explicit trade-offs, then gather feedback on each approach. This comparative exploration during brainstorming reduces rework later and ensures the team aligns on purpose, constraints, and success criteria before implementation.

Can I use brainstorming to define project scope and constraints?▼

Yes. Brainstorming explicitly refines project purpose, constraints, and success criteria through guided questioning. It prevents scope creep by establishing these boundaries before design and code work begin, linking validated designs to issue-tracking artifacts for clarity.

Why should I avoid writing code during the design phase?▼

Writing code during brainstorming shifts focus from problem-solving to implementation details. Prohibiting code changes enforces one-question-at-a-time dialogue and keeps the team converged on design validation—preventing costly rework once coding begins.

How do I validate designs incrementally without building a prototype?▼

Present design sections of 200–300 words and ask for feedback on each part. This incremental validation lets teams converge on a solid design through dialogue, identifying misalignments early without prototype code or full implementation.