菜单
Flow metrics and analysis for Infiquetra project boards using GitHub timeline events. Provides cycle time, throughput, WIP age, per-status time breakdowns, and interpretation guidance across Operations, Asgard, and CAMPPS.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | metrics |
| description | Flow metrics and analysis for Infiquetra project boards using GitHub timeline events. Provides cycle time, throughput, WIP age, per-status time breakdowns, and interpretation guidance across Operations, Asgard, and CAMPPS. |
| when_to_use | Use this skill when the user wants to: Cycle time analysis: - "how long are issues taking", "what's our cycle time", "how fast are we delivering" - "cycle time report", "are we hitting our cycle time targets" - "how long did this capability take", "how long has issue #42 been active" Throughput analysis: - "how many capabilities did we complete last week", "weekly delivery rate" - "throughput this month", "how many items reached Done" WIP age and aging work: - "how old are our active items", "what's stale", "aging work items" Flow health: - "how's our flow", "where's the bottleneck", "which status is slowest" |
Flow metrics for Infiquetra's GitHub Projects boards. Metrics use GitHub timeline events for Status changes. Deployment state is intentionally separate from workflow Status; use deployment records and deployment fields for environment promotion questions.
$INFIQUETRA_SDLC_PATH/../infiquetra-claude-plugins/plugins/mission-control/scripts/sdlc_manager.py
If $INFIQUETRA_SDLC_PATH is unset, use ~/workspace/infiquetra/infiquetra-sdlc as the default base path.
Always run the script with python3.
| Board | Active start | Terminal statuses |
|---|---|---|
| Operations | Active | Done |
| Asgard | Active | Done |
| CAMPPS | In Progress | Done |
Legacy (read-only history): the retired Mount Olympus board used Assigned as active start
with Done/Closed/Cancelled terminals, and its timeline may include In Progress,
In Development, or Deployed. The CLI reads those values for historical continuity only;
new cards use the active boards above.
python3 sdlc_manager.py metrics cycle-time --project campps
python3 sdlc_manager.py metrics cycle-time --project asgard --days 14
python3 sdlc_manager.py metrics cycle-time --project campps --type capability
Cycle time is calculated from the first active-start status to a terminal status.
python3 sdlc_manager.py metrics throughput --project campps
python3 sdlc_manager.py metrics throughput --project asgard --weeks 8
Throughput counts items that reached a terminal workflow status during the reporting window.
python3 sdlc_manager.py metrics wip-age --project campps
python3 sdlc_manager.py metrics wip-age --project operations
WIP age shows current items in active statuses and flags entries over the configured thresholds.
python3 sdlc_manager.py metrics column-time --project campps --number 42
Use this to diagnose where one card spent time.
| Issue Type | P85 Target | Notes |
|---|---|---|
| Capability | < 5 days | Active ownership through terminal status |
| Enhancement | < 2 days | Smaller scope |
| Defect | < 1 day | Highest urgency |
| Exploration | < 3 days | Timeboxed research |
| Context Update | < 1 day | Documentation or context maintenance |
| Board | Status | Flag if age > |
|---|---|---|
| Operations / Asgard | Active | 3 days |
| Operations / Asgard | Verify | 3 days |
| CAMPPS | In Progress | 5 days |
"What's our cycle time for capabilities this month?"
-> metrics cycle-time --project campps --type capability --days 30
"How many items did Asgard complete recently?"
-> metrics throughput --project asgard --weeks 4
"How old are our active items?"
-> metrics wip-age --project campps
"How long has issue #42 been active?"
-> metrics column-time --project campps --number 42
metrics column-time on slow items to find the status consuming the most time.blocked or Needs Question state.Ready is empty or poorly shaped.references/metrics-targets.md - Complete targets, definitions, and interpretation guideskills/board/references/kanban-workflow.md - Board workflows and WIP limitsRoute proposed Team Mimir profile behavior changes to target-owned Hermes dialogue.
Build a versioned Antigravity teammate delegation envelope and route it through the guarded agy wrapper.
Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "break this down", or a handoff issue ready for planning.
Coordinate a whole outcome as a durable DAG of leaf sagas. A level-triggered reconcile loop that dispatches the ready frontier to executors, harvests completion, and pages the operator only at gates and exceptions. The coordinator routes and never runs leaf work; status is derived on read. Thin coordinator verbs only — start, graph, advance, attend, resume, discover, handoff, attach — leaf work stays the native /resume, /work, /code-review, /qa.
Execute a settled Infiquetra plan to PR-ready, then own the round-N PR continuation loop. Restores and writes the work-thread saga (the primary writer), recommends an execution backend, runs risk-gated tests, calls /code-review programmatically and reads its envelope, gates hard on P0/P1 and stale reviews, and coordinates PR-open/review-request/merge under explicit confirmation — without owning deploy. Triggers on "build it", "work this plan", "execute the plan", "resume work on
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.