Acceptance Orchestrator Agent Skill

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.

903 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

223

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/lingxling/awesome-skills-cn --skill acceptance-orchestrator

The instruction itself

11 sections, as written by the author

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

Intake
Read issue and extract task goal + DoD.

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.

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

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 together.

Deploy and runtime verification
If DoD depends on runtime behavior, deploy only to dev by default.
Verify with real logs/API/Lambda behavior, not assumptions.

Completion gate
Before any claim of completion, require verification-before-completion.
No success claim without fresh evidence.

Stop Conditions

Move to accepted only when every acceptance criterion has matching evidence.

Move to escalated when any of these happen:

DoD still fails after 2 full rounds
missing secrets/permissions/external dependency blocks progress
task needs production action or destructive operation approval
review instructions conflict and cannot both be satisfied

Human Gates

Always stop for human confirmation on:

prod/stage deploys beyond agreed scope
destructive git/data operations
billing or security posture changes
missing user-provided acceptance criteria

Output Contract

When reporting status, always include:

Status: intake / executing / accepted / escalated
Acceptance Criteria: pass/fail checklist
Evidence: commands, logs, API results, or runtime proof
Open Risks: anything still uncertain
Need Human Input: smallest next decision, if blocked

Do not report "done" unless status is accepted.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Other skills for the same job

different authors, same section of the catalogue

Azure Kubernetes Automatic Readiness

by microsoft

vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take lingxling/acceptance-orchestrator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.