weekly-report · git:20260922.a4bd47b · 2026-09-22 · sha256 53e57ad79e223317

weekly-report git:20260922.a4bd47bA

Immutable. This exact content never changes and is served at /api/v1/blob/53e57ad79e223317.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7knqk77hw2asukvv/53e57ad79e2233173267046066a119c8f44a42882212620ff8516ae74330a990.json

Then /plugin install weekly-report@markdownregistry-7knqk77hw2asukvv in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: weekly-report
description: >-
  Generate the weekly business report across projects: what shipped, metric
  movement, incidents, next week's plan. Trigger on "weekly report",
  "how did the week go", or on a Friday/Sunday recap request.
---

# Weekly report

## Steps

1. **Window**: the last 7 days (or since the previous report if one exists
   in the project's docs).
2. **Shipped**: git log across all active repos for the window, grouped by
   project; include deploys that reached prod.
3. **Metrics**: pull what is reachable: conversion/funnel numbers from the
   app's admin endpoints, usage counts, model scorecard deltas (only from
   real evaluation runs). Compare against the previous week; compute deltas.
4. **Incidents**: anything that broke in prod and what fixed it (from memory
   notes, logs, and the week's sessions).
5. **Delegate assembly** to the `report-builder` subagent with the collected
   data; ask for the weekly format with 2-3 charts max.
6. Save the result under the project's docs (dated) so next week has a
   baseline, and give the executive summary inline.