write-a-prd

To turn user interviews into a product requirements document, you provide a long problem statement and goals, and the system guides conversations to capture constraints, then assembles problem, solution, and acceptance criteria into a cohesive PRD template.

The best way to generate a PRD ready for GitHub issue submission is to run an interview-driven workflow that translates articulated goals, user stories, and module boundaries directly into a ready-to-use GitHub issue template.

Yes, you can create a PRD from a codebase exploration and stakeholder input by analyzing the repository to inform requirements and module boundaries, ensuring cross-functional alignment before drafting the formal document.

Interview-driven PRD creation works by guiding conversations with stakeholders to capture goals, constraints, and success criteria, then delineating modules to satisfy an end-to-end feature development workflow.

You need a long problem statement and goals to start drafting product requirements, which allows the system to trigger the GitHub issue workflow and generate the formal PRD template accurately.