tracker-maintenance

Automate project tracker maintenance by invoking the tracker maintenance workflow to identify completed items across tactical and strategic trackers, archive them to monthly files, and prune tracker entries. This workflow keeps docs/project-tracker.md accurate and up-to-date.

Archiving completed items in a markdown tracker works by moving finished workstream entries from docs/project-tracker.md and docs/plans/*-tracker.md into archive/completed/YYYY-MM.md files. The workflow then prunes those entries from the active tracker and updates workstream statuses automatically.

The best way to reconcile dependencies in a project tracker is to use an automated workflow that checks **depends on:** and **blocked by:** annotations. This process validates dependencies via standardized steps to ensure workstream statuses reflect actual completion states.

Yes, you can sweep untracked commits into your project documentation automatically. The tracker maintenance workflow scans for untracked commits across strategic and tactical trackers, incorporating them into docs/project-tracker.md to reduce manual coordination overhead.

You need a markdown tracker format located at docs/project-tracker.md with supporting docs/plans/*-tracker.md files. The workflow uses **depends on:** and **blocked by:** annotations within these files to update workstream statuses automatically when all items are completed.

You should not use an automated tracker maintenance workflow when your project lacks standardized dependency annotations like **depends on:** or **blocked by:**. The workflow requires consistent markdown formatting in docs/project-tracker.md to successfully archive completed items and prune entries.