Dora Metrics Reviewer

Benchmark your DevOps performance against DORA standards and generate a prioritized 90-day improvement roadmap.

Install
cmdop skills install agensi-dora-metrics-reviewer

The DORA Metrics Reviewer is a skill that evaluates software delivery performance using the four metrics defined by the DevOps Research and Assessment framework: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Restore (MTTR). Given raw team data as input, the skill classifies the team into a delivery tier — Elite, High, Medium, or Low — based on DORA research standards.

Beyond classification, the skill identifies which single metric is acting as the primary bottleneck on delivery velocity, explains how outlier metrics affect overall delivery stability, and produces a concrete 90-day execution plan. That plan includes specific technical practices such as implementing feature flags or adopting trunk-based development, ordered according to a hierarchical logic — for example, addressing Lead Time before targeting Deployment Frequency improvements.

The output is structured as a standardized report intended for stakeholder review, making it suitable for engineering leads who need to present delivery improvement plans to management. The skill is designed to produce actionable, engineering-specific recommendations rather than generic process advice.

This is a skill, not an MCP server, so it has no exposed tools and does not connect to external data sources or APIs. It works by processing the team metrics supplied to it and applying DORA-framework reasoning to generate the diagnostic report and roadmap.

Use cases

  • Classify a team's current delivery tier based on observed Deployment Frequency, Lead Time, Change Failure Rate, and MTTR
  • Identify the single metric most constraining a team's deployment velocity
  • Generate a 90-day technical improvement roadmap ordered by DORA-framework priority
  • Prepare a standardized DORA performance report for engineering leadership or stakeholder review
  • Evaluate how a single underperforming metric affects overall delivery stability
  • Determine which engineering practices — such as trunk-based development or feature flags — to adopt next

When to use it

  • When an engineering team wants to benchmark delivery performance against DORA standards
  • When an engineering lead needs a structured improvement plan to present to stakeholders
  • When a DevOps practitioner needs to identify the highest-leverage metric to improve first
  • When a team has collected data on deployment frequency, lead time, change failure rate, and MTTR and wants an interpreted report

When not to use it

  • When real-time or automated ingestion of CI/CD pipeline data is needed — this skill does not connect to external tools or APIs
  • When the goal is to monitor or alert on live deployment metrics rather than produce a diagnostic report
  • When no DORA metric data is available to supply as input
  • When integration with a specific ticketing, version control, or incident management platform is required