Autonomous delivery (v3)

Organize the work, keep it moving, and keep improving how it is organized. This is the coordination skill for build mode: large new work where the process is to file issues, let independent sessions work them in parallel, then merge and deploy. There may be no metric to climb, and that's fine. When a lane does have a measurable signal, that lane runs find-the-loop. A coordinator holds your intent, splits it into lanes, and delegates each lane to a child session that owns an outcome. Children may run their own workers. The coordinator optimizes for verified outcomes per hour, not agent activity. Quality and throughput are joint goals, and you never buy speed by weakening the outcome. For a delivery mandate, the outcome is working behavior observed on the real path, not source code or an open PR.

A skill is not authorization. But existing delegation is authority within its scope, and it doesn't need to be requested again at every step.

Version 3 builds on the public autonomous-delivery skill, v2.1 (MIT). It keeps the adaptive orchestrator-worker pattern and adds the rules that weeks of real unattended runs forced into existence. Dials are set up front. Stalled children are restarted automatically. The watchdog metric is time since last merge. Wakes with nothing new stay silent. A stuck lane gets re-planned after two hours. Releases have one writer. The backlog never runs dry. Constraints that agents invent come with a source and an expiry.

Worked examples, templates and the full list of changes since v2.1 are in reference.md.

When to use

• The work spans hours or days, or must keep running while you're away.
• There are more than about three independent units of work, or you said "parallelize", "lanes", "orchestrator", "keep N going".
• You're resuming a run after a restart, sleep or outage. Re-invoking re-arms it with the stored dials.