harness-sync

To keep Plans.md in sync with implementation progress, use automated drift detection to compare task statuses against live file edits, then apply status marker updates like cc:TODO, cc:WIP, and cc:完了 to align the document.

Tracking task drift between a markdown plan and code involves validating the plan's structure and detecting discrepancies between documented tasks and actual file edits. Once detected, progress markers are automatically updated to reflect the true state.

To trigger a retrospective for completed tasks in Plans.md, run a sync operation that detects finished items marked with cc:完了. The retrospective analysis executes automatically upon finding these completed tasks.

Yes, you can save a snapshot of the Plans.md progress state for auditing by running the synchronization command with the --snapshot flag, which captures the current progress markers and task statuses at that moment.

Yes, harness-sync validates the Plans.md structure before applying any updates. It requires the document to contain recognized progress markers such as cc:TODO, cc:WIP, and cc:完了 to successfully detect drift and synchronize status.

Plans.md task statuses may fail to update if the document structure fails validation or lacks the required progress markers like cc:TODO, cc:WIP, and cc:完了. The sync tool must detect these markers to apply status changes.