brainstorming

Guide teams through structured ideation and design planning before implementation.

Updated Jan 27, 2026

Search Tags:#documentation #brainstorming #collaboration #ideation #requirements #trade-offs #design-planning

Ready to run

npx skills add https://github.com/dtheran1/convocatorias_unal --skill brainstorming-dtheran1

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming is a structured pre-design activity that helps align goals, constraints, and success criteria before building features, ensuring every creative decision starts from a clear intent.

Core Features & Use Cases

Guided discovery: asks one focused question at a time to uncover user needs and project constraints.
Options generation: presents 2-3 design approaches with trade-offs to support informed decisions.
Incremental validation: presents design sections in small chunks and checks alignment after each.
Documentation planning: creates a plan for later design and implementation.

Quick Start

Initiate a focused brainstorming session by outlining the project context, success criteria, and constraints, then generate 2–3 design approaches and validate them in short sections.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn early-stage product ideas into design-ready specs?▼

Structured brainstorming turns ideas into design-ready specs by guiding teams through incremental validation, generating 2-3 design approaches with trade-offs, and capturing requirements before implementation.

What is the best way to capture project constraints and requirements before implementation?▼

The best way to capture requirements before implementation is through guided discovery, which asks one focused question at a time to uncover user needs, clarify context, and enforce alignment across cross-functional design sessions.

How do I generate and compare design approaches during ideation?▼

Design ideation generates 2-3 approaches with explicit trade-offs, presenting them in small chunks to validate decisions incrementally and support informed choices before finalizing design documentation.

Does structured design planning work for early-stage feature exploration?▼

Yes, structured design planning is built for early-stage feature exploration, applying one-question-at-a-time interaction to clarify goals, constraints, and success criteria before any building begins.

How do I ensure alignment and traceability during cross-functional design sessions?▼

Alignment and traceability are ensured by presenting design sections in small chunks and checking agreement after each step, creating an incremental design documentation plan for later implementation.

When should I not use structured brainstorming for product development?▼

Structured brainstorming should be avoided when implementation is already underway or when a project requires rapid, undocumented prototyping rather than upfront requirements capture, trade-off analysis, and incremental validation.