Product Requirements Document Generator — illustrative example

INPUT
Draft a small PRD for comparing two CSV supplier files before a catalog update. Required fields: SKU and Price. Match exact SKUs; show old and new prices; export a review list. Duplicate SKUs must be flagged. Volume limits and permissions are undecided.

RESULT
Problem: catalog managers need to inspect supplier price changes before an update.
Inputs: two CSV files containing SKU and Price.
Matching: exact SKU values; duplicate keys require review rather than automatic pairing.
Result: a list containing SKU, old price, new price and change status.
Export: the reviewed comparison is downloadable; the workflow does not update the live catalog.
Acceptance example: A12 changes from 10 to 12 and appears as a price change.
Open decisions: supported volume, permissions and treatment of missing prices.

REVIEW
A PRD connects the user problem to observable product behavior. Keep requirements separate from proposed implementation details and unresolved decisions.

This is a teaching example, not a live execution record.