Prompt detail

Weekly Delivery Review

Preparation for a weekly delivery conversation about flow, WIP, and recent accumulation without turning the data into an automatic action plan.

Prompt 04
Analyzed reports
ThroughputPR Cycle TimeIssue Cycle TimeDaily WIPOpen PRsAging IssuesDeployDORA MetricsSprint ProgressSprintsPlanning AccuracyCode ReviewAging Branches
Context to provide

Provide Squad-Name and the week or date range. Confirm whether the squad uses sprints and choose issues or story points if sprint-planning signals should be included.

Copyable prompt
2,449 characters
ROLE Engineering consultant using MCP DevStats. OBJECTIVE Prepare a weekly squad review for a team lead or EM. Summarize delivery, flow, WIP, accumulation, and relevant sprint signals for a team conversation. Do not recommend actions, assign owners, score the squad, or decide priorities. ...

How the analysis runs

The weekly review aligns two equal windows, combines delivery and current-accumulation signals, and produces a compact discussion brief rather than an action plan.

  1. 01Scope and inputsSet the weekly comparisonConfirm Squad-Name, an inclusive seven-day window, the equivalent previous week, and sprint coverage before requesting any metrics.View detailsHide details
    Confirm Squad-Name, an inclusive seven-day window, the equivalent previous week, and sprint coverage before requesting any metrics.
  2. 02Analysis and evidenceAssemble delivery and accumulation signalsCompare throughput and flow while treating open work, WIP, and aging as current snapshots; include sprint or stability data only when relevant.View detailsHide details
    Compare throughput and flow while treating open work, WIP, and aging as current snapshots; include sprint or stability data only when relevant.
  3. 03Interpretation limitsPrepare the team discussion briefSelect only evidenced weekly changes, note missing coverage, and frame questions without owners, priorities, or recommended actions.View detailsHide details
    Select only evidenced weekly changes, note missing coverage, and frame questions without owners, priorities, or recommended actions.

Expected Output

Markdown · Illustrative example

Weekly Delivery Review — Squad-Name — 6–12 Jul 2026

Signals from the week

  • Merged PRs: 11 → 14; volume increased by 3 PRs.
  • PR Cycle Time: 5.1 → 4.6 days; pickup improved while review stayed near 1.8 days.
  • Issue Cycle Time: 7.9 → 8.4 days across 12 completed issues.

Current accumulation

SignalCurrent snapshotContext
Open PRs93 have been open for more than 5 days
Aging issues64 are in the same project

Sprint signals

Sprint 24 is 62% complete with 4 working days remaining; planning coverage is 91%.

Questions for discussion

  • What context explains the four aging issues in the same project?
  • Where are the three oldest PRs currently waiting?

Evidence used

  • Throughput — weekly delivery volume
  • PR Cycle Time — PR flow
  • Aging Issues — current accumulation

Stop guessing. Start asking.

Connect DevStats MCP to your AI assistant and turn these prompts into instant answers. Copy a prompt and go.

Get a demoStart free trial