From sdlc-manager
Flow metrics and analysis for the Infiquetra Mount Olympus Kanban board using timeline events. Provides cycle time percentiles, throughput trends, WIP age distribution, per-column time breakdowns, and flow efficiency — with targets by issue type and interpretation guidance.
npx claudepluginhub infiquetra/infiquetra-claude-plugins --plugin sdlc-managerThis skill uses the workspace's default tool permissions.
Flow metrics and analysis for the Infiquetra Mount Olympus Kanban board using GitHub timeline
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Flow metrics and analysis for the Infiquetra Mount Olympus Kanban board using GitHub timeline events. Measures cycle time, throughput, WIP age, and flow efficiency — with targets by issue type.
$INFIQUETRA_SDLC_PATH/../infiquetra-claude-plugins/plugins/sdlc-manager/scripts/sdlc_manager.py
If
$INFIQUETRA_SDLC_PATHis unset, use~/workspace/infiquetra/infiquetra-sdlcas the default base path.
IMPORTANT: Always use python3 (not python) to run the script.
The script queries timelineItems on GitHub issues to find ProjectV2ItemFieldValueEvent
entries showing status column changes. From these events it calculates:
# Cycle time for all issue types over last 30 days
python3 sdlc_manager.py metrics cycle-time --project mount-olympus
# Filter by days window
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --days 14
# Filter to specific issue type
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --type capability
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --type enhancement
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --type defect
Cycle Time Report — mount-olympus (last 30 days)
P50 P85 P95 Target Status
capability 3.2d 4.8d 7.1d < 5d ✓ On target
enhancement 1.1d 1.8d 3.2d < 2d ✓ On target
defect 0.4d 0.9d 1.5d < 1d ✓ On target
exploration 1.5d 2.6d 3.0d < 3d ✓ On target
Items measured: 18 (9 capability, 5 enhancement, 3 defect, 1 exploration)
Slowest item: #38 capability "User onboarding service" — 7.1 days
Bottleneck: E2E Testing (2.3 days)
# Throughput over last 4 weeks (default)
python3 sdlc_manager.py metrics throughput --project mount-olympus
# Specify weeks window
python3 sdlc_manager.py metrics throughput --project mount-olympus --weeks 8
# Filter by issue type
python3 sdlc_manager.py metrics throughput --project mount-olympus --type capability
# Current WIP age distribution (all in-progress items)
python3 sdlc_manager.py metrics wip-age --project mount-olympus
Output shows each in-progress item, which column it is in, and how long it has been there. Items exceeding age thresholds are flagged.
# How long a specific issue spent in each column
python3 sdlc_manager.py metrics column-time --project mount-olympus --number 42
Useful for diagnosing where an individual item got stuck.
| Issue Type | P85 Target | Notes |
|---|---|---|
| Capability | < 5 days | End-to-end: In Development -> Deployed |
| Enhancement | < 2 days | Smaller scope |
| Defect (general) | < 1 day | Highest urgency |
| Exploration | < 3 days | Timeboxed research |
| Context Update | < 1 day | Documentation |
| Priority | SLA | Description |
|---|---|---|
| Critical | 4 hours | System down, data loss, security breach |
| High | 1 day | Major functionality broken |
| Medium | 3 days | Minor functionality broken |
| Low | When capacity | Cosmetic or rare edge case |
| Issue Type | Target | Direction |
|---|---|---|
| Capabilities | 2-4 | Higher is better |
| Enhancements | 5-10 | Higher is better |
| Defects | < 2 | Lower is better |
| Column | Age Threshold |
|---|---|
| Ready | > 2 days |
| In Development | > 5 days |
| E2E Testing | > 1 day |
| Deployment Ready | > 2 days |
Target: > 50%
Formula: (time in In Development + time in E2E Testing) / total cycle time
Active columns are In Development and E2E Testing. Waiting columns are Ready and Deployment Ready. High wait time in Deployment Ready typically indicates deployment window constraints.
"What's our cycle time for capabilities this month?"
-> metrics cycle-time --project mount-olympus --type capability --days 30
"How many capabilities did we ship last week?"
-> metrics throughput --project mount-olympus --weeks 1 --type capability
"How old are our in-progress items?"
-> metrics wip-age --project mount-olympus
"How long has issue #42 been in development?"
-> metrics column-time --project mount-olympus --number 42
"Are we meeting our targets?"
-> Run metrics cycle-time and metrics throughput, compare to targets above
"Are any defects violating SLA?"
-> metrics wip-age --project mount-olympus — look for defects flagged as aging
"Compare this month to last month"
-> metrics cycle-time --project mount-olympus --days 30 vs. --days 60 (compare first/second half)
# Run for mount-olympus board
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --days 7
python3 sdlc_manager.py metrics throughput --project mount-olympus --weeks 4
python3 sdlc_manager.py metrics wip-age --project mount-olympus
Compare each metric to the targets table. Share summary in #mount-olympus Discord channel.
# Get all in-progress items (includes defects with their age)
python3 sdlc_manager.py metrics wip-age --project mount-olympus
# For any defect flagged as aging, check full timeline
python3 sdlc_manager.py metrics column-time --project mount-olympus --number <N>
Cross-reference priority label (critical/high-priority/medium-priority) against SLA targets above.
# 1. Check which column has the most aging items
python3 sdlc_manager.py metrics wip-age --project mount-olympus
# 2. Check cycle time breakdown to see which column adds the most time
python3 sdlc_manager.py metrics cycle-time --project mount-olympus --days 30
# 3. Drill into specific slow items
python3 sdlc_manager.py metrics column-time --project mount-olympus --number <N>
references/metrics-targets.md — Complete targets, definitions, and interpretation guideskills/sdlc-board/references/kanban-workflow.md — Column definitions and WIP limits