brainstorming

Transform vague ideas into concrete design concepts through structured inquiry.

66|20|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/cooker/wxHm --skill brainstorming-cooker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/cooker/wxHm/tree/main/.cursor/skills/brainstorming
Command: npx skills add https://github.com/cooker/wxHm --skill brainstorming-cooker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming transforms vague ideas into concrete design concepts, reducing ambiguity early and aligning stakeholders.

Core Features & Use Cases

  • Structured inquiry that guides teams to articulate goals, constraints, and acceptance criteria.
  • Incremental design that splits ideas into 200-300 word sections, with validation after each section.
  • Collaborative planning that proposes 2-3 design approaches with trade-offs and a recommended path.
  • Documentation handoff that produces clear design write-ups suitable for plans, specs, and implementation.

Quick Start

Begin by framing the idea with a targeted clarifying question, then draft the design in successive 200-300 word sections, covering architecture, components, data flow, error handling, and testing. After each section, confirm alignment before proceeding.

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 concrete design plans?

To turn vague ideas into concrete design plans, use structured inquiry to articulate goals and constraints, then draft design sections iteratively with validation after each part. This reduces ambiguity early and aligns stakeholders before implementation.

What is the best way to document requirements during early-stage feature planning?

Document requirements during feature planning by splitting ideas into 200-300 word sections covering architecture, components, data flow, error handling, and testing. Confirm alignment after each section to produce clear design write-ups suitable for specs.

How does structured ideation work for cross-team design sessions?

Structured ideation for cross-team design sessions works by guiding one-question-at-a-time exploration. It proposes 2-3 design approaches with trade-offs and a recommended path, ensuring all stakeholders articulate goals and acceptance criteria clearly.

Can I use this approach to create formal design handoff documentation?

Yes, you can create formal design handoff documentation by drafting successive 200-300 word sections that cover architecture, components, data flow, error handling, and testing. The output produces clear write-ups suitable for plans and implementation specs.

Do I need specific architecture frameworks to start brainstorming design concepts?

No specific architecture frameworks are required to start brainstorming design concepts. You begin by framing the idea with a targeted clarifying question to define goals, constraints, and acceptance criteria before drafting the architecture sections.