propagate-design-change

To trace PRD changes across downstream artifacts, you can run a change propagation analysis that scans ADRs, registries, and stories referencing TR-IDs to surface a consolidated impact report. This identifies dependent artifacts affected by the edit.

Analyzing the ripple effect of a product requirement edit involves scanning downstream documents for TR-IDs or configurable values to categorize findings as stale, potentially stale, or blocked. This prioritized impact report guides remediation to prevent document drift.

To identify impacted ADRs and epics after a PRD update, scan architecture documents and production epics for references to the changed TR-IDs. The analysis collects all dependent artifacts and flags them based on their alignment with the new requirements.

You cannot automatically update downstream stories and registries when a PRD changes because this operation is non-destructive. It reads artifacts without making edits, instead outputting a guided resolution walk-through and actionable plan for you to apply manually.

Change propagation analysis does not modify your architecture documents or registry files. It operates non-destructively by reading artifacts and producing a clear, prioritized impact report with recommended actions for you to execute using other tools.

You need to run a downstream impact report for your product documents immediately after updating a PRD. This ensures that any misalignment across ADRs, stories, and other PRDs is detected early and categorized before development drift occurs.