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.

GitHub

skills

plenipo-module-sdk

Member-by-member reference for authoring a Plenipo domain module in C#: IModule, the ModuleManifest record and every field it accepts, ToolDescriptor versus ModuleTool and why a tool needs both, IModuleToolSource, TabDescriptor and its camelCase field binding, ModuleDbContext with per-entity HasQueryFilter, and Permissions.ForTool. Reach for it while writing module code — declaring a tool, adding a tab, wiring a DbContext, or chasing a tool the agent never calls. USE FOR: exact type names, required versus optional manifest fields, the two-place tool registration, tab data binding, startup-validation rules. DO NOT USE FOR: what the platform already supplies and must not be rebuilt (plenipo-platform), or running and testing the result (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.