write-a-prd

To create a PRD from user interviews and codebase analysis, you can guide structured interview capture, explore the repository to validate constraints, design high-level modules, and submit the PRD as a GitHub issue.

The process for turning feature planning notes into a GitHub issue involves capturing user needs through interviews, analyzing the repository, decomposing modules, and generating a structured PRD submitted directly to GitHub.

Yes, you can use this for module decomposition and dependency planning across software projects of any size, as it validates current repository state and scopes modules during feature planning.

You capture user requirements during a product management interview by using structured interview capture to surface user needs, goals, and success criteria before exploring the codebase.

Generating a PRD includes repository discovery to validate assumptions and current constraints, ensuring the module scoping and dependency planning align with the existing software architecture.

The best way to structure a product requirements document for development tracking is to compile interview goals, codebase constraints, and module designs, then submit the PRD as a GitHub issue for visibility.