acceptance-orchestrator

1# Acceptance Orchestrator
2 
3## Overview
4 
5Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.
6 
7Core rule: **do not optimize for "code changed"; optimize for "DoD proven".**
8 
9## When to Use
10- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
11- You need structured handoff across implementation, review, deployment, and final verification.
12- You want explicit stop conditions and escalation instead of silent partial completion.
13 
14## Required Sub-Skills
15 
16- `create-issue-gate`
17- `closed-loop-delivery`
18- `verification-before-completion`
19 
20Deployment and PR monitoring are project-specific capabilities, not bundled sub-skills.
21Use the repository's actual deployment and review procedures; the legacy names
22`deploy-dev`, `pr-watch`, `pr-review-autopilot`, and `git-ship` are not available in AAS.
23 
24## Inputs
25 
26Require these inputs:
27- issue id or issue body
28- issue status
29- acceptance criteria (DoD)
30- target environment (`dev` default)
31 
32Fixed defaults:
33- max iteration rounds = `2`
34- PR review polling = `3m -> 6m -> 10m`
35 
36## State Machine
37 
38- `intake`
39- `issue-gated`
40- `executing`
41- `review-loop`
42- `deploy-verify`
43- `accepted`
44- `escalated`
45 
46## Workflow
47 
481. **Intake**
49   - Read issue and extract task goal + DoD.
50 
512. **Issue gate**
52   - Use `create-issue-gate` logic.
53…