velocity-tracker

Analyze historical project data to compute velocity, cycle times, and trends.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/mehdic/CDC --skill velocity-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: velocity-tracker
Source: https://github.com/mehdic/CDC/tree/main/.claude/skills/velocity-tracker
Command: npx skills add https://github.com/mehdic/CDC --skill velocity-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes historical data to compute velocity, cycle times, and trends, enabling better PM decisions and proactive planning.

Core Features & Use Cases

  • Analyzes completed vs in-progress task groups to compute velocity
  • Compares current metrics against historical baselines
  • Produces actionable recommendations and saves the report for learning

Quick Start

Run the velocity tracker after completing a task group to log velocity and generate a metrics report.

Frequently Asked Questions about velocity-tracker

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

FAQPage Schema
How do I track development velocity and predict sprint pace?

Velocity tracking analyzes completed task groups to quantify development speed and cycle times, enabling accurate sprint forecasts. Run the tracker after each task group completion to log metrics and generate actionable predictions for PM planning.

What metrics does velocity analysis provide for project planning?

Velocity analysis computes development velocity, cycle times, and trend analysis against historical baselines. It identifies 99% rule violations and produces project_metrics.json and historical_metrics.json with recommendations for team expansion and iteration adjustments.

When should I run velocity tracking during the project lifecycle?

Run velocity tracking after task group completion, before expanding the team, when tasks stall, or during iteration planning. This captures current performance against historical trends and informs cycle time assessments and scheduling decisions.

Can velocity tracking help identify bottlenecks in cycle time?

Yes. Velocity tracking compares current cycle times against historical baselines and flags deviations and 99% rule violations, surfacing stalls and bottlenecks. The summary report includes trend analysis to guide resource allocation and workflow optimization.

What data does velocity tracking require to generate reports?

Velocity tracking reads PM state from a database containing completed and in-progress task groups. It requires historical project data to compute baselines and trends, then outputs concise summaries with metrics and recommendations for decision-making.

How do velocity and cycle time metrics differ in project planning?

Velocity measures development speed (tasks completed per cycle), while cycle time tracks duration from task start to completion. Velocity tracking monitors both metrics and trends to enable predictive sprint pacing and identify performance degradation.