brainstorming

Coordinate collaborative ideation into structured design plans and implementation documents.

371|38|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill brainstorming-ibrahim-3d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers/tree/main/skills/brainstorming
Command: npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill brainstorming-ibrahim-3d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables collaborative ideation to transform vague ideas into structured design plans before implementation, reducing rework and misalignment.

Core Features & Use Cases

  • Explore project context to surface constraints, goals, and opportunities.
  • Ask clarifying questions one at a time to refine purpose and success criteria.
  • Propose 2-3 approaches with trade-offs and select a recommended path.
  • Present a design concept and secure user approval before transitioning to documentation.
  • Generate a concrete design doc and implementation plan to guide execution.

Quick Start

Start a brainstorming session by outlining the project goal and current context, then guide the AI to generate a design plan and an implementation transition.

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

To turn vague ideas into structured design plans, collaborative ideation explores project context, asks clarifying questions, proposes approaches with trade-offs, and secures approval before generating documentation.

What is the best way to facilitate collaborative ideation for early-stage product discovery?

Collaborative ideation for early-stage product discovery works best through a stepwise workflow that surfaces constraints, proposes 2-3 approaches, presents a design concept, and transitions into an implementation plan.

How do I break down project requirements into a concrete design doc?

Breaking down requirements into a design doc involves exploring project goals, asking targeted clarifying questions one at a time, selecting a recommended path from proposed approaches, and automating the writing-plans transition.

Can I propose multiple design approaches with trade-offs before creating implementation docs?

Yes, you can propose 2-3 approaches with clear trade-offs. After presenting the design concept and securing user approval on a recommended path, the system automatically transitions to generating implementation docs.

Does collaborative design planning help reduce rework before development?

Yes, collaborative design planning reduces rework and misalignment by transforming vague ideas into structured plans, enforcing a stepwise exploration of constraints, and securing concept approval before execution begins.