success-metrics-evaluation

$npx mdskill add Fr-e-d/GAAI-framework/success-metrics-evaluation

Evaluates delivery outcomes against success metrics to ensure real business impact

  • Identifies stories mapped to defined success metrics for evaluation.
  • Deploys a toolset that includes acceptance criteria and runtime data analysis.
  • Decides on performance by comparing artefacts with predefined targets.
  • Generates actionable insights into areas needing improvement.

SKILL.md

.github/skills/success-metrics-evaluationView on GitHub ↗
---
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.**

More from Fr-e-d/GAAI-framework

SkillDescription
abort-safe-handlerOrchestrator-level Stage 4 entry gate for /gaai:bootstrap. Presents a pre-loop "Skip Q&A entirely" option, delegates to qa-loop-ui when the user proceeds, and returns a unified abort_safe_result with telemetry on every path. Guarantees no partial state on skip or abort.
ambiguity-detectorTakes surface scan results, optional LLM synthesis open-question entries, and optional tree-sitter AST signals to score project ambiguities (1-10). Outputs structured ambiguity_feed for smart-question-generator. Pure heuristic — no LLM calls. Designed for Stage 3.5 of the /gaai:bootstrap pipeline (between LLM synthesis and Q&A).
approach-evaluationResearch industry standards and best practices, identify viable approaches for a given technical or architectural problem, and produce a structured factual comparison against project-specific constraints. Reports options — does not decide.
architecture-extractConvert raw project structure into clear architectural understanding — module boundaries, data flows, service relationships, and architectural patterns. Activate after codebase-scan during Bootstrap.
bootstrap-llm-synthesisConstruct the LLM synthesis prompt from project surface scan + optional tree-sitter context + optional Q&A answers. Call the LLM. Parse and validate the response into 6-8 structured memory entries with clarity tags and source traceability. Used as Stage 3 of the /gaai:bootstrap pipeline.
bootstrap-memory-ingest-cloudWrite structured memory entries to the Cloud workspace via gaai_memory.store MCP tool with source='bootstrap'. Loops over entries from bootstrap-llm-synthesis, calls the tool per entry, collects success/fail counts. Used as Stage 5 of the /gaai:bootstrap pipeline (Cloud path only).
browser-journey-testValidate user stories by simulating real user journeys in a live browser against deployed application. Activate after implementation to verify actual user experience against acceptance criteria, not just code logic.
build-agents-indexScan all agent and sub-agent definition files in .gaai/core/agents/, extract YAML frontmatter, merge with specialists.registry.yaml, and generate a derived agents-index.yaml at .gaai/core/agents/agents-index.yaml. Activate after adding, modifying, or removing any agent, sub-agent, or specialist entry.
build-skills-indexScan SKILL.md files in .gaai/core/skills/ and .gaai/project/skills/, extract YAML frontmatter, and regenerate separate skills indices for each layer. Core index ships with the OSS framework; project index is project-specific.
ci-watch-and-fixWatch GitHub Actions CI after PR creation, detect failures, extract logs, apply minimal fixes, and re-push — keeping the delivery session alive until CI resolves or escalating after 3 cycles. Activate immediately after gh pr create and before marking the story done.