Skill: monitor-progress

Monitors project execution across 6 modes — from sprint progress tracking to stream synchronization and final data collection. Reads Jira, project-plan, and project-budget. Generates structured reports; triggers email notifications for deviations and weekly status. Falls back gracefully when Jira is unavailable.

Triggers

Russian: «проверь прогресс», «статус проекта», «отчёт по прогрессу», «еженедельный отчёт», «проверь отклонения», «отклонения по срокам/бюджету», «синхронизация потоков», «собери фактические данные», «данные для закрытия» English: "check progress", "project status", "progress report", "weekly status", "check deviations", "deviation report", "sync streams", "collect actual data", "closing data"

Language Detection

• Request in Russian → templates *-ru.md, all outputs in Russian
• Otherwise → templates *-en.md, all outputs in English

Modes

Input

Output

Instructions

Step 1 — Determine Mode

Determine the mode from the PM's request or the scheduled task prompt.

If mode is ambiguous and the request came from PM in chat → ask: "Which report do you need?

1. Sprint progress — task completion status (Phase 4)
2. Deviation check — schedule and budget deviations (Phase 4)
3. Stream sync — dev/marketing/ops synchronization (Phase 5)
4. Actual data — final figures for project closure (Phase 6)"

Phase validation:

• sync-streams: only available in Phase 5. If current phase ≠ 5 → inform PM and stop. Message: "sync-streams is only available in Phase 5 (Launch). Current phase: {PHASE}. If you need current sprint progress data, use progress-report mode instead."
• actual-data: only available in Phase 6. If current phase ≠ 6 → inform PM and stop. Message: "actual-data collection is only available in Phase 6 (Closure). Current phase: {PHASE}."

Step 2 — Read Project Context

Always read:

• project-state.md → project name, current phase, sprint number, last update date

Read per mode:

If files are not found → continue with available data, note missing files in the report with placeholder [DATA NOT AVAILABLE — fill manually].

Step 3 — Query Jira (if available)

Attempt to retrieve data via Jira MCP:

Fallback if Jira MCP unavailable:

• Continue without Jira data
• Mark all Jira-dependent fields with the language-matched placeholder:
  • EN: [JIRA DATA UNAVAILABLE — fill manually]
  • RU: [JIRA НЕДОСТУПЕН — заполнить вручную]
• Notify in chat (match detected language):
  • EN: "Jira MCP unavailable — report generated with placeholders. Fill in Jira sections manually."
  • RU: "Jira MCP недоступен — отчёт сгенерирован с плейсхолдерами. Заполни разделы Jira вручную."

Step 4 — Generate Report

Load the template matching mode and language:

Populate all template sections with data from Step 2 + Step 3.

Deviation assessment rules:

• Schedule deviation: task overdue by >0 days → flag as deviation
• Budget deviation: actual spend > planned by >5% → flag as deviation
• Critical threshold: >10% schedule delay or >10% budget overrun → mark as CRITICAL
• No deviations found → for deviation-check and daily-deviation: write to logs/log.md "no deviations" and STOP (do not generate report file)

For actual-data mode:

• Output is an xlsx schema — generate the schema structure per templates/actual-data-report-schema.md
• Save as 06-closure/actual-data-report.xlsx (structure only; PM fills actual values from populated template or Jira export)

Step 5 — Handle Email (where applicable)

Level 1 (autonomous): Generate email draft → pass to send-email for immediate dispatch. Level 2 (draft): Generate email draft in reports/email-draft-{mode}-{date}.md → notify PM: "Email draft ready — review and confirm before sending via send-email."

Load the matching email template, populate with report key findings, recipients from 01-initiation/stakeholder-map.md (or comm-plan.md).

Step 6 — Save Files and Update State

1. Save the report file to the correct path (see Output table).
2. For actual-data mode: save 06-closure/actual-data-report.xlsx schema.
3. Update project-state.md:
   • Add artifact record with status completed and date.
   • For weekly-status: update field last_weekly_report.
   • For deviation-check/daily-deviation: update field last_deviation_check.
4. Write to logs/log.md: {DATE}: monitor-progress [{MODE}] — {RESULT}. Saved: reports/{FILENAME}
   • RESULT examples: "3 deviations found", "no deviations", "report generated", "Jira unavailable — manual fill needed"
5. Output to chat:
   • File saved path
   • Key findings summary (2–5 bullet points)
   • Email action (if applicable): "Email draft ready at reports/email-draft-{mode}-{date}.md"
   • If deviations are critical: "⚠️ CRITICAL deviation detected — immediate PM attention required."

Templates

Dependencies

Reads (required):

• project-state.md — project name, phase, sprint number
• 02-planning/project-plan.md — planned milestones, tasks, deadlines
• 02-planning/project-budget.xlsx — budget plan (deviation modes)

Reads (optional):

• 01-initiation/stakeholder-map.md — email recipients
• 02-planning/comm-plan.md — communication preferences
• reports/progress-report-*.md — previous reports for trend comparison
• 03-execution/launch-checklist.md — launch readiness (sync-streams)

External actions:

• Jira MCP — sprint and task data (fallback: PM provides manually)
• send-email skill — email dispatch (E4 level 2, E5 level 2, E7 level 1)

Writes:

• reports/progress-report-{date}.md
• reports/deviation-report-{date}.md
• reports/sync-report-{date}.md
• reports/weekly-status-{date}.md
• reports/daily-deviation-{date}.md
• 06-closure/actual-data-report.xlsx
• project-state.md (status update)
• logs/log.md (action record)

Constraints

• sync-streams mode is only available in Phase 5
• actual-data mode is only available in Phase 6
• Does NOT make decisions about deviations — generates report and notifies PM
• Does NOT update project-plan.md — PM decides how to respond to deviations
• For deviation-check and daily-deviation: if no deviations found, logs the check and stops — no report file created
• Fallback mode does not block report generation — produces report with placeholders
• One invocation = one mode; do not combine modes in a single run
• Email for weekly-status (E7, level 1) is sent autonomously — no PM confirmation required
• Email for deviation-check (E4) and sync-streams (E5) are level 2 — PM must confirm before sending