Skip to content

Acceptance Orchestrator

Drives a coding task from issue to verified acceptance, stopping for evidence or human approval

Stars
49,023
Licence
MIT
Files
1 file

What it does

This skill makes an AI agent run a software task like a disciplined project workflow: it checks that a GitHub-style issue is ready, implements the change, watches for review comments, verifies runtime behaviour, and only reports success when every acceptance criterion has evidence. If it gets stuck, after two full retry rounds or when permissions or secrets are missing, it stops and escalates to a human rather than quietly finishing partial work. It is mostly a process and status-reporting framework; it depends on other sub-skills and on the project's own deployment and review procedures, which it does not supply.

Great for

  • Development teams who already write issues with clear acceptance criteria and want an agent to carry them through review and verification
  • Tech leads who want explicit stop conditions and evidence-based status reports from an agent
  • People experimenting with multi-step agent workflows built on the Agentic Awesome Skills collection

Skip it if

  • Quick one-off scripts or small edits with no issue or acceptance criteria, since the workflow adds overhead and expects structured inputs
  • Production or shared-environment deployments without a human approving each step, because the skill itself defers those decisions to people and mistakes in configuration could still cause harm
  • Teams without a deployment gate, CI, or review process, since the skill tells the agent to use the project's actual procedures and cannot substitute for them

Try asking

  • “Take issue #123 and its acceptance criteria through implementation, local validation, review, and a final evidence-backed verdict”
  • “Check whether this issue is ready for execution and stop if its acceptance criteria are missing”
  • “Implement the change, wait for PR review comments, then verify the dev environment logs match the DoD”
Step-by-step guide: how to use Acceptance OrchestratorInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    acceptance-orchestrator.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip acceptance-orchestrator.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip acceptance-orchestrator.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Write the issue with explicit, testable acceptance criteria and a stated target environment before invoking the skill, since missing criteria cause it to stop
  • Install and check the three required sub-skills first; the orchestrator relies on them and does not bundle them
  • Review the Output Contract sections in each status report and confirm the evidence shown is real logs or command output

What's inside

  • SKILL.md

Redistributed unmodified from sickn33/agentic-awesome-skills under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.