brainstorming

Organize raw ideas into actionable design concepts with structured inquiry.

Updated Mar 16, 2026

Search Tags:#design #brainstorming #ideation #requirements #exploration #spec-review

Ready to run

npx skills add https://github.com/thmspi/claude-setup --skill brainstorming-thmspi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming sessions are essential to clarify goals, uncover requirements, and set the direction for design work before any coding or building starts. This skill provides a structured, collaborative dialogue to surface user intents, constraints, and success criteria, mitigating scope creep and misalignment.

Core Features & Use Cases

Structured inquiry: guides a single, focused conversation to gather context, questions, and acceptance criteria.
Multi-approach ideation: proposes 2-3 design directions with trade-offs and recommended path.
Documentation handoff: creates a design doc blueprint and supports a spec-review loop to align stakeholders.

Quick Start

Begin by clarifying the project goals and context, then generate 2–3 design directions for review and refinement.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn raw product ideas into actionable design concepts?▼

To turn raw ideas into actionable design concepts, you need a structured ideation process that applies iterative questioning to clarify goals. This surfaces user intents and constraints early, producing clear design documentation before implementation.

What is the best way to define project scope during early feature exploration?▼

The best way to define project scope during early feature exploration is through structured inquiry that uncovers requirements and acceptance criteria. Generating 2-3 design directions with documented trade-offs ensures stakeholders align on a recommended path before building.

How do I document design directions and run a spec-review loop?▼

Documenting design directions involves creating a design doc blueprint that captures proposed approaches and trade-offs. This supports a structured spec-review loop to gather stakeholder feedback and refine the scope iteratively for reviewable outputs.

Does structured ideation help prevent scope creep in product design?▼

Structured ideation helps prevent scope creep by clarifying goals and success criteria before any coding starts. It provides a focused conversation to surface constraints, ensuring all stakeholders align on the final design direction.

When do I need a brainstorming workflow for design documentation?▼

You need a brainstorming workflow for design documentation when starting early product exploration or feature ideation. It is required to organize raw ideas into clear, reviewable outputs and define acceptance criteria prior to implementation.