delivery-metrics

Derives DORA and Flow Framework delivery metrics from cost-ledger timestamps and delivery-ledger events.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill delivery-metrics-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-metrics
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/delivery-metrics
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill delivery-metrics-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Engineering teams track token costs but lack visibility into actual delivery performance — how fast and how reliably they ship. This Skill computes the DORA four keys plus reliability and Flow Framework metrics from data the harness already records, turning raw timestamps and incident events into banded performance reports without manual data collection. ## Core Features & Use Cases - DORA metrics report: Computes deployment frequency, lead time for change, change failure rate, MTTR, and reliability, banded against the 2024 DORA State of DevOps clusters (elite/high/medium/low). - Flow Framework metrics: Calculates flow efficiency (active time ÷ total flow time), flow time, and flow load from per-phase cost-ledger checkpoints. - Event-driven delivery ledger: The delivery-record script upserts deploy, incident-start, incident-resolve, and SLO events into a JSONL ledger so failure-dependent keys reflect real events rather than hand-edited data. - Anti-fabrication guardrails: Withholds any metric whose input signal is missing (e.g., prints "needs incident linkage") instead of reporting a fabricated zero, and a reviewer gate validates the report before stakeholder use. - Use Case: After merging a feature branch, run the report to see your lead time band and change failure rate for the last 30 days, then feed MTTR trends back into incident-response and error-budget policy. ## Quick Start Run the delivery metrics report for the last 30 days and show my DORA bands and flow efficiency.

Frequently Asked Questions about delivery-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure DORA metrics for my team?

Run the dora-report script with an optional --since window to compute deployment frequency, lead time, change failure rate, MTTR, and reliability. Results are banded against the 2024 DORA State of DevOps clusters rather than raw numbers.

How is flow efficiency calculated in software delivery?

Flow efficiency is active work time divided by total flow time, using the standard lean formula. It is only reported when active_seconds is captured per step in the cost-ledger; otherwise the report withholds it rather than approximating from time gaps.

What data sources does the DORA report need?

It reads the engineer cost-ledger JSONL for timestamps and cycle time, plus a delivery ledger populated by deploy, incident-start, incident-resolve, and SLO events. Git commit timestamps and incident postmortems supply the failure-dependent signals.

Why does the report say needs incident linkage?

Change failure rate, MTTR, and reliability require a real failure signal that timestamps alone cannot provide. Until incident events are recorded via delivery-record, the report prints needs incident linkage instead of fabricating a zero.

Can DORA metrics show whether a feature succeeded?

No. DORA metrics measure delivery speed and stability, not business outcomes. An elite DORA band indicates a healthy delivery machine; whether a shipped feature achieved its goal must be measured separately against the spec's north-star metric.