brainstorming

Guide teams through structured brainstorming to produce design documentation.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/mortenbroesby/playground --skill brainstorming-mortenbroesby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/mortenbroesby/playground/tree/main/.skills/brainstorming
Command: npx skills add https://github.com/mortenbroesby/playground --skill brainstorming-mortenbroesby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Brainstorming helps teams surface intent, requirements, constraints, and success criteria before committing to concrete design or implementation, reducing risk and rework.

Core Features & Use Cases

  • Structured project-context exploration: identify goals, stakeholders, and success metrics to align on scope.
  • Guided questioning and design framing: clarify constraints, assumptions, and user needs through iterative dialogue.
  • Propose 2-3 approaches: present trade-offs and recommendations to accelerate decision-making and alignment.

Quick Start

Initiate a guided ideation session by clarifying goals, constraints, and success criteria before proposing designs.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I align cross-functional teams on project scope and constraints before starting design?

Structured project-context exploration identifies goals, stakeholders, and success metrics to align cross-functional teams on scope and constraints before design begins.

What is the best way to evaluate multiple design approaches during early-stage ideation?

Evaluating multiple design approaches during early-stage ideation involves proposing 2-3 options, presenting trade-offs, and providing recommendations to accelerate team decision-making and alignment.

How do I clarify assumptions and user needs through iterative dialogue before committing to implementation?

Guided questioning and design framing clarify assumptions, constraints, and user needs through iterative dialogue to surface intent and reduce rework before implementation.

When do I need formal design documentation for feature exploration?

Formal design documentation for feature exploration is needed when teams require a guided process to explore context, ask clarifying questions, propose approaches, and generate a design doc to guide implementation.

Does structured brainstorming work for early-stage ideas and design decisions across cross-functional teams?

Structured brainstorming applies to early-stage ideas, feature exploration, and design decisions across cross-functional teams by enabling structured inquiry and multiple approach options.

What are the limitations of starting design or development without surfacing intent and requirements?

Starting design or development without surfacing intent, requirements, constraints, and success criteria increases risk and rework, which structured inquiry and formal design documentation mitigate.