brainstorm

Scoping a vague feature into an MVP requires collaborative requirements discovery that inspects the repository, proposes implementation approaches, and converges scope through single-question Q&A loops. It records goals and acceptance criteria in a living PRD.

Documenting technical decisions for multiple paths involves generating an ADR-lite decision record after researching 2-3 concrete approaches with trade-offs. A diverge-to-converge Q&A loop balances reliability, cost, and speed before recording the final choice.

Seeding a PRD for an unclear feature uses task-first PRD seeding to automatically create a task directory and generate a living prd.md. This living document captures goals, assumptions, open questions, and acceptance criteria immediately as ideas are discussed.

Yes, you can compare architectural approaches using research-first option generation to inspect the repository and external patterns. It proposes 2-3 concrete implementation paths with trade-offs, ideal for choosing libraries, architectures, or UX flows for complex features.

Yes, the requirements discovery process supports automatic task creation alongside repository inspection and integration with task scripting. This allows development teams and AI agents to move from vague ideas to scoped MVPs and actionable development tasks efficiently.

You should avoid a diverge-converge Q&A loop when requirements are already fully defined and no multiple implementation paths exist. It is designed specifically for scenarios needing scope convergence, edge case exploration, and balancing reliability with development speed.