agentsclimarketplace

Acceptance orchestrator

Skill pinkpixel-dev/skills-collection-1/SKILLS/acceptance-orchestrator

Part 1 of a large AI and agent skills collection featuring 900+ reusable skill folders, prompt workflows, references, scripts, and assets across engineering, cloud, security, research, writing, design, and automation.

Install
npx -y skills add pinkpixel-dev/skills-collection-1 --skill acceptance-orchestrator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

2.9 KB, as published. Nobody here has run it

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-gate
  • closed-loop-delivery
  • verification-before-completion

Optional supporting skills:

  • deploy-dev
  • pr-watch
  • pr-review-autopilot
  • git-ship

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.
    • If issue is not ready or execution gate is not allowed, stop immediately.
    • Do not implement anything while issue remains draft.

  3. Execute

    • Hand off to closed-loop-delivery for implementation and local verification.

  4. Review loop

    • If PR feedback is relevant, batch polling windows as:
      • wait 3m
      • then 6m
      • then 10m
    • After the 10m round, stop waiting and process all visible comments together.

  5. Deploy and runtime verification

    • If DoD depends on runtime behavior, deploy only to dev by default.
    • Verify with real logs/API/Lambda behavior, not assumptions.

  6. Completion gate

    • Before any claim of completion, require verification-before-completion.
    • No success claim without fresh evidence.

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 2 full 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 / escalated
  • Acceptance Criteria: pass/fail checklist
  • Evidence: commands, logs, API results, or runtime proof
  • Open Risks: anything still uncertain
  • Need Human Input: smallest next decision, if blocked

Do not report "done" unless status is accepted.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.