write-a-prd

To write a PRD from interviews and codebase analysis, gather a detailed problem description, validate context via repository exploration, conduct structured stakeholder interviews, and draft the PRD using a standardized template.

Creating a GitHub issue template for product requirements involves defining explicit acceptance criteria, outlining major modules, and structuring the document so it is ready to submit directly to a repository.

Gathering product requirements through structured interviews requires collecting user needs via targeted conversations that elicit a long problem description, ensuring alignment with real problems before drafting documentation.

You can validate PRD assumptions against an existing codebase by performing repository exploration to cross-check proposed features, reduce scope creep, and verify technical feasibility before finalizing requirements.

Preventing scope creep when drafting product documentation requires repo-informed validation to cross-check assumptions against the codebase and structured interviews to maintain shared understanding of the actual requirements.

This PRD workflow works for system redesigns and new features by applying a standardized process to gather problem descriptions, sketch module designs, and generate a ready-to-submit GitHub issue with acceptance criteria.