brainstorming

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.

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.

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.

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.

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.