sprint-metrics

Compute cross-cycle sprint metrics from archived sprint data.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill sprint-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-metrics
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/sprint-metrics
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill sprint-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compute cross-cycle sprint metrics from archived data to reveal performance trends and bottlenecks across multiple cycles.

Core Features & Use Cases

  • Throughput and cycle-time analysis across cycles
  • Estimate-accuracy tracking and discipline-event monitoring
  • Per-sprint and per-cycle reporting for dashboards and retrospectives

Quick Start

Run the sprint-metrics command to generate the latest metrics from the archives.

Frequently Asked Questions about sprint-metrics

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

FAQPage Schema
How do I compute sprint metrics like throughput and cycle time from archived data?

Sprint metrics are computed from archived data sources like .sprints/archive to evaluate throughput, cycle time, and estimate accuracy across multiple cycles. The process enforces traceability to source files and exports a structured schema for reporting.

What is cross-cycle sprint performance analysis and when do I need it?

Cross-cycle sprint performance analysis evaluates throughput, cycle time, estimate accuracy, and discipline events across multiple sprints. It is needed to reveal performance trends and bottlenecks for agile team retrospectives and reporting dashboards.

Can I generate per-sprint and per-cycle metrics for agile retrospectives?

Yes, you can generate per-sprint and per-cycle metrics for retrospectives. The analysis aggregates throughput, cycle time, and estimate accuracy data across multiple cycles and exports the results in a structured schema for dashboards.

How do I track estimate accuracy and discipline events across multiple sprints?

Track estimate accuracy and discipline events by analyzing archived sprint records across multiple cycles. This provides visibility into estimate variance and process discipline, supporting per-cycle aggregation and structured exports for reporting.

Do I need a specific framework to analyze archived sprint data for dashboards?

No specific framework is required, but the analysis is applicable to software and product teams practicing agile sprint discipline. It relies on sources like .sprints/archive and related records to export metrics in a structured schema for dashboards.