delivery-completion

Generate a delivery-decision-record after validating verification evidence.

1|Updated Mar 17, 2026

Search Tags:#verification #decision #merge #governance #handoff #pr #delivery

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill delivery-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: delivery-completion
Source: https://github.com/yknothing/prodcraft/tree/main/skills/06-delivery/delivery-completion
Command: npx skills add https://github.com/yknothing/prodcraft --skill delivery-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use this skill 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".

Core Features & Use Cases

Enforces explicit delivery outcomes: merge/land, push PR, hold for later, or discard with a tracked decision.
Provides a controlled handoff to release-management or delivery-related workflows.
Ensures verification evidence freshness before completing and documents final state.

Quick Start

Review the current verification record and execution checkpoint to produce a delivery-decision-record capturing the chosen outcome.

Frequently Asked Questions about delivery-completion

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

FAQPage Schema

How do I turn verified implementation work into an explicit merge or discard decision?▼

A delivery decision automates turning verified work into an explicit merge, hold, or discard outcome. It validates fresh verification evidence and determines the integration target, replacing ambiguous completion statuses with a tracked governance handoff.

What is a delivery-decision-record and when do I need one for a PR?▼

A delivery-decision-record captures the chosen outcome of verified work, such as merging, pushing a PR, holding, or discarding. You need one when verification is complete and an explicit integration decision across development branches is required.

How do I document a decision to hold or discard a development branch?▼

You document a decision to hold or discard a branch by generating a delivery-decision-record. This enforces explicit delivery outcomes and ensures the chosen state is preserved for later or explicitly discarded with a tracked, recorded outcome.

Does delivery completion require verification evidence before merging?▼

Yes, delivery completion requires verification evidence freshness before merging. It ensures validation of fresh execution checkpoints to produce an accurate delivery-decision-record for the chosen integration target.

What is the best way to hand off verified work to release management?▼

The best way to hand off verified work to release management is through a controlled delivery-decision-record. This provides an explicit governance handoff, documenting the final state and chosen outcome for downstream delivery-related workflows.

Why should I use an explicit delivery decision instead of just marking a task as done?▼

You should use an explicit delivery decision instead of marking a task as done to avoid ambiguous completion. It enforces a tracked outcome for merging, holding, or discarding, ensuring verification evidence validates the final integration state.