Delivery Completion

Turn verified work into an explicit integration decision: land it, open a PR, keep it for later, or discard it deliberately.

Context

Delivery completion is the narrow bridge between "the work is verified" and "the work has an explicit fate." It does not replace release management or deployment strategy. It answers a smaller question first: what should happen to this verified branch or change set right now?

Use this skill when implementation and review are complete, verification evidence is fresh, and the team needs an explicit completion outcome instead of an implied next step.

Inputs

• verification-record -- Fresh evidence from verification-before-completion. If the evidence is stale, stop and re-run verification before making any completion claim.
• execution-checkpoint -- Optional batch context when the work was executed through task-execution.

Process

Step 1: Confirm Fresh Verification Evidence