brainstorming

Convert vague concepts into structured design plans through guided questioning.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/baskarajati/undangan --skill brainstorming-baskarajati
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/baskarajati/undangan/tree/main/.agent/skills/brainstorming
Command: npx skills add https://github.com/baskarajati/undangan --skill brainstorming-baskarajati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming and early design often stall because ideas are vague and unstructured. This skill guides a one-question-at-a-time exploration to rapidly transform raw ideas into a concrete design plan with defined goals and success criteria.

Core Features & Use Cases

  • Guided Q&A: proceeds one question at a time to precisely elicit requirements and constraints.
  • Multi-approach design: proposes 2-3 viable design or feature approaches with trade-offs.
  • Incremental design delivery: outputs design in small sections (200-300 words) for iterative review and validation.
  • Documentation: generates a concise plan or design doc after the exploration session.

Quick Start

Share the current project context and constraints, then begin with a single question and proceed iteratively.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn vague product ideas into a structured design plan?▼

Guided brainstorming transforms vague ideas into a structured design plan by asking one question at a time to identify constraints, proposing multiple approaches, and delivering incremental sections for review.

What is the best way to conduct collaborative ideation for product features?▼

Collaborative ideation for product features works best through iterative questioning that explores constraints, proposes 2-3 viable approaches with trade-offs, and generates a concise design doc for validation.

How do I start a brainstorming session to define technical requirements and constraints?▼

Start defining technical requirements by sharing your current project context and constraints, then proceed iteratively with one question at a time to refine the design approaches and validate goals.

Can I use guided brainstorming for both user experience and technical design approaches?▼

Yes, guided brainstorming applies to user experience and technical design approaches across multiple projects, using incremental delivery to produce sectioned, review-ready outputs for validation.

Does this ideation method output a full design document immediately?▼

No, this ideation method delivers design outputs incrementally in small 200-300 word sections for iterative review, ultimately generating a concise plan or design document after the exploration session.

Why should I use a one-question-at-a-time approach for requirements gathering?▼

A one-question-at-a-time approach for requirements gathering prevents early design stalls by precisely eliciting constraints and validating ideas incrementally before producing a final design plan.