# Quality Metric Validator (COBIT APO11)

> Define quality standards for IT services and SDLC aligned to COBIT APO11. Suggest quality gates based on Capability Levels. Includes SLA–quality sync check.



Tags: COBIT, APO11, Quality, QMS, SLA, PDCA


## Example Prompts

- Suggest quality gates for our SDLC based on COBIT Capability Levels
- Ensure our Quality Management Plan thresholds match our SLAs
- Define our QMS narrative and Continuous Improvement loop (PDCA)

URL: https://rakenne.app/skills/quality-metric-validator/index.md

Try this skill: https://rakenne.app/a/?skill=quality-metric-validator



## Overview

Define quality standards for IT services and SDLC aligned to COBIT APO11. Suggest quality gates based on Capability Levels. Includes SLA–quality sync check.

## Example Conversation

> **You:** Our SLAs promise 99.9% uptime and 4-hour response for P1. I need a Quality Management Plan that matches those commitments and quality gates for the SDLC.

> **Agent:** I'll draft the Quality Management Plan with internal thresholds that match or exceed your SLAs (99.9% uptime, 4h response), plus quality gates for the SDLC (e.g. test coverage, defect rates), then run `sla_quality_sync`.

> **Agent:** Created `quality-plan-apo11.md`. Running `sla_quality_sync` (plan + SLA doc)...

> **Agent:** **PASS** — SLA metrics (99.9%, 4h) have matching or stricter thresholds in the plan (internal target 99.95%, 3h response). Plan and SLA are in sync. I've also added a short PDCA/continuous improvement section.

## What the Tools Validate

**`sla_quality_sync`** ensures the Quality Management Plan's thresholds match or exceed the Service Level Agreements promised to customers:

- **Inputs:** Path to the Quality Management Plan; optional path to a separate SLA document. If no SLA path is given, the tool uses the same document.
- **Detection:** Extracts SLA metrics (e.g. uptime %, response time) and quality plan thresholds (target/ minimum uptime, response time) from both documents.
- **Rule:** For every SLA commitment, the plan should have a matching or stricter threshold (e.g. SLA 99.9% → plan ≥ 99.9%). FAIL if SLA metrics exist but plan thresholds are missing or lower.
- **Output:** PASS if plan and SLA are in sync (or no SLA to compare); FAIL with guidance to align plan thresholds to SLAs (APO11).

## Output Excerpt

**Quality Plan (excerpt):**

```markdown
## Service quality thresholds (APO11)

- **Availability:** Internal target 99.95% (SLA 99.9%).
- **P1 response time:** Internal target 3 hours (SLA 4 hours).
- **SDLC quality gates:** Unit test coverage ≥ 80%; no critical defects open at release.
- **PDCA:** Quarterly review of metrics and improvement actions.
```

**sla_quality_sync report (excerpt):**

```
=== SLA QUALITY SYNC (APO11) ===
Result: PASS

Quality Plan: quality-plan-apo11.md. SLA: slas.md.
SLA metrics found: 2 (e.g. 99.9, 4).
Quality plan thresholds found: 2.
Plan and SLA are in sync (or no SLA to compare).
SLA–quality sync OK.
```

## Getting Started

Add your SLA document (or commitments) and any existing quality or SDLC standards to the project workspace, then activate the *Quality Metric Validator (COBIT APO11)* skill. The agent will draft the plan and run `sla_quality_sync`; align thresholds and re-run until in sync.


---

Back to [Skill Library](https://rakenne.app/skills/index.md)