| name | weekly-progress-summary |
| description | Use when generating the weekly project progress summary (run Fridays) from Jira/Linear — covering what shipped, what's at risk, and what's coming next week. |
Weekly Progress Summary (Fridays)
A higher-altitude rollup than the twice-daily pulse — meant for stakeholders,
not just yourself. Runs once a week, typically Friday afternoon.
Steps
-
Pull the week's activity through the official MCP servers (same
connectors as jira-progress-pulse — Linear MCP and the official
Atlassian Remote MCP server) rather than ad hoc API calls:
- Linear: issues completed/updated in the cycle (
list_issues with date filters, list_cycles)
- Jira: JQL like
project = X AND updated >= -7d, plus a sprint/board view for burndown context
- Using the official connectors means auth and rate-limit handling are
already solved — and the same connection serves both this skill and the
daily pulse, no duplicate setup.
-
Organize into:
## Week of <date> — <Project> Summary
**Shipped this week**
- <outcome-level bullets — "Shipped X", not "closed JIRA-123">
**At risk / blocked**
- <issue + why + what's needed to unblock — be specific, this is the
section stakeholders actually act on>
**Next week**
- <top 3-5 priorities pulled from the upcoming sprint/cycle>
**Velocity note** (optional)
- <only include if the trend is notable — don't manufacture a metric>
-
Write for the audience: translate ticket titles into outcomes a
non-engineer would understand. Group related tickets into one bullet.
-
Show the draft for review before sending/posting (Slack, email, Confluence —
whatever the configured destination is). Don't auto-publish.
Notes
- Schedule via
/schedule for Friday afternoons.
- "At risk" is the most valuable section — don't bury it or skip it because
it's uncomfortable to report.
- Keep total length to something a busy stakeholder reads in under a minute.
