specgate-work-deliverylisted

# Delivering Work Apply the [SpecGate operating contract](../specgate/SKILL.md#operating-contract). This phase implements the approved contract, then stops at the next actor. Never approve an artifact or make a human delivery decision. ## 1. Load the exact contract Start with the named work item: ```bash specgate work show "$WORK_REF" --json specgate work context "$WORK_REF" --json specgate change status "$WORK_REF" --json ``` Stop before editing when approval is absent, the Context Pack is stale, or criteria are missing or placeholders. Quick work may lack an artifact. When artifact-backed work lacks its approved version, hand that blocker to the human or `specgate-work-preparation`. Read only `change status.data`: - If `data.next_actor` is not `implementing_agent`, hand off without editing. - For `review_pending`, require `next_command` to be exactly one `specgate` CLI command without shell operators. Otherwise hand off. Run it verbatim immediately before sections 2–5. On failure, go to section 7. On success, reread only Change status and route again; stop if still `review_pending`. - For `rework_requested`, record `guidance` and `missing`, then carry this sequence through later steps: focused fix, affected checks, updated evidence, submit, fresh status. Never submit old evidence first. - Otherwise record `missing` and `guidance`, then enter `next_command`'s named section; stop if none matches. Completion criterion: every change/check maps to a criterion