Sprint Management - Development Velocity Tracking

Track sprint velocity and capacity using Backlog and Sprints APIs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/brentwpeterson/claude-commands --skill sprint-management-development-velocity-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sprint Management - Development Velocity Tracking
Source: https://github.com/brentwpeterson/claude-commands/tree/main/skills/sprint-management
Command: npx skills add https://github.com/brentwpeterson/claude-commands --skill sprint-management-development-velocity-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to track development velocity, plan capacity, and measure hours per point across sprints, enabling better forecasting and more predictable delivery.

Core Features & Use Cases

  • Velocity tracking: monitor completed_points vs. capacity_points to assess sprint health.
  • Capacity planning: estimate sprint capacity using working days, expected points per day, and recurring items.
  • End-to-end sprint lifecycle: plan, start, execute, close, and retrospect with API-backed data rather than static planning artifacts.
  • Use Case: A PM analyzes S2 to forecast S3 completion by leveraging S2 velocity and hours_per_point, while auto-creating recurring items for the new sprint.

Quick Start

Use this skill to query sprint health for a given sprint and pull current backlog items via the Backlog API, then summarize velocity and hours_per_point.

Frequently Asked Questions about Sprint Management - Development Velocity Tracking

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

FAQPage Schema
How do I track sprint velocity and capacity across two-week agile sprints?

You can track sprint velocity by comparing completed_points against capacity_points using the Backlog and Sprints APIs. This skill automates capacity planning and hours-per-point measurement specifically for two-week agile sprints with recurring items.

How do I forecast sprint completion based on previous sprint data?

To forecast sprint completion, analyze S2 velocity and hours_per_point metrics to estimate S3 capacity. This skill automates pulling previous sprint data via APIs to project future sprint delivery predictably.

Do I need specific API endpoints to automate capacity planning for my backlog?

Yes, you need the Backlog and Sprints API endpoints to automate capacity planning. The solution requires authenticating with the agent API key to access working days, expected points per day, and recurring items.

Can I auto-create recurring items when starting a new sprint?

Yes, you can auto-create recurring items for a new sprint by leveraging backlog and sprint APIs. The skill supports the end-to-end sprint lifecycle including planning, starting, executing, and closing with API-backed data.

What is the best way to measure hours per point for agile development teams?

The best way to measure hours per point is by automating data collection through the Sprints API during the sprint lifecycle. This skill calculates hours_per_point to enable better forecasting and more predictable delivery across sprints.