- name
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.
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/sickn33/agentic-awesome-skills/tree/HEAD/plugins/agentic-awesome-skills-claude/skills/acceptance-orchestratorFrom the publisher
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".
create-issue-gateclosed-loop-deliveryverification-before-completionDeployment 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.
Require these inputs:
dev default)Fixed defaults:
23m -> 6m -> 10mintakeissue-gatedexecutingreview-loopdeploy-verifyacceptedescalatedIntake
Issue gate
create-issue-gate logic.ready or execution gate is not allowed, stop immediately.draft.Execute
closed-loop-delivery for implementation and local verification.Review loop
3m6m10m10m round, stop waiting and process all visible comments together.Deploy and runtime verification
dev label does not grant deployment permission; inspect effects and use the project's deployment gate before changing any shared environment.Completion gate
verification-before-completion.Move to accepted only when every acceptance criterion has matching evidence.
Move to escalated when any of these happen:
2 full roundsAlways stop for human confirmation on:
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 blockedDo not report "done" unless status is accepted.
User request:
Take this issue and its acceptance criteria through implementation, validation, review, and a final evidence-backed verdict.
© 2026 Skills Rack.
---name: acceptance-orchestratordescription: Use when a coding task should be driven end-to-end from issue intake through implementation, review…---# plugins/agentic-awesome-skills-claude/skills/acceptance-orchestrator/SKILL.mdFAQ
Download plugins/agentic-awesome-skills-claude/skills/acceptance-orchestrator/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/sickn33/agentic-awesome-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.