delivery-loop

Automate end-to-end feature delivery with multi-agent orchestration and governance checks.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/fall-out-bug/sdp_lab --skill delivery-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-loop
Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/delivery-loop
Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill delivery-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manual coordination across multiple phases of software delivery leads to drift, wasted effort, and slow feedback. The delivery-loop skill automates bootstrap, preflight, build/review/fix cycles, PR creation, codex review, and closeout, reducing toil and ensuring governance.

Core Features & Use Cases

  • Declarative phase model (bootstrap, preflight, build, pr, codex, closeout) with per-feature overrides via .sdp/delivery.yaml.
  • Parallel subagents per workstream (with safe concurrency, backoff, and cycle control) to accelerate delivery while maintaining quality.
  • Checkpointing, archival, and resume support for interrupted runs, plus batch closeout and artifact retention.
  • Governance, traceability, and quality gates integrated into the PR and codex review phases for auditable delivery.
  • Use cases: enterprise SDP teams needing repeatable, evidence-backed delivery cycles with controlled handoffs and rollback.

Quick Start

Invoke the @delivery-loop operator in your SDP environment to start an end-to-end feature delivery cycle for a selected Epic.

Frequently Asked Questions about delivery-loop

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

FAQPage Schema
How do I automate end-to-end feature delivery workflows with build, review, and fix cycles?

Automating end-to-end feature delivery workflows involves coordinating multi-agent sub-skills across bootstrap, preflight, build, PR creation, codex review, and closeout phases. This orchestration reduces manual toil while ensuring governance, traceability, and quality gates are integrated into the pipeline.

What is autonomous software delivery orchestration and when do I need it?

Autonomous software delivery orchestration coordinates parallel subagents across iterative build, review, and fix cycles to reduce drift and wasted effort. You need it when manual coordination across delivery phases slows feedback and lacks auditable governance for enterprise SDP teams.

How do I configure per-phase budgets and overrides for automated delivery pipelines?

You can configure per-phase budgets and override-driven customization by defining settings in a .sdp/delivery.yaml file. This declarative approach allows you to set specific parameters for bootstrap, preflight, build, PR, codex, and closeout phases.

Can I resume automated delivery loops if an interrupted run stops halfway?

Yes, automated delivery loops support checkpointing, archival, and resume capabilities for interrupted runs. This allows the pipeline to safely pause and restart without losing progress, enabling batch closeout and artifact retention.

Does parallel subagent execution work safely with concurrent feature delivery workstreams?

Yes, parallel subagent execution works safely with concurrent feature delivery workstreams by using safe concurrency, backoff, and cycle control. This accelerates delivery while maintaining quality and preventing race conditions across parallel tasks.

What are the limitations of using autonomous delivery loops for software pipelines?

Autonomous delivery loops require structured governance and checkpointing infrastructure to function correctly. If your environment lacks support for multi-agent coordination or declarative phase models, the orchestration may fail to provide controlled handoffs and rollback capabilities.