harness-sync

To detect drift between your Plans.md and the actual codebase, you can run a reconciliation process that validates the plan structure and compares plan items against recent commits to surface misalignments.

Keeping project plans in sync with evolving code involves reconciling the planning document with the implementation state by comparing planned items to commits, driving corrections and ensuring documentation stays aligned.

Yes, you can take a point-in-time snapshot of your project plan progress by running the sync process with a snapshot flag, which records the current state of your implementation reconciliation.

Generating a retrospective report for plan implementation status requires running a sync process that compares your planning document to actual commits and provides retrospective context to record progress over time.

Plan-implementation reconciliation requires a living Plans.md file with a valid structure; the process validates the document's structure before comparing its items to commits, so projects without structured plans cannot be reconciled.