Use when verified implementation work must be merged, handed off through a PR, preserved for later, or explicitly discarded with a recorded outcome instead of an ambiguous "done".
Turn verified work into an explicit integration decision: land it, open a PR, keep it for later, or discard it deliberately.
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.
verification-before-completion. If the evidence is stale, stop and re-run verification before making any completion claim.task-execution.Do not present completion options until you have current evidence that the work is actually passing. If merge-base drift, dependency updates, or additional commits changed the verified surface, re-run the necessary verification first.
Clarify:
If the user asks to discard work that affects an active hotfix, incident follow-up, or team-owned branch, escalate before deleting anything.
Present these four outcomes, with the concrete branch names or paths filled in:
Do not offer vague "what do you want to do next?" prompts. Completion should end in an explicit outcome.
release-management when the change now needs coordinated release handlingdiscard confirmation before destructive cleanupdelivery-decision-record into release-management.release-management or stops here.See gotchas for branch-policy edge cases, discard safety, and stale-verification recovery.
skills/.curatedskills/06-delivery/delivery-completion/SKILL.mdnpx skills add/update compatibility.betabeta