spec/propagate

Cross-document consistency is maintained by propagating specification updates through a sequential diff, scan, review, and apply process. This automatically identifies and updates downstream references in PRDs, architectures, and guides.

Propagating spec updates follows a strict four-step workflow: diff to identify changes, scan related documents, review proposed edits, and apply approved modifications. State tracking ensures traceability across all propagated updates.

State tracking during document updates is handled by maintaining an in-memory change manifest and recording explicit user approvals. This ensures only pre-approved modifications are applied, preserving traceability across documents.

Yes, explicit user approval is required before any specification change updates your documentation. The sequential enforcement process ensures only pre-approved changes are applied to related documents like PRDs and architecture guides.

Automated cross-document specification propagation is limited to pre-approved changes within spec-driven ecosystems. It requires sequential execution of the diff, scan, review, and apply steps, meaning steps cannot be skipped or executed out of order.

Yes, you can use this workflow to update architecture guides when a spec concept is renamed. The propagation process automatically scans for references to the renamed concept and applies updates across all related project documentation.