Prompt detail

Sprint Signal Review

Review of sprint progress, WIP, aging work, and planning coverage as input for team discussion.

Prompt 07
Analyzed reports
Sprint ProgressSprintsPlanning AccuracyDaily WIPAging IssuesIssue ListOpen PRsAging BranchesThroughputPR Cycle TimeIssue Cycle Time
Context to provide

Provide Squad-Name, the sprint identifier or dates, and the planning unit (issues or story points). Confirm that sprint data is used consistently by the squad.

Copyable prompt
2,237 characters
ROLE Sprint delivery analyst using MCP DevStats. OBJECTIVE Review current or selected sprint signals for a squad. Show progress, planning coverage, WIP, and aging work as evidence for human adjustment. Do not predict sprint success, assign health status, recommend actions, or judge individuals. ...

How the analysis runs

The review validates sprint coverage, combines progress with current WIP and aging, and highlights discussion signals without predicting completion or judging planning quality.

  1. 01Scope and inputsValidate the sprint boundary and unitResolve Squad-Name, sprint dates, planning unit, and coverage so progress and planning values refer to the same committed population.View detailsHide details
    Resolve Squad-Name, sprint dates, planning unit, and coverage so progress and planning values refer to the same committed population.
  2. 02Analysis and evidenceRead progress, flow, and agingCombine sprint progress with WIP, aging issues, and current PR queues while keeping completed-flow metrics separate from open-work snapshots.View detailsHide details
    Combine sprint progress with WIP, aging issues, and current PR queues while keeping completed-flow metrics separate from open-work snapshots.
  3. 03Interpretation limitsFrame sprint discussion signalsCall out coverage gaps and concentrations, avoid completion forecasts, and ask context questions tied to the displayed sprint evidence.View detailsHide details
    Call out coverage gaps and concentrations, avoid completion forecasts, and ask context questions tied to the displayed sprint evidence.

Expected Output

Markdown · Illustrative example

Sprint Signal Review — Squad-Name — Sprint 24

Sprint scope

1–14 Jul 2026 · unit: issues · 22 planned issues · planning coverage: 95%.

Progress and flow

  • 14 of 22 issues complete (64%) with 4 working days remaining.
  • 6 issues in progress and 2 not started; this is a current snapshot, not a completion forecast.
  • Completed Issue Cycle Time is 6.9 days across 11 covered issues.

Aging and queue signals

SignalValueContext
Aging issues43 are older than 10 days
Open PRs72 are waiting in review

Questions for the team

  • What context applies to the three issues older than 10 days?
  • Are the two review queues connected to the same dependency?

Evidence used

  • Sprint Progress — current sprint state
  • Aging Issues — current aging work

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