brainstorm

Run a Socratic ideation session to surface constraints, risks, and trade-offs.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/mikecubed/agent-orchestration --skill brainstorm-mikecubed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/mikecubed/agent-orchestration/tree/main/plugins/flow/skills/brainstorm
Command: npx skills add https://github.com/mikecubed/agent-orchestration --skill brainstorm-mikecubed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to run a structured ideation session (Socratic dialogue) to surface constraints, risks, and trade-offs before committing to a direction.

Core Features & Use Cases

  • Socratic dialogue to surface constraints, trade-offs, and risks.
  • Structured ideation brief generation and handoff to sdd-specify.
  • Roles and workflow guidance for discovery, ideation, and review.

Quick Start

Initiate a brainstorm session with a rough idea to surface constraints and trade-offs before specification.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I run a structured ideation session to surface project constraints and risks?

To run a structured ideation session, initiate a Socratic dialogue flow with a rough idea to clarify intent and surface trade-offs. The session defines role responsibilities and outputs a durable ideation brief for handoff to formal specification.

What is Socratic dialogue for early-stage idea exploration?

Socratic dialogue for idea exploration is a structured questioning technique that exposes project constraints, risks, and trade-offs before committing to a direction. It enforces a guided discovery flow to clarify intent during the initial ideation phase.

How do I prepare requirements and ideation briefs for formal specification handoff?

To prepare requirements for handoff, complete a structured brainstorming session to compare trade-offs and clarify intent. The session generates a durable ideation brief and records the session state in SESSION.md for downstream specification.

When do I need to use a Socratic dialogue workflow for software requirements?

You need a Socratic dialogue workflow when you are in early-stage idea exploration and must clarify intent, surface constraints, and compare trade-offs before committing to a formal specification direction.

Can I capture ideation session state and role responsibilities without external dependencies?

Yes, you can capture ideation session state and define role responsibilities without external dependencies. The skill operates independently, recording session state in SESSION.md and generating a durable brief for handoff.

What are the limitations of using Socratic dialogue for requirements discovery?

Socratic dialogue for requirements discovery is limited to early-stage idea exploration before formal specification. It focuses on surfacing constraints and trade-offs rather than generating final technical specifications or implementation details.