oaor75/acceptance-orchestrator
skills/acceptance-orchestrator/SKILL.md
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.
devops
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add oaor75/skillsAntigravity acceptance-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 6:59 PM6.2s1 file scanned
SKILL.md
- name:
- acceptance-orchestrator
- 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.
- risk:
- safe
- source:
- community
- date_added:
- 2026-03-12
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.
Related Skills
oaor75/azure-servicebus-py
development
VerifiedTrustedCommunity
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
SKILL.mdUpdated Apr 24, 2026
oaor75/azure-servicebus-dotnet
development
VerifiedTrustedCommunity
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions.
SKILL.mdUpdated Apr 24, 2026
oaor75/azure-security-keyvault-secrets-java
development
VerifiedTrustedCommunity
Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.
SKILL.mdUpdated Apr 24, 2026
oaor75/azure-security-keyvault-keys-java
development
VerifiedTrustedCommunity
Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.
SKILL.mdUpdated Apr 24, 2026