prd-update-decisions

To keep PRDs synchronized with design decisions, you need a process that captures conversation outcomes, logs the rationale and date, and updates relevant prds/[issue-id]-[feature-name].md sections to prevent documentation drift.

Logging product management decisions for audit traceability involves recording the specific design change, the date it was made, the strategic rationale behind it, and its impact on scope within a structured decision log linked to your PRDs.

To update product requirements after a scope change, apply the strategic decisions identified during the review directly to the corresponding PRD sections, ensuring you capture the new requirements and record the decision rationale for cross-artifact consistency.

Yes, you can apply strategic changes across multiple PRD sections by targeting the prds/[issue-id]-[feature-name].md documents, updating the affected requirements, and aligning the workflow changes to reduce cross-artifact drift.

PRD documentation drifts from actual product development because design decisions and strategic scope changes occur during conversations without being systematically captured, logged with rationale, and applied back to the original product requirements documents.