review-tracker

Generating a progress report requires parsing tracker metadata, statuses, and dependencies across phases and tracks. The skill computes completion percentages, identifies blockers, and outputs a structured report with recommendations and an optional detailed view for archiving.

Tracker analysis evaluates project statuses and dependencies across multiple phases to compute overall completion. By parsing this metadata, the mechanism detects stalled tracks and dependencies, surfacing specific blockers in a structured report to help teams resolve bottlenecks quickly.

Yes, the skill supports exporting generated tracker reports for meetings and archiving. After it analyzes tracker statuses and computes blockers, you can export the structured report output to share progress insights with stakeholders or save it for historical reference.

The best way to review tracker progress is by analyzing metadata across all project tracks and phases simultaneously. This approach computes overall completion, cross-references dependencies to find blockers, and produces a single structured report with recommendations to guide decision-making.

No, you do not need to manually map dependencies. The skill automatically parses existing tracker metadata, phase statuses, and dependency data to compute completion rates and identify blockers, generating the structured report directly from the available tracker information.

A tracker progress report may show incomplete phases due to pending dependencies or unstarted tracks rather than active blockers. The analysis computes completion by parsing all phase and track statuses, meaning tasks not yet started will lower overall completion rates even without explicit blockers.