Harness Kit

skill

deliver

Inner-loop composer for one backlog item to merge-ready code. Composes /shape, /implement, /code-review, /ci, /refactor, and /qa; stops before push, merge, or deploy. Emits receipt.json plus operator brief + /reflect. Use for "deliver this", "make it merge-ready", shaped-ticket builds, and `--polish-only <branch|PR>` for existing branch/PR cleanup. Trigger: /deliver.

/deliver

Source: skills/deliver/SKILL.md

What it does

Inner-loop composer for one backlog item to merge-ready code. Composes /shape, /implement, /code-review, /ci, /refactor, and /qa; stops before push, merge, or deploy. Emits receipt.json plus operator brief + /reflect. Use for "deliver this", "make it merge-ready", shaped-ticket builds, and `--polish-only <branch|PR>` for existing branch/PR cleanup. Trigger: /deliver.

Workflow role

Orchestrate primitive in the Harness Kit operating loop.

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Inner-loop composer. One backlog item → merge-ready code. **Delivered ≠
shipped.** The outer loop (`/flywheel`) consumes the receipt and
decides whether to deploy. Humans merge.

## Invariants

- Compose atomic phase skills. Never inline phase logic.
- Fail loud. Never swallow a phase failure into a "best effort" pass.
- Clean closeout is part of merge-readiness. Before writing `merge_ready` or
  presenting delivery as complete, shared Closeout applies; every visible path
  must be classified into a follow-up commit, deletion, move-out, durable
  ignore, or explicit handoff. See `harnesses/shared/AGENTS.md` (Closeout).

## Delegation Floor

Delegation floor applies: probe the roster first; dispatch two or more
providers for substantive work; direct solo only for mechanical, emergency,
user-forbidden, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).

Local lane guidance: Phase skills dispatch their own lanes; /deliver verifies roster-member receipts or explicit exceptions before calling work merge-ready.

## Completion Evidence

Completion evidence core applies: use `harnesses/shared/AGENTS.md`
(Completion Evidence) as the universal evidence shape, then fill the local
fields in the merge-ready block below.

## Work Ledger

When `.harness-kit/work/ledger.jsonl` is available, `/deliver` calls
`scripts/work-ledger.py append` at transition points: `phase_started` for
`shape`, `implement`, `review`, `ci`, `qa`, and `reflect`; `blocker_added`
when a phase fails; `phase_completed` with `status=completed` when the branch
is merge-ready. On `--resume`, consume the latest record for the same
backlog/branch/work id to report current phase, blockers, evidence refs,
spawned agents, trace refs, and next action without parsing chat history.

## Agent Readiness
...

What to verify