brainstorming

Convert raw ideas into concrete design specifications with structured refinement.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/shynlee04/idumb-plugin --skill brainstorming-shynlee04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/shynlee04/idumb-plugin/tree/main/.agents/skills/brainstorming
Command: npx skills add https://github.com/shynlee04/idumb-plugin --skill brainstorming-shynlee04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming converts raw ideas into concrete design specifications to reduce ambiguity and rework.

Core Features & Use Cases

  • Understand the idea and project context before designing.
  • Explore 2-3 viable design approaches with trade-offs.
  • Present designs in incremental sections and validate with stakeholders.

Quick Start

Analyze the current project state and begin with one clarifying question to guide the design direction.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I turn raw project ideas into actionable design specifications?

Converting raw ideas into actionable design specifications requires assessing project context, refining scope through iterative questioning, and exploring multiple design approaches with trade-offs before finalizing a plan.

What is the best way to reduce ambiguity and rework during project discovery?

Reducing ambiguity during project discovery involves enforcing a structured brainstorming process that builds up-front understanding and validates incremental design sections with stakeholders before implementation begins.

How does structured brainstorming guide context assessment for new design tasks?

Structured brainstorming guides context assessment by analyzing the current project state and asking one clarifying question at a time to direct the ideation and design-planning workflow.

Can I explore multiple design approaches with trade-offs before starting development?

Yes, you can explore 2-3 viable design approaches with explicit trade-offs to ensure stakeholders validate the incremental design delivery and finalize requirements before development.

When do I need a structured ideation process for design planning?

You need a structured ideation process for design planning when starting project discovery tasks that require converting ambiguous concepts into concrete documentation to guide development.

Why should design documentation be produced as a plan before implementation?

Producing design documentation as a plan before implementation enforces up-front understanding and stakeholder validation, converting raw ideas into concrete specifications to reduce rework.