trellis-brainstorm

MVP scope is defined by running a Phase 1 planning interview that asks one high-value question at a time, turning vague requests into concrete decisions captured in prd.md. This iterative flow converges on a shared understanding of the minimal viable product.

Requirements discovery starts by creating a Trellis task directory and seeding a prd.md file. The process then kicks off a collaborative interview flow to surface key decisions and establish shared understanding before any coding begins.

You generate a PRD by inspecting existing code, tests, docs, and task history to answer questions with repository evidence. This evidence-first questioning approach seeds the prd.md with factual project context rather than assumptions.

Planning artifacts like prd.md, design.md, and implement.md evolve iteratively as decisions and dependencies become clearer. The process updates these files continuously to reflect the shared understanding achieved through the one-question-at-a-time interview flow.

Yes, this task-management approach is designed specifically for situations where multiple approaches exist. It facilitates collaborative requirements discovery to converge on a single MVP scope by asking targeted questions and updating planning artifacts.

Inspecting repository evidence prevents asking for facts the project already provides. By checking code, tests, and docs first, the questioning flow focuses on high-value decisions that actually surface new requirements rather than redundant information.