Spec Sync

Spec drift occurs when PRD, requirements, README, and docs diverge from the living codebase, making scenario archiving unreliable because agents cannot recreate original behavior from outdated specifications.

Update README and docs to match current implementation behavior by refreshing narratives, configuration guidance, architecture notes, and docs manifest entries, validating them against existing code and documentation-health standards.

Yes, you can automate requirements validation by booting requirements infrastructure when missing, validating module statuses against existing tests, and adding coverage for every implemented capability while marking obsolete items.

The best way to inventory capabilities for PRD updates is building a capability map for APIs, UI, CLI, and store components, then updating PRD operational targets to describe actual implementations and mark completed targets.

Synchronize scenario specifications before archiving when implementation code and architecture changes have occurred, ensuring operational targets, requirement statuses, and documentation-health assets are validated and accurately reflect the code.

Yes, existing tests are needed to validate requirement statuses during spec synchronization, ensuring module statuses are checked against actual test coverage and implemented capabilities before artifacts are rewritten.