Acceptance Orchestrator V2

Acceptance Orchestrator

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/acceptance-orchestrator from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Acceptance Orchestrator

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Required Sub-Skills, Inputs, State Machine, Stop Conditions, Human Gates, Output Contract.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• 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.
• Use when the request clearly matches the imported source intent: a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Intake
2. Read issue and extract task goal + DoD.
3. Issue gate
4. Use create-issue-gate logic.
5. If issue is not ready or execution gate is not allowed, stop immediately.
6. Do not implement anything while issue remains draft.
7. Execute

Imported Workflow Notes

Imported: 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.

Imported: 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".

Imported: Required Sub-Skills

• create-issue-gate
• closed-loop-delivery
• verification-before-completion

Optional supporting skills:

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

Examples

Example 1: Ask for the upstream workflow directly

Use @acceptance-orchestrator-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @acceptance-orchestrator-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @acceptance-orchestrator-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @acceptance-orchestrator-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/acceptance-orchestrator, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: 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

Imported: State Machine

• intake
• issue-gated
• executing
• review-loop
• deploy-verify
• accepted
• escalated

Imported: 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

Imported: 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

Imported: 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.

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not 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.