Skip to content

abrahamferga/deliver

v0.4.0MIT

The build and verification loops: take one Ready issue at a time from the board to a merged PR, and prove each change at runtime rather than at compile time. Ships the Plenipo module and connector SDK references Claude reaches for while coding, the runbook installer that gives a product its execution + verification surface, and the run -> exercise -> observe -> diagnose -> fix -> lock-in loop. The default coding-loop plugin.

work-next-issue

Take exactly one Ready issue off the GitHub project board and drive it to an open pull request: select the top item by build order, move the card to In Progress, cut a branch, implement it against the platform contract, climb the test ladder, prove the change at runtime, then open a PR that closes the issue and leave the card In Review. Never more than one issue in flight — a second run resumes the one already started instead of opening another. USE FOR: implementing the next feature off the board, resuming an interrupted issue, running the branch → code → runtime proof → PR cycle. DO NOT USE FOR: creating or ordering the backlog (/define:sync-backlog), deciding architecture or moving cards Backlog → Ready (the shape loop), or debugging behaviour that has no issue behind it (../verify-runtime).

License
MIT
Read SKILL.md at the source

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.