brainstorming

Structure vague ideas into design directions through guided one-question-at-a-time sessions.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/csim-sg/yacc --skill brainstorming-csim-sg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/csim-sg/yacc/tree/main/.opencode/skills/brainstorming
Command: npx skills add https://github.com/csim-sg/yacc --skill brainstorming-csim-sg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps transform ambiguous ideas into concrete design directions, aligning stakeholders and reducing ambiguity early in the product process.

Core Features & Use Cases

  • Guided ideation: structure conversations to surface core requirements, constraints, and success criteria.
  • Approach exploration: propose 2-3 viable design options with trade-offs.
  • Incremental design delivery: present designs in sections for validation and iteration.

Quick Start

Describe the project goal and constraints, then guide the session with a single focused question at a time to refine ideas.

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 structured design directions?

To turn vague ideas into structured design directions, describe your project goal and constraints to start a guided ideation session that surfaces core requirements, proposes 2-3 viable approaches with trade-offs, and delivers incremental sections for validation.

What is the best way to scope early-stage project requirements and refine ideas?

The best way to scope early-stage project requirements is through a one-question-at-a-time process that structures conversations, aligns stakeholders, and reduces ambiguity by validating success criteria incrementally.

How does guided ideation help with software and product design planning?

Guided ideation helps with software and product design planning by enforcing a focused, single-question process that explores multiple design options with trade-offs, ensuring stakeholders validate requirements before committing to a direction.

Can I use this approach for both product and services design thinking?

Yes, you can use this approach for both product and services design thinking because it applies broadly to early-stage ideation, project scoping, and requirements refinement across software, product, and service domains.

Why propose multiple design approaches with trade-offs during brainstorming?

Proposing multiple design approaches with trade-offs during brainstorming allows stakeholders to compare viable options, validate constraints, and select the most suitable design direction before moving into detailed implementation.

What are the limitations of a one-question-at-a-time brainstorming process?

A limitation of the one-question-at-a-time brainstorming process is that it enforces incremental validation, which may slow down initial scoping but ensures structured, actionable design directions and reduces early ambiguity.