weekly-report · git:20260711.2d30535 · 2026-07-11 · sha256 dc6d7188ce71b582

weekly-report git:20260711.2d30535A

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

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7knqk77hw2asukvv/dc6d7188ce71b582395ecfd7f1005461fe2d8cdddb5434bd17a60a187379899c.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", "как прошла неделя", 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.