trellis-brainstorm

Requirements discovery is guided through a structured brainstorming workflow that seeds a PRD, asks targeted questions one at a time, and converges on an MVP scope to clarify vague feature requests.

Creating a PRD for unclear projects is handled by seeding a task directory with an initial document, then using one-question-at-a-time interrogation to extract specifics and reduce back-and-forth.

Collaborative requirements discovery works by applying a Diverge→Converge thinking process, exploring future scope while locking the MVP, and performing research-first analysis to surface viable technical choices for sprint planning.

Yes, this approach applies when there are multiple viable technical paths, using research-first analysis to evaluate options before committing to a specific implementation strategy for AI-coding tasks.

No specific dependencies or environment setup are required to start brainstorming requirements; the workflow directly seeds a task directory and initiates the PRD generation process.

You should avoid guided requirements discovery when the task is already well-defined with a clear scope, as the one-question-at-a-time interrogation strategy is specifically designed for complex, unclear, or new feature descriptions.