Prompt detail

Work Mix Review

Reading of work distribution across roadmap, maintenance, bugs, hotfixes, rework, and similar categories.

Prompt 10
Analyzed reports
AllocationEngineering InvestmentInvestment ProfileWork BreakdownThroughputIssue ListPR List
Context to provide

Provide Squad-Name, a period (90 days is useful for a mix review), and the unit: issues or story points. Mention whether you want a snapshot or an equivalent-period comparison.

Copyable prompt
2,456 characters
ROLE Engineering work-mix analyst using MCP DevStats. OBJECTIVE Explain how a squad's work is distributed across available DevStats categories in a selected period. Show mix signals, interpretation limits, and strategic context questions. Do not judge strategy quality, infer value or productivity, or recommend reallocations. ...

How the analysis runs

The review aligns category reports to one scope and unit, shows the observed distribution once, and discusses strategic context without defining an ideal mix.

  1. 01Scope and inputsAlign scope, period, and unitConfirm Squad-Name, dates, issues or story points, and category coverage so overlapping investment reports are not compared as if identical.View detailsHide details
    Confirm Squad-Name, dates, issues or story points, and category coverage so overlapping investment reports are not compared as if identical.
  2. 02Analysis and evidenceMap the work-category distributionRead allocation, investment, profile, and code-mix categories with their own definitions, avoiding duplicate conclusions from overlapping labels.View detailsHide details
    Read allocation, investment, profile, and code-mix categories with their own definitions, avoiding duplicate conclusions from overlapping labels.
  3. 03Interpretation limitsFrame strategic context without a target mixExplain what the categories can and cannot show, disclose unmapped work, and ask about roadmap intent rather than prescribing reallocation.View detailsHide details
    Explain what the categories can and cannot show, disclose unmapped work, and ask about roadmap intent rather than prescribing reallocation.

Expected Output

Markdown · Illustrative example

Work Mix Review — Squad-Name — Q2 2026

Distribution of work

Category / reportValueWhat it measuresLimit
Roadmap / Allocation48%Planned roadmap issues6% unmapped
Unplanned / Allocation21%Work classified as unplannedDoes not identify urgency or value
Maintenance / Allocation25%Planned + unplanned maintenanceCategory overlaps KTLO semantics
Rework / Work Breakdown14%Code classified as reworkCode mix differs from issue mix

Mix signals

  • Roadmap and planned maintenance represent 67% of mapped issues.
  • Unplanned work moved from 16% to 21% versus the previous equivalent period.
  • Hotfixes account for 5 of 96 classified issues.

Data and interpretation limits

  • Six issues lacked an allocation category.
  • The mix does not establish value, waste, productivity, or an ideal allocation.

Strategic context questions

  • What planned event or policy affected unplanned work in June?
  • How does the team distinguish KTLO from planned maintenance?

Evidence used

  • Allocation — issue distribution
  • Work Breakdown — code mix

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