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.
- License 许可
- MIT
- 最近更新
- 2026-04-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- acceptance-orchestrator
- risk
- safe
- source
- community
- date_added
- 2026-03-12
- 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.
03 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".
Required Sub-Skills
create-issue-gateclosed-loop-deliveryverification-before-completion
Optional supporting skills:
deploy-devpr-watchpr-review-autopilotgit-ship
Inputs
Require these inputs:
- issue id or issue body
- issue status
- acceptance criteria (DoD)
- target environment (
devdefault)
Fixed defaults:
- max iteration rounds =
2 - PR review polling =
3m -> 6m -> 10m
State Machine
intakeissue-gatedexecutingreview-loopdeploy-verifyacceptedescalated
Workflow
-
Intake
- Read issue and extract task goal + DoD.
-
Issue gate
- Use
create-issue-gatelogic. - If issue is not
readyor execution gate is notallowed, stop immediately. - Do not implement anything while issue remains
draft.
- Use
-
Execute
- Hand off to
closed-loop-deliveryfor implementation and local verification.
- Hand off to
-
Review loop
- If PR feedback is relevant, batch polling windows as:
- wait
3m - then
6m - then
10m
- wait
- After the
10mround, stop waiting and process all visible comments together.
- If PR feedback is relevant, batch polling windows as:
-
Deploy and runtime verification
- If DoD depends on runtime behavior, deploy only to
devby default. - Verify with real logs/API/Lambda behavior, not assumptions.
- If DoD depends on runtime behavior, deploy only to
-
Completion gate
- Before any claim of completion, require
verification-before-completion. - No success claim without fresh evidence.
- Before any claim of completion, require
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
2full 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 / escalatedAcceptance Criteria: pass/fail checklistEvidence: commands, logs, API results, or runtime proofOpen Risks: anything still uncertainNeed Human Input: smallest next decision, if blocked
Do not report "done" unless status is accepted.
04 同仓库更多 Skills
webapp-testing
To test local web applications, write native Python Playwright scripts.
python-packaging
Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.
canvas-design
These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.
webapp-testing
To test local web applications, write native Python Playwright scripts.
slack-gif-creator
A toolkit providing utilities and knowledge for creating animated GIFs optimized for Slack.
frontend-design
You are a frontend designer-engineer, not a layout generator.