agile-metrics
Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.
Best use case
agile-metrics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.
Teams using agile-metrics should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agile-metrics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agile-metrics Compares
| Feature / Agent | agile-metrics | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Master agile metrics with velocity, burn-down charts, cycle time, and team health indicators for data-driven improvement.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Agile Metrics Track and analyze agile metrics to measure team performance, predict delivery, and drive continuous improvement. ## When to Use This Skill - Measuring team performance - Forecasting delivery - Identifying bottlenecks - Sprint planning - Stakeholder reporting - Process improvement - Team health assessment - Trend analysis ## Core Concepts ### 1. Velocity **Definition**: Story points completed per sprint ```markdown ## Velocity Trend Sprint 1: 35 points Sprint 2: 42 points Sprint 3: 38 points Sprint 4: 45 points Sprint 5: 43 points Sprint 6: 47 points **Average Velocity**: 42 points **Trend**: Increasing (+2 points per sprint) **Forecast**: Sprint 7 likely 45-50 points ``` ### 2. Burn-Down Chart ``` Story Points 50 |● 40 | ● 30 | ● 20 | ● 10 | ● 0 |__________● Day 1 3 5 7 9 10 ● Actual ─ Ideal ``` ### 3. Team Health Metrics ```markdown | Metric | Target | Actual | Trend | |--------|--------|--------|-------| | Velocity | 40-45 | 43 | ↗️ | | Sprint Completion | >90% | 95% | ↗️ | | Team Happiness | >7/10 | 8/10 | → | | Code Quality (bugs) | <5 | 3 | ↗️ | | Cycle Time | <5 days | 4 days | ↗️ | ``` ## Best Practices 1. **Focus on trends** - Not individual sprint 2. **Use for planning** - Not performance reviews 3. **Team-owned metrics** - Not imposed 4. **Multiple indicators** - Holistic view 5. **Continuous tracking** - Regular updates 6. **Visualize data** - Charts and dashboards 7. **Act on insights** - Drive improvements 8. **Context matters** - Consider factors ## Resources - **Agile Metrics**: Scrum.org guide - **Jira/Azure DevOps**: Metric dashboards
Related Skills
agile-product-owner
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
application-metrics
Guide for instrumenting applications with metrics. Use when adding observability, monitoring, metrics, counters, gauges, or instrumentation to code. Covers API endpoints, databases, queues, caching, and locks.
agile-retrospective
When facilitating sprint retrospectives or team improvement sessions.
agile-ceremonies
Agile ceremonies and sprint management specialist. Use when running standups, retrospectives, sprint planning, or tracking sprint progress.
sentry-setup-metrics
Setup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, TypeScript, Python, React, Next.js, and Node.js.
agile-workflow
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective.
Agile Scrum
Comprehensive guide to Agile Scrum methodology including roles, ceremonies, artifacts, sprint planning, and best practices for iterative software development
agile-methodology
Apply agile development practices. Use when planning sprints, running ceremonies, or improving team processes. Covers Scrum, Kanban, and agile principles.
agile-coordinator
Orchestrate multiple worker agents to implement groomed tasks. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous.
aggregating-gauge-metrics
Aggregate pre-computed metrics (gauge, counter, delta types) using OPAL. Use when analyzing request counts, error rates, resource utilization, or any numeric metrics over time. Covers align + m() + aggregate pattern, summary vs time-series output, and common aggregation functions. For percentile metrics (tdigest), see analyzing-tdigest-metrics skill.
x-metrics-tracker
Track X account metrics (followers, posts, following) with daily snapshots via browser automation. Use when you need to monitor X profile growth, capture daily analytics, or view historical follower/post trends.