How do I install the Delivery Monitor skill?

Run npx skillmds@latest add arozumenko/delivery-monitor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Delivery Monitor safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Delivery Monitor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Delivery Monitor free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Delivery Monitor?

arozumenko (@arozumenko) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Delivery Monitor by arozumenko — Agent Skill

Name: Delivery Monitor
Rating: 4.2 (5 reviews)
Author: arozumenko

Delivery Monitor

Delivery monitor for harness work items — the cycle-time and cadence sibling of tokenomics. Registers a plan (campaign → mission → task) with ranged, human-accepted estimates, records dispatch/merge/cancel transitions into a git-committed event ledger (.agents/telemetry/delivery/), backfills history from git, and reports cycle time, weekly throughput/velocity and estimate-vs-actual delta per level. Use when the user asks "how fast are we delivering", "register the plan / estimates", "record that TASK-023 merged", "delivery report / status", "enable delivery tracking", or "how good were our estimates". For cost per case use tokenomics; for sizing new work use automation-scoping.

arozumenko Updated Sep 22, 2026

File contents

delivery-monitor — cycle time, cadence, estimate vs actual

tokenomics answers what did it cost; this skill answers how long did it take and how did that compare with what we said. It never estimates, never defaults a missing number, and labels every proxy as a proxy.

Quick start

# 1. Register the plan (the tech-lead's plan file carries a ```json delivery-plan block)
node .claude/skills/delivery-monitor/scripts/delivery.mjs plan register --from docs/superpowers/plans/<plan>.md --id reg-1
# 2. Bind this session (lets the hook attribute dispatches) and record transitions as they happen
node .claude/skills/delivery-monitor/scripts/delivery.mjs session set --host claude --session <id> --plan sec/run-1
node .claude/skills/delivery-monitor/scripts/delivery.mjs event TASK-023 done --sha <merge-sha> --id done-023
node .claude/skills/delivery-monitor/scripts/delivery.mjs event G12 done --sha <landing-sha> --id land-g12    # mission landing
# 3. Fill in history that predates the ledger
node .claude/skills/delivery-monitor/scripts/delivery.mjs backfill --git --plan sec/run-1 --head <sha>
# 4. Optional: automatic dispatch start/end on Claude Code (+ shared telemetry submodule)
node .claude/skills/delivery-monitor/scripts/install-hooks.mjs            # --remove undoes, --doctor checks
# 5. Read
node .claude/skills/delivery-monitor/scripts/delivery.mjs status
node .claude/skills/delivery-monitor/scripts/delivery.mjs report [--json] [--html] [--from-json <f>] [--since 2026-09-01] [--level task] [--class M]
node .claude/skills/delivery-monitor/scripts/delivery.mjs report --html --out delivery.html

Contracts: references/event-model.md, references/plan-block.md, references/metrics.md, references/spike-1.md. Design (in the sdlc-skills repo): docs/superpowers/specs/2026-09-16-delivery-monitor-design.md.

---name: delivery-monitordescription: Delivery monitor for harness work items — the cycle-time and cadence sibling of tokenomics. Registers a plan (campaign → mission → task) with ranged, human-accepted estimates, records dispatch/merge/cancel transitions into a git-committed event ledger (.agents/telemetry/delivery/), backfills history from git, and reports cycle time, weekly throughput/velocity and estimate-vs-actual delta per level. Use when the user asks "how fast are we delivering", "register the plan / estimates", "record that TASK-023 merged", "delivery report / status", "enable delivery tracking", or "how good were our estimates". For cost per case use tokenomics; for sizing new work use automation-scoping.license: Apache-2.0---# delivery-monitor — cycle time, cadence, estimate vs actual`tokenomics` answers *what did it cost*; this skill answers *how long did ittake and how did that compare with what we said*. It never estimates, neverdefaults a missing number, and labels every proxy as a proxy.## Quick start```bash# 1. Register the plan (the tech-lead's plan file carries a ```json delivery-plan block)node .claude/skills/delivery-monitor/scripts/delivery.mjs plan register --from docs/superpowers/plans/<plan>.md --id reg-1# 2. Bind this session (lets the hook attribute dispatches) and record transitions as they happennode .claude/skills/delivery-monitor/scripts/delivery.mjs session set --host claude --session <id> --plan sec/run-1node .claude/skills/delivery-monitor/scripts/delivery.mjs event TASK-023 done --sha <merge-sha> --id done-023node .claude/skills/delivery-monitor/scripts/delivery.mjs event G12 done --sha <landing-sha> --id land-g12 # mission landing# 3. Fill in history that predates the ledgernode .claude/skills/delivery-monitor/scripts/delivery.mjs backfill --git --plan sec/run-1 --head <sha># 4. Optional: automatic dispatch start/end on Claude Code (+ shared telemetry submodule)node .claude/skills/delivery-monitor/scripts/install-hooks.mjs # --remove undoes, --doctor checks# 5. Readnode .claude/skills/delivery-monitor/scripts/delivery.mjs statusnode .claude/skills/delivery-monitor/scripts/delivery.mjs report [--json] [--html] [--from-json <f>] [--since 2026-09-01] [--level task] [--class M]node .claude/skills/delivery-monitor/scripts/delivery.mjs report --html --out delivery.html```Contracts: `references/event-model.md`, `references/plan-block.md`, `references/metrics.md`, `references/spike-1.md`.Design (in the sdlc-skills repo): `docs/superpowers/specs/2026-09-16-delivery-monitor-design.md`.

Frequently asked questions