trellis-brainstorm

To create a PRD from an unclear product requirement, use a structured brainstorming flow that auto-gathers repo context, seeds a PRD, and uses staged questioning to converge on an MVP scope.

The best way to define MVP scope with multiple viable approaches is applying divergence-convergence cycles during brainstorming, clarifying risks and acceptance criteria before implementation begins.

Yes, collaborative discovery guides cross-functional teams by asking one question at a time, researching decisions first, and finalizing confirmations to ensure alignment before AI coding starts.

Auto-context gathering for product management brainstorming works by automatically collecting repository and documentation context to inform staged questions, seed the PRD, and drive research-first decisions.

No, you do not need a pre-existing seeded PRD to start; the workflow creates a new brainstorming task, automatically gathers context, and generates the initial seeded PRD for you.

You should avoid structured brainstorming for requirements when the task is already clear, lacks multiple viable approaches, or does not require cross-functional alignment and complex MVP scope definition.