Prompt detail

Aging Issues Investigation

Investigation of old in-progress work to understand where it is concentrated before discussing cause, priority, or owners.

Prompt 02
Analyzed reports
Aging IssuesIssue ListDaily WIPIssue Cycle TimeOpen PRsAging Branches
Context to provide

Provide Squad-Name or a project, and optionally a recent period for resolved-flow context. Mention whether you want only the current aging snapshot or also a comparison with WIP and cycle time.

Copyable prompt
2,405 characters
ROLE Engineering workflow investigator using MCP DevStats. OBJECTIVE Map currently aging in-progress issues for a squad or project context. Show where work is accumulating, what evidence exists, and what context questions should be asked. Do not prioritize items, declare blockers, assign owners, or prescribe next actions. ...

How the analysis runs

The investigation inventories current aging work, groups it by observable concentration, and separates what the records show from assumptions about blockers, urgency, or ownership.

  1. 01Scope and inputsDefine the active-work boundaryResolve Squad-Name or project scope and decide whether the question concerns the current snapshot alone or needs recent resolved-flow context.View detailsHide details
    Resolve Squad-Name or project scope and decide whether the question concerns the current snapshot alone or needs recent resolved-flow context.
  2. 02Analysis and evidenceMap where aging work concentratesInventory current aging issues, then group available records by age band, status, or project without assigning priority or inferring a blocker.View detailsHide details
    Inventory current aging issues, then group available records by age band, status, or project without assigning priority or inferring a blocker.
  3. 03Interpretation limitsBound findings with record-level evidenceUse listed issues only as evidence for those records, state missing fields, and convert possible dependencies or queue effects into questions.View detailsHide details
    Use listed issues only as evidence for those records, state missing fields, and convert possible dependencies or queue effects into questions.

Expected Output

Markdown · Illustrative example

Aging Issues Investigation — Squad-Name

Current aging issues

IssueAgeStatus / projectWhat it shows
ENG-14231 daysIn Progress / CheckoutOldest active record in the selected scope
ENG-18724 daysReview / CheckoutOne of 4 records concentrated in review
ENG-20319 daysIn Progress / PlatformAbove the squad's current 14-day aging band

Concentration patterns

  • 4 of 7 aging issues are in review; this shows concentration, not the reason for waiting.
  • The Checkout project contains 5 of 7 listed records.

Flow context

Resolved Issue Cycle Time was 8.6 days over the last 30 days; it does not predict completion of current issues.

Context questions

  • Which policies or dependencies apply to the four issues currently in review?
  • Are the Checkout records part of one shared delivery path?

Evidence used

  • Aging Issues — current snapshot
  • Issue Cycle Time — resolved-flow context

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