Acceptance Orchestrator

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.

9 stars 4 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add huytran1120/vietnam-agentic-skills --skill acceptance-orchestrator
Manual install
git clone --depth 1 https://github.com/huytran1120/vietnam-agentic-skills.git /tmp/vietnam-agentic-skills
mkdir -p ~/.claude/skills
cp -r /tmp/vietnam-agentic-skills/skills/acceptance-orchestrator ~/.claude/skills/acceptance-orchestrator

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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`

Deployment and PR monitoring are project-specific capabilities, not bundled sub-skills.
Use the repository's actual deployment and review procedures; the legacy names
`deploy-dev`, `pr-watch`, `pr-review-autopilot`, and `git-ship` are not available in AAS.

## 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.
Read the full skill on GitHub

Details

Skill name
acceptance-orchestrator
Path
skills/acceptance-orchestrator/SKILL.md
License
MIT
Repo updated
29 October 2026
Copies
Found in 3 GitHub repos

FAQ

What does the Acceptance Orchestrator skill do?

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.

How do I install the Acceptance Orchestrator skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add huytran1120/vietnam-agentic-skills --skill acceptance-orchestrator. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Acceptance Orchestrator popular?

It lives in huytran1120/vietnam-agentic-skills, which has 9 GitHub stars and 4 forks.

Related skills

Apify Audience Analysis

9

huytran1120/vietnam-agentic-skills

Understand audience demographics, preferences, behavior patterns, and engagement quality across Facebook, Instagram, YouTube, and TikTok.

Images, Video & Audio

Apify Competitor Intelligence

9

huytran1120/vietnam-agentic-skills

Analyze competitor strategies, content, pricing, ads, and market positioning across Google Maps, Booking.com, Facebook, Instagram, YouTube, and TikTok.

Marketing, Sales & Business

Apify Content Analytics

9

huytran1120/vietnam-agentic-skills

Track engagement metrics, measure campaign ROI, and analyze content performance across Instagram, Facebook, YouTube, and TikTok.

Writing & Content

Test Analyze

9

yasunori0418/skills

ISTQB/JSTQB のテスト分析(test analysis)活動を支援するスキル。テストベース(仕様・設計・コード・リスク)を分析して「何をテストすべきか」= テスト条件(test condition)を識別し、test-plan のプロダクトリスク評価があればそれを入力に優先度を付けた test-analysis.md を作る。「何をテストすべきか洗い出して」「テスト条件を整理して」「テスト観点を出して」「テスト分析して」と依頼されたときに使う。テストケースの導出(test-design)は対象外。単発のテスト作成依頼(単にユニットテストを書きたいだけ)も対象外。/test-analyze <テスト対象名> で明示的に呼び出されたときのみ使用する。

Testing & QA

QA Only

9

borkweb/skills

Test an application at its browser, API, CLI, job or webhook surface and report reproducible bugs with evidence, without fixing them. Use for 'QA this and report', 'test the app', 'find bugs but don't fix', 'verify this flow works' or when do needs a runtime check of a change.

Testing & QA

Test and Verify

5

cellrishi-code/claude-skills-atlas

Use after implementing code to systematically verify behavior, tests, regressions, and important edge cases.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.