write-a-prd

To create a PRD from user interviews and codebase analysis, you provide a detailed problem statement and potential solution ideas. The system then guides a deep interview and analyzes your repository to validate constraints before outputting a structured product requirements epic.

A beads epic in product management is a structured PRD output that captures problem statements, proposed solutions, implementation modules, design decisions, and testing considerations. It is generated through a multi-step workflow involving problem gathering and design scoping.

Yes, you can generate a PRD with a rough problem statement. Providing a long, detailed problem statement alongside any potential solution ideas initiates the user interview process, which systematically elicits the missing requirements to scope the full design.

To scope design decisions and testing considerations for a new feature, use a guided interview process that evaluates your codebase context. This multi-step workflow captures problem statements, defines the proposed solution, and outlines the implementation plan within the PRD.

Analyzing the codebase is a core feature of this PRD generation workflow, used to systematically validate project context and technical constraints. Skipping repository exploration means losing critical validation that informs the implementation modules and design decisions.

The best way to turn product discovery interviews into a ready PRD is to use a guided workflow that combines user interviews with repository exploration. This approach captures problem statements and solution ideas, outputting a beads epic with implementation plans and testing decisions.