brainstorm

You can generate a structured requirements document by conducting AI-guided collaborative brainstorming. This process expands thinking on edge cases before narrowing to MVP requirements and produces a PRD.

The best way to clarify feature scope is using a research-first workflow that conducts comparative research. It evaluates trade-offs and ensures a well-defined MVP scope before any code is written.

You can automatically gather repository context to seed a PRD through auto-context gathering. It inspects existing repository files and documentation to populate initial product requirements without user prompts.

Yes, you can use iterative Q&A to guide divergence and convergence for product brainstorming. It guides users through single-question loops, continuously updating the PRD and acceptance criteria throughout the process.

No external dependencies are required to create task directories. The workflow automatically generates task directories and seeds PRD files with initial information natively.

You should not use AI-driven brainstorming for requirements generation when dealing with simple, single-option tasks. It is specifically applied to ambiguous, multi-option development tasks to clarify scope.