prd-writer

To draft a structured Product Requirements Document, define the problem statement, user and business goals, success metrics, and requirements prioritization. This process ensures clear product definition and team alignment for new features, improvements, bug fixes, or experiments.

A feature specification should include problem statements, business objectives, success metrics, user stories, technical considerations, and risk assessments. Categorizing requirements by priority like P0, P1, and P2 helps ensure comprehensive product definition and team alignment.

Yes, you can generate PRDs for bug fixes and product experiments. The document generation supports iterative refinement based on common PRD formats, adapting the problem statements, requirements, and success metrics for various product specification types.

The best way to prioritize requirements in a product requirements document is to categorize them into P0, P1, and P2 tiers. This prioritization guidance helps define the scope of user stories and technical considerations for the feature specification.

You refine a PRD after the initial draft through iterative refinement based on common formats. This allows you to progressively adjust problem statements, success metrics, and technical considerations as the feature specification evolves during product management.

You need to write a PRD for a product improvement when kicking off a new feature to outline user problems and business objectives. It ensures everyone on the team is aligned from the start by documenting success metrics and risk assessments.