Antigravity Skills - Build and Discover AI Agent SkillsAntigravity Skills

Acceptance Orchestrator Skill · Devops

Acceptance Orchestrator: End-to-End Coding Automation

Automate end-to-end coding tasks with 2 max iteration rounds.

Achieve DoD proven results with minimal human intervention. Start orchestrating today!

  • State Machine
  • DoD Verification
  • Automated Workflow
  • Closed-Loop Delivery
  • Issue Gating

About This Skill

Master the art of 'DoD proven' development. This skill utilizes a robust state machine with 7 distinct states to ensure every coding task reaches verified acceptance with minimal human re-intervention.

Quick Start

  1. 1Define your issue ID and Acceptance Criteria (DoD)
  2. 2Configure the target environment (default: dev)
  3. 3Trigger the orchestrator to begin the intake state
Example Command
orchestrate --issue=123 --dod='tests pass' --env=dev

Core Capabilities

Overview

Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence.

When to Use

Ideal for tasks requiring structured handoff across implementation, review, deployment, and final verification.

Required Sub-Skills

Leverages create-issue-gate, closed-loop-delivery, and verification-before-completion for robust execution.

State Machine

Manages transitions through intake, executing, review-loop, and deploy-verify states automatically.

Usage Examples

Before

Manual checking of test results and PR status

After

Orchestrator automatically verifies tests and moves to deploy-verify

Before

Developers accidentally starting work on unready issues

After

Orchestrator gates execution until issue is 'ready'

Before

Constant manual polling of PR comments

After

Automated polling at 3m, 6m, and 10m intervals

SKILL.md

---
name: acceptance-orchestrator
description: Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
risk: safe
source: community
date_added: "2026-03-12"
---

# Acceptance Orchestrator

## Overview

Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.

Core rule: **do not optimize for "code changed"; optimize for "DoD proven".**

## When to Use
- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
- You need structured handoff across implementation, review, deployment, and final verification.
- You want explicit stop conditions and escalation instead of silent partial completion.

## Required Sub-Skills

- `create-issue-gate`
- `closed-loop-delivery`
- `verification-before-completion`

Optional supporting skills:
- `deploy-dev`
- `pr-watch`
- `pr-review-autopilot`
- `git-ship`

## Inputs

Require these inputs:
- issue id or issue body
- issue status
- acceptance criteria (DoD)
- target environment (`dev` default)

Fixed defaults:
- max iteration rounds = `2`
- PR review polling = `3m -> 6m -> 10m`

## State Machine

- `intake`
- `issue-gated`
- `executing`
- `review-loop`
- `deploy-verify`
- `accepted`
- `escalated`

## Workflow

1. **Intake**
   - Read issue and extract task goal + DoD.

2. **Issue gate**
   - Use `create-issue-gate` logic.
   - If issue is not `ready` or execution gate is not `allowed`, stop immediately.
   - Do not implement anything while issue remains `draft`.

3. **Execute**
   - Hand off to `closed-loop-delivery` for implementation and local verification.

4. **Review loop**
   - If PR feedback is relevant, batch polling windows as:
     - wait `3m`
     - then `6m`
     - then `10m`
   - After the `10m` round, stop waiting and process all visible comments toge

Frequently Asked Questions

FAQ

What tool compatibility does this skill have?
It is compatible with any Git-based workflow and supports integration with issue trackers like GitHub or GitLab.
Who is the target audience for this skill?
It is designed for DevOps engineers, AI Agent developers, and software engineers looking to automate the DoD process.
How does this differ from standard CI/CD pipelines?
Unlike standard CI/CD which focuses on 'code changed', this orchestrator optimizes for 'DoD proven' via a state machine.
Does it support different language environments?
Yes, it is language-agnostic as long as the sub-skills can execute the necessary verification commands.
What are the expected results after implementation?
Expect a significant reduction in human re-intervention and a higher rate of verified, production-ready code.

Discussion

Discussion

0 comments
U

On This Page

Trigger Phrases

Use these phrases to activate this skill in your AI coding assistant:

Orchestrate this issueVerify DoD for taskRun end-to-end implementationExecute closed-loop deliveryGate this pull request
Acceptance Orchestrator AI Agent Skill for Developers