execution-tracking

Real-time progress tracking ties current delivery status directly to the original execution plan. By consuming plan.md, schedule.md, and team-checklist.md, the skill generates live progress updates, blocker logs, and updated schedules to keep timelines synced with reality.

Surfacing blockers and risks during active build phases requires capturing status updates and plan deviations across teams. The skill enforces input contracts to process team checklists and schedules, producing phase reports and a dedicated blocker log for immediate escalation.

Generating progress reports and updated schedules involves feeding current execution status and blockers into the skill. It outputs updated progress data, risk updates, and timeline adjustments to inform stakeholders of phase completions and delivery deviations.

Yes, cross-team collaboration and milestone tracking are supported during active build phases. The skill captures status updates and timelines across multiple teams, processing team-checklist.md inputs to produce synchronized phase reports and milestone deviations.

Tracking plan deviations and timeline adjustments requires three specific input files: plan.md, schedule.md, and team-checklist.md. The skill enforces these input contracts to accurately capture deviations and output updated progress reports.

Progress tracking becomes disconnected from the execution plan when real-time status updates are not tied to established milestones and schedules. This skill solves the problem by enforcing input and output contracts that sync live team updates directly with the original plan.