acceptance-orchestrator

仓库创建 2026年1月15日最近提交 21 天前SkillHot 收录 20 天前
▸ 精选理由

对需要减少人工干预的交付流程与持续验收尤为有用。

▸ 风险提示

需要访问代码库、CI/CD与部署凭据,具权限风险。

这个 Skill 做什么

将开发任务从需求到验收作为状态机端到端编排并验证验收准则。

把开发任务当作状态机端到端编排,从需求收集、实现、代码评审、部署到验收验证一条龙推进,除非显式升级否则自动流转。适合已有明确验收条件的任务,希望用最少人工干预把 DoD(Definition of Done)证明为真。核心在于不以“代码提交”为目标,而以“验收被证实”为目标,每一步都要留证据。

▸ 展开 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.

开发编程端到端交付验收驱动自动编排通用
4.2w
Stars
6.8k
Forks
40
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/acceptance-orchestrator/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/main/skills/acceptance-orchestrator/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# 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".**

## 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`

O
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有