trellis-brainstorm

To turn ambiguous product requests into MVP plans, use an evidence-first interview process that asks one high-value question at a time, automatically seeds a PRD, and updates planning artifacts after each decision to align scope and reduce rework.

Aligning scope for complex tasks requires searching the repository codebase first for existing evidence, then asking targeted questions about intent to fill remaining gaps, and finally generating explicit design and implementation plans to make execution testable.

Creating a PRD from an unclear request involves conducting a relentless requirements interview that converges on shared requirements, automatically seeding a prd.md file, and iteratively updating it with each user decision.

Requirements brainstorming can automatically generate or update design.md and implement.md files for complex work, ensuring that execution and acceptance criteria are fully testable without manually writing separate design documents from scratch.

Use a one-question-at-a-time interview for architecture decisions when there are multiple feasible technical approaches and scope or risk choices are not yet decided, allowing evidence-first repository inspection to guide the questioning.