Jira

Sprint trust reports, cross-project queries, and the views Jira's own dashboards won't give you straight. Each entry ships with the tool, a user guide, and the prompts to build a similar one yourself.

Sprint Trust Report
A local tool that reconciles Jira's contradictory sprint numbers — Velocity Chart vs Sprint Report vs the actual issue history — and names the specific issues responsible for the drift. Scope creep, de-scoped issues, workflow re-closures, mid-sprint estimate changes: every category, every issue, every timestamp.
Stale Epics Report
A local tool that walks every epic in a Jira project via the REST API and classifies each by days since last activity (Fresh / Slowing / Stale / Cold / Frozen). One HTML page, broken items first. Plus a "what's still moving" callout for the trust signal and a no-children list for the epics that probably need closing. Bundled 20-epic demo fixture runs end-to-end with no Jira creds; live mode points at your own project.
Bug Aging Report
A local tool that pulls every unresolved bug in a Jira project and renders a 4 × 4 age × priority matrix — the cross-cut Jira's Average Age report doesn't give you. Plus per-bucket bug tables (Stale first), an oldest-unresolved top-10 list, an oldest-Highest callout with a healthy-state explicit count, and a bugs-by-component breakdown. Bundled 30-bug demo fixture engineered to land in every matrix cell.
Velocity Drift Report
A local tool that walks the last 6 sprints, computes per-sprint committed vs delivered, and flags chronic patterns per assignee — Sandbagger (delivers >=130% in 4+ sprints) and Over-promiser (delivers <=70% in 4+ sprints). The signal Jira's Velocity Chart hides because it aggregates at the team level. One HTML page, GREEN/AMBER/RED verdict, trend split (last 3 vs prior 3), top dropped issues. Bundled 6-sprint Aegis Platform fixture engineered for AMBER verdict with 1 sandbagger + 2 over-promisers.

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 Jira instance data flows direct from your machine to your-tenant.atlassian.net 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.