monitor-progress

Automate project progress monitoring by reading Jira, project plans, and budgets to generate sprint progress, deviation checks, and weekly status reports for phases 3 through 6. It consolidates tracking into structured outputs to keep stakeholders aligned.

Generate weekly status reports by extracting sprint progress and deviation data from Jira and project budget files. The monitoring process applies to phases 3 through 6 and produces structured reports for stakeholder alignment.

Project progress tracking works without Jira by falling back to file-based output. When Jira MCP data is unavailable, the system generates reports from local planning and budget files to enable manual review and workflow continuation.

Trigger automated email notifications for project deviations by using the send-email skill alongside generated status reports. The system uses language-aware templates to alert stakeholders when deviations are detected during progress monitoring.

Monitoring sprint progress and deviations requires project-state.md, 02-planning/project-plan.md, and 02-planning/project-budget.xlsx. These planning files provide the baseline data needed to check deviations and generate closure data.

Track project closure data by reading project-state and planning sources to consolidate sprint progress and deviation checks. This approach generates structured closure reports during phases 3 through 6 of the project lifecycle.