brainstorming

Name: brainstorming
Availability: InStock
Author: oduffy

Transform ambiguous feature requests into an implementation-ready design spec.

5|2|Updated Mar 20, 2026

Search Tags:#architecture #brainstorming #requirements #scope control #design spec #planning handoff #PM-EM collaboration

Ready to run

npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill brainstorming-dbc-oduffy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brainstorming
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/brainstorming
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill brainstorming-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves ambiguity in feature requests by producing a PM-approved design spec before any implementation starts, preventing rework caused by unclear requirements or missing architectural intent.

Core Features & Use Cases

Clarifies intent with the PM: asks focused questions and aligns on what success looks like when the request is vague.
Proposes feasible approaches: generates 2–3 alternative directions with trade-offs so the PM can choose confidently.
Produces a committed design spec: writes a complete, implementation-ready spec and enforces a hard gate that blocks coding until PM approval.

Use it when you receive genuinely unclear “what should we build?” requests or multi-subsystem decomposition needs.

Quick Start

Invoke brainstorming to explore the design for a new feature request that is still ambiguous, and ask the PM to approve the resulting design spec before moving to planning.

Frequently Asked Questions about brainstorming

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

FAQPage Schema

How do I turn ambiguous feature requests into an implementation-ready design spec?▼

To turn ambiguous feature requests into a design spec, the Skill uses PM-EM collaborative dialogue to clarify intent, proposes 2-3 alternative directions with trade-offs, and writes a committed spec for PM approval before implementation starts.

What is the best way to control project scope during initial feature design exploration?▼

To control project scope during feature design exploration, the Skill enforces a hard gate that strictly prohibits code generation, scaffolding, or executor dispatch until the design spec is explicitly written, committed, and approved by the PM.

How do I align PM and EM on architectural requirements for multi-subsystem decomposition?▼

To align PM and EM on multi-subsystem architectural requirements, the Skill applies PM-EM collaborative dialogue, asking focused questions to define success criteria and explore feasible design directions when the team lacks a clear shape for what to build.

Can I generate code and start building immediately after defining the design spec?▼

You cannot generate code immediately after defining the design spec. The Skill enforces a hard gate that blocks implementation, scaffolding, or executor dispatch until the PM officially approves the spec for transition to the planning phase.

When should I use a collaborative brainstorming dialogue instead of jumping straight into execution?▼

You should use collaborative brainstorming dialogue instead of direct execution when you receive genuinely unclear "what should we build?" requests or multi-subsystem decomposition needs that require design exploration rather than immediate next-step execution.