sum-delivery

Verify worker results, run independent review, and publish reviewable PRs without merging.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill sum-delivery-douglasjarquin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sum-delivery
Source: https://github.com/douglasjarquin/sum/tree/main/skills/sum-delivery
Command: npx skills add https://github.com/douglasjarquin/sum --skill sum-delivery-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multi-agent coding work creates a trust gap: a worker agent's report is only a claim, and accepting it blindly risks shipping unverified or unreviewed code. This Skill gives the coordinator a disciplined delivery process that independently verifies worker output, arranges fresh-context review, and publishes a reviewable PR while leaving the merge decision to the user. ## Core Features & Use Cases - Independent Verification: Re-run the project's declared verification contract against the exact candidate SHA in a detached checkout via sumctl verify --execute, keeping worker claims, reviewer findings, and coordinator runs as separate evidence records. - Nine-Gate Delivery Pipeline: Drive Intent, Rebase, Review, Test, Document, Lint, Push, PR, and CI gates with sumctl pipeline run, where every row is derived from saved task records rather than set by hand. - Safe PR Publication: Push fast-forward only, adopt existing PRs instead of duplicating them, publish before/after evidence and pipeline tables into marked PR blocks, and reconcile PR identity through gh after every push. - Use Case: A worker agent reports a bug fix complete. You run the delivery flow to re-verify the candidate yourself, launch a separate reviewer, open the PR with evidence attached, and present the URL to the user, who alone decides whether to merge. ## Quick Start Ask the coordinator to verify the worker's latest candidate for a task, arrange an independent review, and open a pull request without merging it.

Frequently Asked Questions about sum-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a worker agent's code changes before merging?

Run sumctl verify TASK_ID --candidate SHA --execute to re-run the project's verification contract in a detached checkout of the exact candidate. The worker's own run is treated as a claim you check against, never as your result.

How does the sum delivery pipeline publish a pull request?

Run sumctl pipeline run TASK_ID, which drives rebase, test, lint, document, push, and PR gates in order and stops at the first failure. It adopts an existing PR for the branch instead of duplicating one and never merges.

Can the coordinator merge a pull request automatically?

No. Only the user merges. The pipeline opens and reconciles the PR, publishes evidence and gate tables, and presents the URL, but the merge decision always remains with the user.

What happens when coordinator verification fails on a candidate?

The task is parked with the failed run recorded as evidence, and closure.missing names the failure. A repair candidate requires the worker to run again, the coordinator to re-verify, and a review of the intervening diff.

Does sum-delivery support repositories without a standardized verification contract?

Yes. A not-yet-standardized project keeps its existing commands and records prose results with sumctl verify --result and --text. Both forms use the same public sumctl verify command.

Why is a second verification run required if the worker already ran tests?

The worker's run is a claim bound to its own context, so the coordinator re-runs verification independently against the exact candidate SHA. This separation keeps worker claims, reviewer findings, and coordinator evidence as distinct records.