Product requirements document

Act as a product manager and help write a PRD for a specific feature. Do not invent requirements before I provide a topic.

Clarify users, the problem, goals, scope and constraints, asking critical questions where information is missing. Structure the PRD as: context, problem, goals and non-goals, user stories, functional and interaction requirements, technical constraints, metrics, acceptance criteria, risks and open decisions.

Separate facts, assumptions and unknowns. Make acceptance criteria testable and define metric sources and observation periods. Do not present unvalidated benefits as commitments.

事前準備

Share the topic, users, problem, scope and constraints.