brainstorming

Coordinate structured brainstorming to convert vague ideas into actionable design directions.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill brainstorming-conradmaker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/brainstorming
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill brainstorming-conradmaker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming helps teams move from vague ideas to concrete decisions quickly by providing a lightweight, structured process with guardrails.

Core Features & Use Cases

  • Structured steps (Discover, Propose, Converge, Capture) to move from idea to direction while maintaining speed.
  • Up to 3 clarifying questions to align intent and constraints before proposing options.
  • Two recommended directional options with trade-offs to accelerate decision-making.
  • Clear capture of decisions and rationale as human-readable notes for accountability.

Quick Start

State your goal, and request two actionable directions to choose from.

Frequently Asked Questions about brainstorming

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

FAQPage Schema
How do I convert vague feature ideas into actionable design directions quickly?

Structured brainstorming converts vague ideas into actionable design directions using a four-step process: Discover, Propose, Converge, and Capture. This framework enforces guardrails and focused questions to balance speed and quality in project teams.

What is the best way to facilitate rapid ideation and decision-making for a design team?

Rapid ideation and decision-making are facilitated by limiting initial alignment to three clarifying questions, then proposing two directional options with documented trade-offs. This lightweight process accelerates team convergence and captures clear rationale.

Does structured brainstorming require any code generation or technical dependencies?

Structured brainstorming requires no code generation and has zero dependencies. It functions as a lightweight, human-readable process framework to coordinate feature design, component creation, and behavioral changes within project teams.

How do I ensure accountability when my team makes design decisions during a brainstorming session?

Accountability during brainstorming is ensured by capturing decisions and their rationale as human-readable notes. The Capture step documents the team's choices and trade-offs, creating a clear record of why specific design directions were selected.

Can I use this structured brainstorming process for component creation and behavioral changes?

Yes, structured brainstorming applies across feature design, component creation, and behavioral changes. It provides a consistent framework to move from initial proposals to concrete decisions while maintaining speed and quality.

What limitations exist when using guardrails for collaborative ideation?

The main limitation of guardrailed collaborative ideation is its strict structure: it asks up to three clarifying questions and limits proposals to two recommended options. This accelerates decisions but may restrict open-ended, unstructured exploration.