delivery-prepare

Generate and validate delivery/1 contracts with local evidence for Git workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hack-ink/codexlab --skill delivery-prepare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-prepare
Source: https://github.com/hack-ink/codexlab/tree/main/.codex/skills/delivery-prepare
Command: npx skills add https://github.com/hack-ink/codexlab --skill delivery-prepare

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the generation of a formal delivery contract and collects local delivery evidence during the prepare stage, ensuring governance over code changes and readiness for delivery-closeout.

Core Features & Use Cases

  • Produces a Delivery/1 contract ready for delivery-closeout validation.
  • Generates local delivery evidence anchored to the commit, enabling traceability.
  • Enforces required fields (type, scope, summary, intent, impact) and refs (linear authority/related, GitHub mirrors) with validation.

Quick Start

Run the delivery-prepare workflow to generate a delivery/1 contract and local evidence before committing.

Frequently Asked Questions about delivery-prepare

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

FAQPage Schema
How do I generate a delivery contract for a Git commit before integration?

To generate a delivery contract for a Git commit, run the delivery-prepare workflow to produce a single-line JSON contract and collect local evidence. It enforces required fields like type, scope, summary, intent, and impact for validation.

What is a delivery contract in a Git workflow and when do I need one?

A delivery contract is a formal JSON document enforcing governance over code changes before integration. You need it during the prepare stage of a Git workflow when a commit requires structured validation of authority refs, risk level, and breaking flags.

How do I validate authority refs and GitHub mirrors for a delivery contract?

You validate authority refs and GitHub mirrors by running the delivery-prepare validation process. It checks the proper refs structure, enforces the contract schema, and ensures linear authority and related refs are correctly formatted before integration.

Can I use this delivery contract generation for automated Git push workflows?

Yes, you can use delivery-prepare for automated Git push workflows requiring a formal delivery contract. It generates the necessary contract and local delivery evidence anchored to the commit, ensuring traceability and readiness for downstream delivery-closeout.

What fields are required in a delivery/1 contract schema?

The delivery/1 contract schema requires fields including type, scope, summary, intent, and impact. It also enforces a boolean breaking flag, risk level, and proper refs structure encompassing linear authority, related refs, and optional GitHub mirrors.

Why does my delivery contract validation fail on missing local evidence?

Delivery contract validation fails on missing local evidence because the generation process requires evidence anchored to the commit for traceability. Running the delivery-prepare workflow ensures both the contract and local evidence are properly produced and validated.