Skip to content
Back to skills

Success Metrics Evaluation

ASecurity

Evaluate delivery outcomes against defined success metrics and acceptance goals. Activate after Delivery to verify that delivered work creates real business and technical impact, not just output.

  • 162 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agentsgoperformance

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add digipulse-engineering/GAAI-framework --skill success-metrics-evaluation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Success Metrics Evaluation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Success Metrics Evaluation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/digipulse-engineering-success-metrics-evaluation/badge)](https://www.skillsdirectory.com/skills/digipulse-engineering-success-metrics-evaluation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: success-metrics-evaluation
description: Evaluate delivery outcomes against defined success metrics and acceptance goals. Activate after Delivery to verify that delivered work creates real business and technical impact, not just output.
license: ELv2
compatibility: Works with any filesystem-based AI coding agent
metadata:
  author: gaai-framework
  version: "1.0"
  category: cross
  track: cross-cutting
  id: SKILL-SUCCESS-METRICS-EVALUATION-001
  updated_at: 2026-02-26
  status: future
inputs:
  - contexts/artefacts/stories/**
  - acceptance_criteria
  - delivered_artefacts
  - defined_success_metrics
  - runtime_or_usage_data  (optional)
outputs:
  - metric_results
  - story_level_success_report
  - gap_analysis
  - improvement_recommendations
---

# Success Metrics Evaluation

## Purpose / When to Activate

Activate after Delivery to verify outcomes, not just outputs. Prevents "output without outcome."

Use when:
- Success metrics were defined in the PRD or Story
- Delivery is complete and runtime data is available
- Objective quality gates are required

---

## Process

1. Map each Story to its defined success metrics
2. Measure artefacts and runtime results against targets
3. Detect underperformance and partial success
4. Generate actionable improvement insights

---

## Outputs

- Story-by-story KPI report
- Metric vs target comparisons
- Identified gaps with root signals
- Improvement suggestions linked to backlog items

---

## Quality Checks

- Each metric is measured against a defined target
- Gaps are identified with root cause signals
- Recommendations are linked to specific backlog items
- No invented metrics — only those defined in artefacts

---

## Non-Goals

This skill must NOT:
- Redefine success metrics post-delivery
- Make product decisions about gaps
- Substitute for `qa-review`

**Ensures delivery creates real impact. Makes scaling predictable.**

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.