developer-productivity

Translate DORA and DevEx signals into engineering management insights.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill developer-productivity-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-productivity
Source: https://github.com/imsus/cto/tree/main/.agents/skills/developer-productivity
Command: npx skills add https://github.com/imsus/cto --skill developer-productivity-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps engineering managers measure and improve team productivity without misleading metrics that get gamed or demotivate engineers.

Core Features & Use Cases

  • DORA delivery measurement: Uses deployment frequency, lead time, change failure rate, and MTTR to assess delivery system health and correlate with business outcomes.
  • DevEx friction diagnosis: Breaks developer experience into feedback loops, cognitive load, and flow state to find what’s slowing engineers down.
  • Business translation: Connects engineering delivery signals to customer and commercial metrics (e.g., reliability reducing support cost, lead time improving time-to-market).
  • Anti-pattern guardrails: Avoids common measurement failures like SLOC, raw velocity, and especially using metrics to evaluate individuals.

Quick Start

Ask the skill for a DORA-and-DevEx measurement plan for your team, then tell it what your current bottleneck feels like (for example, slow releases, long lead time, or frequent incidents).

Frequently Asked Questions about developer-productivity

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

FAQPage Schema
How do I measure developer productivity using DORA metrics without demotivating my team?

DORA delivery measurement uses four signals—deployment frequency, lead time for changes, change failure rate, and mean time to recover—to assess delivery system health and correlate engineering performance with business outcomes like time-to-market.

How do I diagnose why cycle time and developer velocity are poor?

DevEx friction diagnosis breaks developer experience into feedback loops, cognitive load, and flow state to find what’s slowing engineers down. This method pinpoints specific bottlenecks in the delivery system rather than blaming individual performance.

How do I connect engineering metrics to business outcomes for leadership reporting?

Business translation connects engineering delivery signals to customer and commercial metrics, such as mapping reliability to reduced support cost and lead time to improved time-to-market, enabling engineering managers to explain performance to leadership.

What are common metric anti-patterns to avoid when tracking engineering team performance?

Anti-pattern guardrails avoid common measurement failures like tracking SLOC, raw velocity, and especially using metrics to evaluate individuals. These practices get gamed and demotivate engineers, undermining accurate delivery health assessment.

Can I use this approach to measure delivery health for a single engineering team?

Yes, this approach provides team-level measurement guidance using DORA and DevEx concepts. It is designed for engineering managers diagnosing specific team bottlenecks like slow releases, long lead time, or frequent incidents within their immediate scope.