living-documentation

Spec documentation stays in sync with code changes by automatically updating .kiro/specs/*/requirements.md and design.md files to reflect feature implementations, bug fixes, and refactors, maintaining a clear contract between design and implementation.

Living documentation maintains traceability by embedding implementation notes and edge cases directly into spec files, ensuring the documentation evolves alongside the codebase rather than becoming stale.

You need to update .kiro/specs files during a refactor when the changes affect behavior documented in requirements.md or design.md, and triggering the sync ensures the specs capture the new implementation logic and edge cases.

Yes, the documentation sync tool works directly with existing .kiro/specs/* directories, reading your current requirements.md and design.md files and applying updates based on the code modifications you have made.

The best way to document edge cases in living specs is to enforce their inclusion during the code change sync process, embedding the edge case handling directly within the requirements and design documentation.

Spec documentation diverges from implementation when code changes are made without updating the corresponding design docs, and living documentation solves this by syncing spec files with code changes to reduce divergence.