Azure DevOps

Sprint reports, work-item rollups, and stakeholder views the canned dashboards won't deliver. Each entry ships with the tool, a user guide, and the prompts to build a similar one yourself.

→ Entry 01 PowerShell · Local · ~1 hr setup →

Sprint Report Builder

A self-contained tool that pulls your iteration data from Azure DevOps and produces a single-page sprint report — burn-up chart with goal and plan lines, work-item table with configurable columns. Runs locally; no data leaves your machine.

→ Entry 02 PowerShell · Local · Demo + live mode →

PR Aging Report

A local tool that pulls every active pull request from your Azure DevOps project and buckets them by days open (Fresh / Aging / Stale / Forgotten). Plus dedicated callouts for the two most common stuck patterns — PRs with no reviewers assigned, and PRs with reviewers but no approvals — and a per-repo aging breakdown. Bundled 25-PR demo fixture; live mode points at your own org.

→ Entry 03 PowerShell · Local · Compliance audit →

Policy Bypass Audit

A local tool that produces the branch-policy bypass audit your quarterly compliance review asks for: total in window, top actor, top repo, monthly timeline, by-actor / by-repo / by-reason breakdowns, full chronological log. Green/amber verdict from two threshold heuristics (volume + concentration). Bundled 18-event demo fixture; live mode (ADO Audit Log API) deferred to v2 because it requires Project Collection Administrator access.

→ Entry 04 PowerShell · Local · Cross-pipeline rollup →

Pipeline Reliability Report

A local tool that pulls Azure DevOps pipeline runs and rolls up failure rate, top failing tests, and top flaky tests across pipelines. ADO has Test Analytics for one pipeline at a time; this adds the cross-pipeline view eng managers actually want. Bundled 60-run / 3-pipeline demo fixture engineered to land in each failure-rate bracket (10% green, 30% red, 45% red). Live mode deferred to v2.

Claude could write this. Two reasons to prefer the script.

Some workplaces — defense, medical devices, finance, anywhere with a strict IT policy — won't let Claude or any AI tool touch production data. These tools run on your machine, with no Claude or AI in the data path — your Azure DevOps organization's data flows direct from your machine to dev.azure.com and back, no third-party SaaS in between, no telemetry, no tokens leaving your environment. And even where AI is allowed, repeat workflows shouldn't cost tokens — a deterministic script runs the same way every time, for free, forever. The prompt guide on each entry shows how the tool was built with Claude; the downloads are what you run after.