prd-writing

To write a product requirements document for an existing codebase, you can use a structured interview process to explore the repository structure and co-author a Behavioral PRD saved directly as docs/prd.md.

A behavioral PRD defines what a system should do from the user's perspective, capturing expected behaviors and scoping features. You need one to formalize problem statements and user stories before implementation begins.

You can scope a new feature and capture expected behaviors by conducting an interview-driven planning process that references existing documentation to generate a complete product requirements document with an Expected Behaviors section.

Yes, you can generate a reusable PRD workflow for multiple projects by applying an interview-driven process that formalizes problem statements and outputs a standardized product requirements document at each repository root.

Manual codebase exploration is not required beforehand because the PRD co-authoring process integrates structured interviews with automated codebase exploration to reference existing code structure and documentation directly.

The best way to define system requirements through structured interviews is using a co-authoring process that asks targeted questions about user goals, translating answers into a formal product requirements document with user stories.