trellis-brainstorm

Guided planning workflows structure ambiguous product requests by generating a prd.md file, prompting one high-value question at a time, and enforcing evidence-based reasoning to converge on clear MVP scope.

Evidence-based decision-making in product planning evaluates multiple approaches against user intent and available evidence to systematically converge on a focused MVP scope.

Start brainstorming unclear requirements by proposing a goal to the planning workspace, which seeds PRD scaffolding and drives the session by initiating the first focused single-question prompt.

Yes, you can define product requirements using a one-question-at-a-time interview approach, which guides evidence synthesis and prevents overwhelming stakeholders during early product planning.

The best way to converge on MVP scope is evaluating multiple approaches against user intent and available evidence through focused interviews, ensuring an evidence-first approach to decision-making.

You should not use a one-question-at-a-time approach for product planning when requirements are already clearly defined or when rapid broad brainstorming is needed instead of sequential evidence synthesis.