What it does

Creates a product requirements document draft covering the problem, users, goals, scope, requirements, user stories, acceptance criteria, dependencies, risks, and success measures. It aligns information into one structure without deciding product strategy or technical feasibility.

How it works

Provide the approved problem statement, user research, business goals, constraints, existing decisions, dependencies, and delivery context. Product, design, and engineering owners should review assumptions, scope, metrics, edge cases, feasibility, and acceptance criteria before planning work.

Example workflows

• Turn discovery notes into a first PRD draft.

• Standardize requirements across product teams.

• Prepare a feature brief for cross-functional review and estimation.