traverspec-reconcile

To detect documentation drift, you can compare existing spec nodes against your codebase implementation to identify discrepancies, verify architectural integrity, and flag undocumented features for human review.

You should verify spec-to-code alignment at the start of a session or after a major refactor to ensure your architecture documentation accurately reflects the current state of the codebase.

The best way to check for undocumented features is to systematically compare your spec graph against the modified code to identify matches, drift, or new features that lack documentation.

No, spec-driven verification applies a human-in-the-loop approach, flagging discrepancies for human decision-making rather than making risky automated assumptions or synchronizing documentation automatically.

Yes, you can manually verify architectural integrity by comparing spec nodes against the implementation, satisfying requirements for manual verification of spec-to-code mapping without automated synchronization.

The primary limitation is that it requires manual human intervention to resolve flagged discrepancies, meaning it does not automatically correct stale documentation or synchronize the spec graph with code changes.