borghei/Claude-Skills / project-management/execution/cycle-time-analyzer
cycle-time-analyzer
VerifiedCompute lead time, cycle time, throughput, WIP, aging WIP and a cumulative flow diagram from issue status history. Use when diagnosing slow delivery, setting WIP limits or preparing a flow review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.5 KB |
| assets/flow-metrics-dashboard.md | markdown | 2.3 KB |
| assets/sample_issues.json | config | 5.8 KB |
| examples/wayfinder-flow-analysis.md | markdown | 9.7 KB |
| references/flow-metrics-guide.md | markdown | 12.2 KB |
| references/metrics-and-tool-reference.md | markdown | 7.9 KB |
| references/red-flags.md | markdown | 14.0 KB |
| scripts/flow_metrics.py | script | 26.9 KB |
assets/flow-metrics-dashboard.md
View on GitHub# Flow Metrics Dashboard: [Team Name]
**Reporting window:** [YYYY-MM-DD] to [YYYY-MM-DD]
**As-of date:** [YYYY-MM-DD]
**Owner:** [Scrum Master / Delivery Lead]
**Generated by:** `flow_metrics.py`
---
## 1. Summary
| Metric | Value | Trend (vs prior period) |
|--------|------:|:------------------------|
| Lead time (median) | [X.X] days | [↑ / ↓ / →] |
| Lead time (85th percentile) | [X.X] days | [↑ / ↓ / →] |
| Cycle time (median) | [X.X] days | [↑ / ↓ / →] |
| Cycle time (85th percentile) | [X.X] days | [↑ / ↓ / →] |
| Throughput (items/week) | [X.X] | [↑ / ↓ / →] |
| Current WIP | [X] items | [↑ / ↓ / →] |
| Aging WIP (> 85th %ile cycle time) | [X] items | [↑ / ↓ / →] |
---
## 2. Cycle Time Distribution
| Percentile | Days |
|-----------:|-----:|
| 50th | |
| 75th | |
| 85th | |
| 95th | |
**Service Level Expectation (85th):** "We commit to delivering an item within [X] days of starting, 85% of the time."
---
## 3. Aging WIP Report
Items currently in flight, sorted by age. Items exceeding the 85th-percentile cycle time are flagged "AT RISK."
| ID | Title | Type | Status | Age (days) | Status | Action |
|----|-------|------|--------|-----------:|:------:|--------|
| | | | | | [ ON TRACK / AT RISK ] | |
---
## 4. Throughput Trend (Last 8 Weeks)
| Week Ending | Items Completed |
|-------------|----------------:|
| | |
(Generated chart or sparkline)
---
## 5. Cumulative Flow Diagram
Insert Mermaid output from `flow_metrics.py --format mermaid`:
```mermaid
xychart-beta
title "Cumulative Flow"
x-axis [date1, date2, ...]
y-axis "Items" 0 --> 100
line [Backlog values]
line [Ready values]
line [In Progress values]
line [In Review values]
line [Done values]
```
---
## 6. Observations and Actions
### What the data shows
- [Observation 1, with metric reference]
- [Observation 2]
- [Observation 3]
### Recommended actions
| Action | Owner | Due |
|--------|-------|-----|
| | | |
| | | |
| | | |
---
## 7. Caveats
- Flow metrics rely on accurate, real-time status updates. Verify with the team that the board reflects actual work state.
- Cycle time is reported as a team-level metric. Do not use this data for individual performance ranking.
- Trends are more meaningful than snapshots; treat single-period changes as noise unless sustained over 3+ periods.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |