trellis-brainstorm

To define MVP scope with unclear requirements, use structured requirements discovery to ask iterative questions, document a living PRD, and align stakeholders before implementation. This process scaffolds tasks and converges multiple valid approaches into an actionable plan.

Writing a PRD for features with multiple approaches requires research-first exploration and one-question-at-a-time interrogation. This disciplined scoping method documents technical choices in a living PRD and records decisions to ensure stakeholder alignment before development.

Facilitate collaborative requirements discovery by enforcing a Q&A cadence that asks one high-value question per message. This prevents overload, ensures immediate alignment through PRD seeding, and systematically narrows complex tasks into an MVP-ready scope.

Yes, structured brainstorming aligns stakeholders before implementation by guiding iterative questions and documenting decisions in a living PRD. It is designed for complex tasks requiring disciplined scoping, ensuring everyone agrees on the MVP scope and expansion plan.

Use guided requirements discovery instead of writing a PRD directly when requirements are unclear, complex tasks require disciplined scoping, or multiple viable approaches exist. It forces iterative alignment and research-informed choices that a static PRD would miss.

Yes, the requirements discovery method supports future expansion by researching technical choices, recording stakeholder decisions, and seeding a living PRD. It creates an expansion-ready plan that documents the rationale behind the finalized MVP scope.