Recurring Status Report
Produce a recurring (weekly/biweekly) status report by gathering signals from the team's tools and writing a tight, skimmable update for stakeholders. Scopes the report template and the exact data sources FIRST (sections, audience, reporting window, RAG/health convention), then a developer gathers the raw signals from issue trackers, PRs, metrics, and notes into a facts file, then a copywriter writes the polished report strictly from those gathered facts. Scoping the template before gathering is what keeps every recurring issue consistent and prevents the model from padding with prose. Use for weekly status updates, sprint reports, project health reports, stakeholder updates, and exec summaries.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Scope the report | Planner | lock the template, sources, window, and health convention |
| 2 | Gather signals | Developer | pull raw facts from each named source into a facts file |
| 3 | Write the report | Copywriter | compose the polished report from gathered facts |
| 4 | Evaluate | Reviewer | Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap. |
| 5 | Finish | Developer | All acceptance criteria met. Stamp a short summary and report DONE. |
Say something like "weekly status report" or "project update" or "sprint report" or "status update" or "stakeholder report" in chat to start it.