AI prompt library for engineering leaders

Turn your engineering data into leadership updates, retro insights, and 1:1 prep. Copy a prompt into your AI assistant connected to DevStats and get a deck, spreadsheet, dashboard, or memo.

  • An example for every prompt
  • Conclusions, not just numbers
  • Free to copy
pptx6-slide deckSee prompt

Browse the library

Pick the moment you are in. Every prompt ends in something you can send.

Showing 16 prompts

MONTHLY ENGINEERING UPDATE 1 / 6 We shipped 50% more than the month before.Less of it was new.PRS MERGED352234 the month beforeEFFORT ON NEW15%46% the month beforePLAN DELIVERED66.7%89.4% the month before

Monthly engineering update for leadership

A six-slide deck with what changed, where the effort went, and the one ask for leadership.

pptx6-slide deck
WHERE THE CYCLE TIME GOES 2d 9h 32% 10% 51% CODING3h 32mPICKUP15h 19mREVIEW4h 44mDEPLOY1d 1hDeploy owns half of the time, pickup a third.

Where is our PR flow losing time?

Find the stage that owns the delay, the outliers hiding inside the average, and the first move.

mdDiagnosis + order of attack
D3 dev-3LAST 30 DAYS VS THE 30 BEFOREPRS MERGED149 ▲ from 124ISSUES RESOLVED125 ▲ from 84REVIEWS GIVEN108 ▲ from 761. RECOGNIZE2. ASK ABOUT3. WHAT I OWE4. GROWTH

Prepare a 1:1 with a developer

What to recognize, what to ask about, and what you owe them, built from their last month of work.

mdConversation guide
SHARE HELD BY ONE PERSONDevelopment projectdev-370% Support projectdev-265% site repositorydev-766% devstats repositorydev-347%

Who is a single point of failure?

A risk map of the repositories and projects that depend on one person, with the smallest fix for each.

mdRisk map + mitigation
ITEMS37CLOSE14FIX STATUS1KEEP22BRANCHAGE (DAYS)fix/aikido-security-update-pack…98Closefeature/sup2-812-fix-off-by-one…79Closefix/code-review-controls-panel…9Keep

Clean up stale work

Every stale PR, branch and issue in one spreadsheet, each with a recommended action and the reason.

xlsxPrioritized spreadsheet
APP SQUAD LIVEPRS MERGED324▲ +40%PR CYCLE TIME2d 9h+12%DEPLOYS168+2%FAILURE RATE2.4%was 1.8%WHERE THE CYCLE TIME GOES32% 10% 51%

Build a live squad dashboard

One page that answers in five seconds: are we shipping, is anything stuck, are we stable.

htmlLive HTML dashboard
30-DAY BRIEFApp squadLAST 90 DAYSPRS MERGED737▲ from 339DEPLOYS513▲ from 339PLANNING ACCURACY62.4%▲ from 53.7%1. GOOD AT2. FRUSTRATIONS3. INHERITED4. 10 QUESTIONS

Taking over a team: 30-day brief

How the team really works, what it is good at, what you inherited, and ten questions for your first month.

mdMemo for your first 30 days
TRIAGEGTMNEEDS HELPFlow frictionSupportWATCHStuck items, not overloadAppHEALTHYLeave aloneNot a ranking: each squad against itself.

Which squad needs help?

A triage of your squads: who is struggling, with what, which kind of help fits, and who to leave alone.

mdFair comparison, no ranking
QUARTER IN REVIEW 1 / 9 Engineering shipped more than twice as much,planned twice as much of it,and broke half as often.PRS MERGED783336 last quarterROADMAP SHARE69%34% last quarterFAILURE RATE2.1%4.3% last quarter

Quarter in review, squad by squad

A deck that tells each squad in one line, shows where the quarter went, and sets the capacity for the next one.

pptxSquad-by-squad deck
PAYING OFFBEFORE ROLLOUTLAST 90 DAYSMerged PRs335→838Coding time per PR16h 46m→3h 23mRework8.9%→17.7%ILLUSTRATIVE

Is our AI spend paying off?

From seats paid to delivery outcomes: what is used, what changed since the rollout, and what to keep, expand or cut.

mdBefore/after deck or memo
HABITUAL OR ABOVE5 of 7SEATS TO RECLAIM9A MONTH$213PLAYERACTIVE DAYS PER TOOLdev-1Cursor 21 · Claude Code 17Power userdev-2Cursor 19Habitualdev-5Claude Code 3Tryingdev-6—Not usingILLUSTRATIVE

AI adoption map: who uses what, and where it has not landed

A spreadsheet of adoption by person and squad, the seats to reclaim, and a three-step enablement plan.

xlsxSpreadsheet + summary
100% DONEON TRACKDAY 16 OF 16THIS CYCLE 100% OUR NORMAL CYCLE 62.4% 162 issues, nothing to descope

Mid-sprint: are we going to make it?

A straight verdict on the sprint, what will land, what will not, and what to descope today.

mdRisk verdict + descope list
THE SPRINT IN NUMBERS CYCLE 53 CYCLE 51 Committed16366Completed99%89.4%PR cycle time1d 10h17h 14mRework share25.6%17.3%

Sprint retro with evidence

Three themes backed by data, a question to open each one, and an experiment for the next sprint.

mdThemes + next experiments
SHARE OF RESOLVED ISSUES90 days before33% 63% Last 90 days65% 33% 70% EXPECTEDROADMAPUNPLANNED WORKUNPLANNED MAINTENANCE

Where does engineering time go?

The answer in one sentence, a chart of roadmap vs everything else, and two levers to shift the split.

htmlInvestment memo with a chart
DORA SCORECARD, LAST 90 DAYSLEAD TIME1d 20hHigh tierDEPLOY FREQUENCY513deploys, Elite tierCHANGE FAILURE RATE3.1%was 4.4%TIME TO RECOVERY5d 10h40% slower

DORA scorecard vs benchmarks

Where you stand on the four DORA metrics, the one to fix first, and the practices that move it.

mdOne-pager vs industry tiers
# squad-appWEEKLY DELIVERY SYNC EM Engineering ManagerApp, this weekWHAT MOVED77 PRs merged, 53 the week beforePR cycle time 1d 22h, down from 4d 20h40 deploys, up from 20

Before your weekly delivery sync

Know what moved, what is stuck and what to do about it, with a Slack post ready to paste.

mdSlack-ready post + 3 actions

How it works

  1. 01

    Connect DevStats MCP

    Add the DevStats MCP server to Claude, ChatGPT, Cursor or your own app.

    Set up DevStats MCP
  2. 02

    Copy a prompt

    Pick the ceremony you are preparing for. Fill in the [bracketed] placeholders or leave them: the assistant asks for what is missing.

  3. 03

    Get the deliverable

    The assistant pulls your real DevStats metrics, reaches a conclusion and hands you the deck, the spreadsheet, the dashboard or the memo.

Stop guessing. Start asking.

Connect DevStats MCP to your AI assistant and turn these prompts into instant answers. Copy a prompt and go.