velocity

Calculate team velocity metrics from sprint history and generate a velocity report.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill velocity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: velocity
Source: https://github.com/mahg-es/araya/tree/main/skills/velocity
Command: npx skills add https://github.com/mahg-es/araya --skill velocity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track, analyze, and forecast team velocity — the amount of work completed per sprint — using historical data to predict future capacity and identify improvement opportunities.

Core Features & Use Cases

  • Velocity tracking and forecasting based on sprint history.
  • Generate reports showing velocity trends, completion rates, and capacity planning.
  • Use cases: forecast project timelines, identify process improvements, plan staffing.

Quick Start

Provide a velocity forecast from the latest sprint history and generate a velocity report.

Frequently Asked Questions about velocity

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

FAQPage Schema
How do I forecast sprint capacity using historical agile velocity data?

Sprint capacity forecasting uses historical agile velocity data to calculate rolling averages and completion rates, predicting future output and guiding sprint planning. It analyzes sprint history to generate reports showing team performance trends.

What agile metrics are used to measure team performance and predict project completion?

Agile metrics for team performance include velocity, rolling averages, completion rates, carry-over, and variability. Computing these from sprint history evaluates process changes and identifies improvement opportunities to forecast project timelines accurately.

Can I track sprint carry-over and variability to improve agile planning?

Yes, tracking sprint carry-over and variability improves agile planning by identifying process bottlenecks. Calculating these metrics from sprint history helps evaluate the impact of process changes across sprints for better capacity forecasting.

Does this velocity forecasting tool require specific agile framework dependencies?

No specific agile framework dependencies are required. The tool operates independently using sprint history data to compute velocity metrics, rolling averages, and completion rates for sprint planning and project timeline forecasting without external components.

When should I use rolling averages instead of raw velocity for sprint planning?

Use rolling averages for sprint planning when raw velocity shows high variability across sprints. Averaging multiple sprints smooths out anomalies, providing a reliable capacity forecast that helps evaluate process changes and guide staffing decisions accurately.