brainstorming

To consolidate vague requests into a structured design document, this Skill interactively asks clarifying questions one at a time, proposes 2-3 named approaches with trade-offs, and saves the finalized design to docs/brainstorms.

The best way to prevent single-solution bias during project planning is to generate 2-3 named approaches with explicit trade-offs. This ensures you evaluate multiple design decisions before committing to a formal PRD workflow.

You need a formal design document before coding when requirements are ambiguous or allow multiple interpretations. Generating a PRD-like traceable record in docs/brainstorms aligns stakeholders and converges on a clear plan.

To prepare ambiguous requirements for a formal PRD workflow, apply a controlled sequence of clarifying questions to converge on a plan. This captures all design decisions in a structured document located in docs/brainstorms.

Yes, this brainstorming process works specifically for multi-interpretation project requests. It resolves ambiguity by interactively clarifying requirements one question at a time and locking in design decisions before build.