Regtransfers/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 Jun 23, 2026
$ install --global
skillsauthnpx skillsauth add Regtransfers/agency-agents-mcp 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: Jun 23, 2026, 2:50 AM110.4s1 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: never optimize for "code changed"; optimize for "DoD proven".
@ When to Use
- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
- You need structured handoff across implementation, review, deployment, and final verification.
- You want explicit stop conditions and escalation instead of silent partial completion.
@ 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
- Intake
- Read issue and extract task goal + DoD.
- Issue gate
- Use create-issue-gate logic.
- If issue is not ready or execution gate is not allowed, stop immediately.
- never implement anything while issue remains draft.
- Execute
- Hand off to closed-loop-delivery for implementation and local verification.
- 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.
- 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.
- 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
never report "done" unless status is accepted.
@ Limitations
- Use this skill only when the task clearly matches the scope described above.
- never treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
Regtransfers/computer-use-agents
tools
VerifiedTrustedCommunity
Build AI agents that interact with computers like humans do - viewing screens, moving cursors, clicking buttons, and typing text. Covers Anthropic's Computer Use, OpenAI's Operator/CUA, and open-source alternatives.
SKILL.mdUpdated Jul 22, 2026
Regtransfers/comprehensive-review-pr-enhance
testing
VerifiedTrustedCommunity
Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.
SKILL.mdUpdated Jul 22, 2026
Regtransfers/comprehensive-review-full-review
tools
VerifiedTrustedCommunity
Use when working with comprehensive review full review
SKILL.mdUpdated Jul 22, 2026
Regtransfers/competitor-alternatives
development
VerifiedTrustedCommunity
You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively.
SKILL.mdUpdated Jul 22, 2026