flow-metricslisted

Use this skill when the user asks for DORA / Flow Framework metrics over a Jira scope -- "what's our cycle time this quarter for PROJ", "give me throughput and WIP for the Foo team", "compare flow efficiency before/after the AI-pairing rollout via a cohort split", "rollup flow metrics across program 42". Computes cycle time, lead time, throughput, WIP, flow load, rework rate, flow efficiency, flow distribution, and defect ratio from Jira changelogs (optionally joined with Jira Align for program / portfolio scope). Read-only -- never transitions, comments, creates, updates, or deletes Jira data. Do NOT use for live-dashboard streaming, deployment-event metrics (Change Failure Rate / MTTR proper), or anything requiring a tracker that isn't Jira.
eugenelim/agent-ready-repo · ★ 7 · AI & Automation · score 81

Install: claude install-skill eugenelim/agent-ready-repo

# Skill: flow-metrics This skill is the one place to compute Flow Framework / DORA-style metrics over a Jira scope. It composes two upstream skills and emits a canonical JSON / CSV / JSONL block; it does **not** invent new tracker verbs or replicate them inline. - **`jira` skill** (sibling in this pack) — every Jira read: `check`, `whoami`, `get-issue`, `search`, `get-project`, plus a tightly- allowlisted set of `raw GET` paths for the custom-field catalog, project-status enumeration, and per-issue changelog pagination. - **`jira-align` skill** (sibling in this pack) — used **only** for `--program-id` / `--portfolio-id` scope, and **only** for the four team / program / portfolio enumeration paths. Time-in-state numbers always come from Jira's changelog. The pipeline (config validation, scope JQL, changelog walk, per-issue derivation, aggregation, cohort split, per-team rollup, notes, meta, output rendering, caching) lives in `scripts/flow_metrics/`. This SKILL.md tells the agent how to **invoke** the CLI for common flows; for design details, read the inline module docstrings. ## Cross-skill invocation — name, not path This skill names sibling skills (`jira`, `jira-align`) by their `name:` field, never by path. Install locations vary by IDE and scope, and skills can be renamed at install time. The agent's harness resolves the name to whatever location the user picked. **If you find yourself writing a hardcoded skill path, stop — look up the skill by name inste