DORA Capability Assessment

Overview

Draft and maintain the DORA capability assessment document: technical and cultural capabilities that drive delivery performance, with evidence and maturity per capability, linked to the four key metrics.

Getting Started

Add your source materials to the project workspace, then activate the DORA Capability Assessment skill. The agent will guide you through the process step by step.

Example Conversation

Below is an example of how a typical DORA capability assessment session unfolds. The agent confirms scope and then drafts the capability assessment document.

You: We need a DORA capability assessment for our platform team. Cover CI, CD, and culture with evidence and maturity.

Agent: I’ll draft the DORA capability assessment. Do you have existing evidence in the workspace (e.g. pipeline configs, runbooks, survey results) I should reference, or should I create a structure with placeholders?

You: We have a short pipeline doc and our last team health survey. Use those and add placeholders for evidence we’re missing.

Agent: I’ve loaded the DORA capabilities reference. I’ll create sections for technical capabilities (CI, CD, trunk-based development, test automation, monitoring) and cultural capabilities, with current state, evidence, and maturity. I’ll link each to the four key metrics where relevant and add a short gaps and recommendations section.

Sample Output Excerpt

Below is a representative excerpt from a DORA capability assessment document.

Technical capabilities

Link to metrics

CI and CD support our lead time (median 2 days) and deployment frequency (12/week). Manual production gate is the main constraint on increasing deployment frequency.

Extension and validation

This skill does not include custom validation tools. Elaboration is guided by the workflow in the skill and the DORA capabilities reference. You can add extension tools later (e.g. to check coverage of capability categories) by editing the skill’s extension.ts.