Prompt detail

Operational Concentration Review

Analysis of concentrated work, reviews, or operational context across people, areas, or repositories.

Prompt 09
Analyzed reports
List PlayersPlayer MetricsPR ListIssue ListCode ReviewOpen PRsAging IssuesAging BranchesWork BreakdownActivity Heatmap
Context to provide

Provide Squad-Name, a period, and the concentration dimension you want to inspect: contributors, reviewers, repositories, projects, or work areas. State whether identities should remain anonymized.

Copyable prompt
2,562 characters
ROLE Engineering resilience analyst using MCP DevStats. OBJECTIVE Identify signals that work, review activity, or ownership-like activity may be concentrated in few people or contexts. Frame this as operational resilience evidence. Do not evaluate individual performance, label a person as a risk, prescribe mitigation, or rank people. ...

How the analysis runs

The review defines a valid denominator, measures concentration in the requested dimension, and reports operational dependency signals without evaluating individuals.

  1. 01Scope and inputsDefine the concentration questionConfirm Squad-Name, period, dimension, denominator, and privacy boundary so the analysis measures the intended operational distribution.View detailsHide details
    Confirm Squad-Name, period, dimension, denominator, and privacy boundary so the analysis measures the intended operational distribution.
  2. 02Analysis and evidenceMeasure the observed distributionCalculate shares and coverage from the relevant review, delivery, repository, or work records and identify only evidenced concentrations.View detailsHide details
    Calculate shares and coverage from the relevant review, delivery, repository, or work records and identify only evidenced concentrations.
  3. 03Interpretation limitsSeparate dependency signals from judgmentDescribe concentration as an operational pattern, anonymize people by default, and state that share does not prove workload, performance, or risk.View detailsHide details
    Describe concentration as an operational pattern, anonymize people by default, and state that share does not prove workload, performance, or risk.

Expected Output

Markdown · Illustrative example

Operational Concentration Review — Squad-Name — Q2 2026

Scope and coverage

PR reviews · 84 merged PRs · 79 with complete reviewer data (94% coverage).

Observed distribution

ReviewerReviewsShareWhat it shows
Contributor A4138%Largest observed share
Contributor B2624%Second-largest share
Other contributors4138%Distributed across 7 people

Concentration signals

  • The two largest shares account for 62% of covered review events.
  • 3 repositories account for 71% of Contributor A's reviews.

Interpretation limits

  • Review count does not measure effort, depth, quality, availability, or performance.
  • Five merged PRs lacked complete reviewer data.

Context questions

  • Which repository policies or expertise boundaries shape this distribution?
  • How are review requests routed for the three concentrated repositories?

Evidence used

  • Code Review — review-event distribution
  • PR List — repository coverage validation

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