reconcile

To synchronize your scrum board state with git history, you can use an automated workflow that scans epics, stories, and tasks to verify their completion status against actual commits and worktrees, ensuring project tracking accuracy.

The best way to clean up stale todo entries after a sprint is to run an automated board reconciliation that cross-references task statuses against git commits and automatically promotes or demotes items based on actual implementation progress.

Automated task verification works by scanning project management documentation artifacts and cross-referencing the recorded statuses of epics, stories, and tasks against the actual code implementation history found in git commits and worktrees.

Yes, you can update project management documentation to reflect true progress by performing a board reconciliation, which identifies tasks completed outside the standard workflow and rolls up status changes to match the actual repository state.

Yes, board reconciliation works without external dependencies, operating directly within your environment to scan documentation artifacts and synchronize project tracking data with your existing git implementation history.

You should avoid automated workflow cleanup when your scrum board has intentionally manual task statuses that must not be overwritten, as the reconciliation process will automatically promote implemented tasks and demote stale items to match git history.