Prompt detail

Engineering Flow & Stability Review

Comparison of two equivalent squad periods to understand changes in flow, volume, WIP, and stability.

Prompt 05
Analyzed reports
PR Cycle TimeIssue Cycle TimeThroughputDeployDORA MetricsDaily WIPCode ReviewAging BranchesAging Issues
Context to provide

Provide Squad-Name and a current period, normally 30 days. Add repository filters only when needed and identify whether deployment stability should be part of the review.

Copyable prompt
3,183 characters
ROLE Engineering consultant using MCP DevStats. OBJECTIVE Compare a squad's current delivery period with the previous equivalent period to understand changes in flow, volume, work in progress, and stability. Turn DevStats data into a concise, evidence-based review, highlights current accumulations and divergent signals, and provides contextual questions for team discussions. ...

How the analysis runs

The review compares equivalent periods across flow, volume, WIP, and stability, then highlights converging or conflicting signals with explicit comparability limits.

  1. 01Scope and inputsCreate equivalent review periodsAlign Squad-Name, dates, repositories, units, and temporal semantics before comparing the current window with the previous one.View detailsHide details
    Align Squad-Name, dates, repositories, units, and temporal semantics before comparing the current window with the previous one.
  2. 02Analysis and evidenceRead flow and stability togetherCompare cycle time, throughput, deployments, DORA dimensions, and WIP while drilling only into the stages or accumulations that changed materially.View detailsHide details
    Compare cycle time, throughput, deployments, DORA dimensions, and WIP while drilling only into the stages or accumulations that changed materially.
  3. 03Interpretation limitsSurface tensions and limitsExplain where signals move together or diverge and state what the available windows cannot establish about cause, value, or team health.View detailsHide details
    Explain where signals move together or diverge and state what the available windows cannot establish about cause, value, or team health.

Expected Output

Markdown · Illustrative example

Engineering Flow & Stability Review — Squad-Name — Jun 2026

Period comparison

SignalPreviousCurrentEvidence-led read
PR Cycle Time4.8 days6.1 daysReview added 1.0 day
Merged PRs3941Volume remained similar
Deployments1215Deployment frequency increased
Change Failure Rate9%16%3 of 19 covered changes failed

Current accumulation

  • 12 open PRs, including 4 older than 7 days.
  • Daily task WIP ended at 23, compared with 17 at the previous period end.

Tensions

  • Deployment volume rose while change failures also increased; the relationship needs release context.
  • PR volume stayed stable while review time increased.

Interpretation limits

  • Incident linkage coverage was 84% in the current period.
  • Two periods show a change, not a durable trend.

Evidence used

  • PR Cycle Time — flow comparison
  • DORA Metrics — stability dimensions
  • Daily WIP — 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