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.

verify-runtime

Drive one change on a Plenipo product from symptom to proof: reproduce through the narrowest surface, diagnose from telemetry before source, fix one variable per turn, then lock the behaviour in with a regression test seen red before the fix and green after. Refuses to call anything done that was not observed working at runtime, and refuses to let an assertion move instead of the code. USE FOR: proving a specific fix or feature actually works, debugging a failing chat turn, endpoint, or approval gate, picking which test rung locks a fix in, catching an agent that gamed a pinned assertion. DO NOT USE FOR: standing up the verification surface in a repo that has none (../install-runbook/SKILL.md), or the product-independent run and test contract (plenipo-runbook).

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.