write-a-prd

To convert user research into a product requirement document, provide a detailed problem description to trigger a guided interview that validates assumptions against your codebase and generates a PRD with problem statements, user stories, and implementation decisions.

When you write a PRD for a new software feature, required sections include a Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, Out of Scope, and Further Notes to ensure complete module design coverage.

Yes, you can generate a GitHub issue directly from a feature planning interview by completing the iterative discovery process, which outlines major modules and automatically formats the structured PRD output for repository submission.

To plan modular architecture during product development kick-off, the system analyzes your repository context to validate scope and sketches major modules with specific design choices, enabling testable isolation before finalizing the requirement document.

The best way to outline implementation decisions for a requirement document is through structured interviewing that resolves dependencies and evaluates design trade-offs, ensuring all technical choices are documented alongside user stories.

Feature planning requires a long, detailed problem description before writing a PRD to reach a shared understanding, which then drives clarifying questions and context exploration to accurately define the product scope.