compute-velocity

Compute per-sprint velocity from completed story points and generate velocity reports.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/yannmenec/delivery-management-skills --skill compute-velocity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compute-velocity
Source: https://github.com/yannmenec/delivery-management-skills/tree/main/archive/v1/skills/sprint-operations/compute-velocity
Command: npx skills add https://github.com/yannmenec/delivery-management-skills --skill compute-velocity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Velocity analysis for sprint planning and forecasting is automated, reducing manual calculation errors and enabling faster decisions.

Core Features & Use Cases

  • Compute per-sprint velocity from completed work
  • Generate trend, predictability, and forecasts for current sprint
  • Support sprint planning and retrospectives with data-driven insights

Quick Start

Provide sprint history and current sprint progress to generate a velocity report.

Frequently Asked Questions about compute-velocity

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

FAQPage Schema
How do I calculate sprint velocity from historical sprint data?

You can calculate sprint velocity by analyzing completed story points across your sprint history. This Skill automates velocity calculation by processing your sprint_history structured-text to reveal per-sprint team performance metrics.

What is the best way to forecast agile sprint completion using current progress?

Sprint forecasting uses your current sprint progress alongside historical velocity trends. By providing current_sprint structured-text with progress data, this Skill generates predictability metrics and forecasts for your ongoing sprint.

How do I generate a velocity report for sprint planning and retrospectives?

To generate a velocity report for sprint planning, supply your sprint history containing sprint names, committed story points, completed story points, and sprint dates. The Skill outputs a structured velocity report with trend insights.

Can I use this velocity calculator without including completed task counts in my sprint history?

Yes, you can compute velocity without completed task counts. The Skill requires sprint name, committed story points, completed story points, and sprint dates in the sprint_history structured-text, while the completed task count remains optional.

Does this agile forecasting tool require any specific dependencies or external libraries?

No dependencies are required to run this velocity analysis tool. It operates independently to process your structured sprint data and output a velocity report without needing external libraries or components.