deliver
One build tick, safe to fire on a timer: decide whether building is even the right move right now — a rejected PR to fix first, a p0 bug ahead of features, or too many PRs already waiting on review — then delegate the chosen item to the Opus 5 deliver:product-developer agent and journal the tick so a repeated timer cannot spin invisibly. Admission control and stagnation detection stay cheap in this context; /deliver:work-next-issue still owns the branch → code → runtime proof → PR procedure inside the worker. USE FOR: /loop 20m /plenipo:deliver, a single unattended build tick, resuming after a PR merged. DO NOT USE FOR: the implementation procedure itself (/deliver:work-next-issue), reviewing or merging what a tick produced (../ship/SKILL.md), or filling an empty board (../define/SKILL.md).
- License
- MIT
Pinned to revision a2ee8094fc23, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.