Skill · when you ask for the loop

Delivery Lead

What a team adds to a plan is the loop: someone takes the next ticket, makes sure it is really finished, moves the board, and picks up the one after. This is that loop for one developer — and it never calls a ticket done that was not proven and merged.

Soumya Rauth · Creator & maintainer

npx skills add soumyaRauth/skills-hub --skill delivery-lead

The problem

plan → tickets → … who picks the next one, and who says it is done?

Working alone, the gap between tickets is where projects stall. And without someone whose job is to check, “done” slides into “the code was written”: a PR opened, tests assumed, the board moved on a feeling.

When it activates

Only when you ask for the loop. A single request stays a single request, however large — and when it does run, one ⚡ line says so. How the skills work together →

Engages	“Work through the backlog”, “take the next ticket”, “keep going until the milestone is done”, “build the whole thing”, or by name. Also to resume an unfinished run.
Stays quiet	One ordinary request, even a large one; a request naming one skill; /skills-pipeline; planning or re-ordering tickets.
Depth	Sequences the whole run. Owns one judgment only: whether a ticket met the definition of done. Never states another skill’s verdict.
Works with	ProofBuild on every ticket, Production Guard when a milestone completes, and every other discipline when a ticket earns it

What it does

next ready ticket → branch t/<id>-<slug>
   → build ProofBuild always · the others when earned
   → VERIFIED? review · PR · merge · done
   → milestone complete? Production Guard · staging · production if allowed

You:    Work through the backlog.

Agent:  [1/5] T-002 Class list page  — done · VERIFIED · PR #12 merged
        [2/5] T-003 Book a class     — done · VERIFIED · PR #13 merged
        [3/5] T-004 Cancel a booking — blocked · REVIEW REQUIRED · refund rule undecided

        STOPPED  nothing ready · 1 decision
        1. T-004 — a member cancels <24h before class: refund?
           [full refund]  [no refund]  [class credit]

You set what it may do

Merging to the default branch, deploying production, and anything irreversible happen only when .delivery/config.yml says auto for that action, or you said yes in the session. A missing setting means ask. It never force-pushes, rewrites history, or mixes two tickets on one branch, and a run stops after five tickets unless you raise the budget.

It picks up where it stopped

Every ticket writes a checkpoint to a run ledger in .delivery/runs/. A new session reads it and the tracker, and continues — keeping a crashed session’s work, but proving it again before anything is called done.

Where it fits

delivery-planner owns the plan, the tickets and the tracker; this runs the loop over them. ProofBuild owns VERIFIED, Production Guard owns the ship decision, and release-engineer performs the deploy. The lead only refuses to call anything done without them.