kanban-flow-metrics

Measure Kanban cycle time, lead time, throughput, and WIP to build Cumulative Flow Diagrams and percentile-based delivery forecasts.

Updated May 13, 2026
One-click install
npx skills add https://github.com/jcg-admin/kaupamex-api --skill kanban-flow-metrics-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-flow-metrics
Source: https://github.com/jcg-admin/kaupamex-api/tree/main/.claude/skills/kanban-flow-metrics
Command: npx skills add https://github.com/jcg-admin/kaupamex-api --skill kanban-flow-metrics-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running Kanban boards often cannot answer "when will it be done?" with evidence, relying on gut feeling or misleading averages instead of real flow data. This Skill turns timestamped board transitions into objective flow metrics, bottleneck detection, and a probabilistic Service Level Expectation that stakeholders can trust. ## Core Features & Use Cases - Four Flow Metrics: Computes cycle time, lead time, throughput, and WIP from per-column transition timestamps, and validates them against Little's Law (Lead Time ≈ WIP / Throughput). - Cumulative Flow Diagram Analysis: Builds and interprets the CFD to locate bottlenecks — the widening band marks the state where work accumulates faster than it is released. - Percentile-Based Forecasting: Reports p50/p85/p95 distributions instead of averages and formulates a verifiable SLE such as "85% of standard requests complete in 12 days or less." - Use Case: A product team with six weeks of board history uses this Skill to discover that the Review column is the bottleneck, verify Little's Law consistency, and commit to a p85 delivery expectation with stakeholders. ## Quick Start Ask the assistant to measure the Kanban flow metrics from your board's column transition timestamps and produce the CFD, percentile table, and a Service Level Expectation.

Frequently Asked Questions about kanban-flow-metrics

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

FAQPage Schema
How do I measure cycle time and lead time on a Kanban board?▼

Record a timestamp each time an item transitions between board columns, then compute cycle time from In Progress to Done and lead time from the commitment point to Done. Report the results as percentiles (p50, p85, p95), not averages, because the distribution has a long tail.

What is a Cumulative Flow Diagram and how do I read it?▼

A Cumulative Flow Diagram stacks the cumulative count of items in each board state over time, with one band per column. A widening band signals a bottleneck, vertical distance between curves approximates WIP, and horizontal distance approximates lead time.

Why should I use percentiles instead of averages for flow metrics?▼

Cycle time distributions are asymmetric with a long tail, so the average is contaminated by outliers and produces commitments that are systematically missed. Percentiles like p85 give a realistic, verifiable Service Level Expectation grounded in the actual distribution.

How does Little's Law apply to Kanban systems?▼

Little's Law states Lead Time ≈ WIP / Throughput, linking the three core flow metrics. Reducing WIP at constant throughput reduces lead time, which is the mathematical justification for WIP limits; the Skill verifies measured lead time against this relation.

When should I not use Kanban flow metrics for forecasting?▼

Avoid forecasting without per-column timestamps, with fewer than about two weeks of data, or after structural changes like a new team or work type, since historical percentiles no longer represent the system. Flow metrics also measure the system, not individual productivity.