agentsclimarketplace

Deliver

Skill mblauberg/provenant/skills/deliver

Portable equal-primary Claude and Codex agent harness for a governed agentic SDLC

Install
npx -y skills add mblauberg/provenant --skill deliver

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use for taking an approved research, analysis, document, or agent-product outcome through evidence, review, and user acceptance. Not for software-only work, unsettled scope, or release; use implement, scope, or release.

SKILL.md

3.8 KB, as published. Nobody here has run it

Deliver

Run the domain-neutral lifecycle kernel. This skill coordinates existing capabilities; domain skills still own domain methods.

Entry

Require an approved intent, acceptance criteria, minimum risk tier and bounded authority. Consequential scope/design, disclosure, one-way doors and risk downgrades need explicit user approval. If intent is unsettled, use scope.

Select one base profile from config/delivery-profiles.json: software, research, analysis, document or agent-product. Add the high-stakes overlay when source authority, privacy or qualified review matters. Projects may strengthen a profile, never weaken kernel gates silently.

Lifecycle

  1. Create .agent-run/<id>/RUN.json from templates/RUN.template.json and bind intent, design and authority by digest. When the delivery belongs to a coordinated project, bind the top-level fabric_relationships to its project session, coordination run and workstream/lead IDs per the receipt contract. Use the explicit independent not_applicable form rather than inventing parents.
  2. Record each state transition. No state may jump an approval, evidence, review, acceptance or release gate.
  3. Execute through the relevant skills. Software routes execution through implement; stochastic behaviour routes through evaluate; failures use diagnose; substantial parallel work may use orchestrate.
  4. Produce profile-required deterministic evidence before judgement evidence. Every gate links to a typed artifact or receipt. At acceptance, a stochastic gate must bind and hash-verify a passing canonical evaluation-run receipt; copied scores or sampling metadata are not evidence. Retain failed or incomplete evaluation receipts as non-gating history.
  5. Review independently with lenses selected from the dependency cone. Substantial+ follows HARNESS.md: targeted lenses plus the other primary; distinct-family review is used when available, with terminal pressure made stronger and skipped optional legs recorded.
  6. Repair at most twice. Scope/design drift returns to the user gate.
  7. Validate from the project root with "${AGENTS_HOME:-$HOME/.agents}/skills/deliver/scripts/validate_delivery.py" .agent-run/<id>/RUN.json --workspace-root "$PWD" --verify-hashes (plus a digest-bound --project-policy when used). awaiting_acceptance is machine-ready, not complete.
  8. User acceptance and external release are separate. Define observation before release; close only after its evidence window passes. Feed incidents and recurrence into retrospect and the next scoped cycle.

Boundaries

Delegates may only narrow authority. One writer owns each shared source surface. Artifact manifests classify canonical, evidence, handoff, scratch or external; cleanup removes only expired, run-owned scratch with explicit authority. Filesystem receipts remain truth when Herdr or another transport is unavailable.

implement uses this same receipt with profile software; no parallel implementation receipt format exists. Live task or membership projections may link to it but never replace its canonical acceptance evidence.

For audience-ready HTML, apply the interactive-document boundary.

Adapter-absent path

Console, Herdr and GitHub are optional. Continue from canonical project artifacts and emit the skill-owned artifact kind in portable-workflow.v1.json. That filesystem artifact records workflow evidence; it never grants acceptance or release authority.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.