azoth-deliver-full

Orchestrate Azoth's /deliver-full workflow with governance gates and kernel-level checks.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-deliver-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-deliver-full
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-deliver-full
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-deliver-full

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit Codex entrypoint that enables Azoth's /deliver-full workflow to be run with governance controls from Codex or CLI, consolidating steps into a single surface.

Core Features & Use Cases

  • Codex-native entrypoint: enables /deliver-full to be invoked from Codex CLI/IDE and the slash command surface.
  • Governance-aware orchestration: preserves command stage structure, gate rules, and evaluation criteria across the delivery pipeline.
  • Source-of-truth integration: reads the command contract at commands/deliver-full/command.yaml and the execution body at .claude/commands/deliver-full.md, then executes with user-provided arguments.
  • Use Case: orchestrate a full delivery pipeline with governance checks for kernel or breaking changes, using an orchestrator agent.

Quick Start

Invoke the full deliver workflow by typing /azoth-deliver-full followed by your arguments.

Frequently Asked Questions about azoth-deliver-full

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

FAQPage Schema
How do I automate an end-to-end delivery pipeline with governance gates?

Automating an end-to-end delivery pipeline with governance gates is done by orchestrating the delivery workflow to preserve stage structure, gate rules, and evaluation criteria across execution. It reads command contracts from YAML files and binds to an orchestrator agent with write access.

What is a governance-aware delivery workflow orchestration?

A governance-aware delivery workflow orchestration is a process that applies kernel-level checks and structured command execution to a delivery pipeline. It preserves command stage structure and evaluation rules sourced from YAML command contracts and markdown execution bodies.

Can I invoke the delivery workflow orchestration directly from the Codex CLI?

Yes, you can invoke the delivery workflow orchestration directly from the Codex CLI, IDE, or slash command surface. It provides a Codex-native entrypoint that consolidates pipeline steps into a single execution surface using user-provided arguments.

How do I execute kernel-level checks for breaking changes in a delivery pipeline?

Executing kernel-level checks for breaking changes in a delivery pipeline requires an orchestrator agent bound with write access. It evaluates gate rules and evaluation criteria defined within the command contract before proceeding through pipeline stages.

Do I need specific command contract files to orchestrate the delivery workflow?

Yes, you need specific command contract files to orchestrate the delivery workflow. The orchestration reads the command contract from commands/deliver-full/command.yaml and the execution body from .claude/commands/deliver-full.md to preserve gate rules and stage structure.