[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-ef2fb039-eeee-44b2-8cc4-7e8e0514d99a":3,"$f2rBx4Dbj4h8kUGZ308iV8KwItaWIwWdTbUdlvXQpTvg":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"ef2fb039-eeee-44b2-8cc4-7e8e0514d99a","acceptance-orchestrator","使用时，应从问题接收通过实施、审查、部署和验收验证，以最小化人工重新干预的方式驱动编码任务端到端。","cat_life_career","mod_other","sickn33,other","---\nname: acceptance-orchestrator\ndescription: 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.\nrisk: safe\nsource: community\ndate_added: \"2026-03-12\"\n---\n\n# Acceptance Orchestrator\n\n## Overview\n\nOrchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.\n\nCore rule: **do not optimize for \"code changed\"; optimize for \"DoD proven\".**\n\n## When to Use\n- The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.\n- You need structured handoff across implementation, review, deployment, and final verification.\n- You want explicit stop conditions and escalation instead of silent partial completion.\n\n## Required Sub-Skills\n\n- `create-issue-gate`\n- `closed-loop-delivery`\n- `verification-before-completion`\n\nOptional supporting skills:\n- `deploy-dev`\n- `pr-watch`\n- `pr-review-autopilot`\n- `git-ship`\n\n## Inputs\n\nRequire these inputs:\n- issue id or issue body\n- issue status\n- acceptance criteria (DoD)\n- target environment (`dev` default)\n\nFixed defaults:\n- max iteration rounds = `2`\n- PR review polling = `3m -> 6m -> 10m`\n\n## State Machine\n\n- `intake`\n- `issue-gated`\n- `executing`\n- `review-loop`\n- `deploy-verify`\n- `accepted`\n- `escalated`\n\n## Workflow\n\n1. **Intake**\n   - Read issue and extract task goal + DoD.\n\n2. **Issue gate**\n   - Use `create-issue-gate` logic.\n   - If issue is not `ready` or execution gate is not `allowed`, stop immediately.\n   - Do not implement anything while issue remains `draft`.\n\n3. **Execute**\n   - Hand off to `closed-loop-delivery` for implementation and local verification.\n\n4. **Review loop**\n   - If PR feedback is relevant, batch polling windows as:\n     - wait `3m`\n     - then `6m`\n     - then `10m`\n   - After the `10m` round, stop waiting and process all visible comments together.\n\n5. **Deploy and runtime verification**\n   - If DoD depends on runtime behavior, deploy only to `dev` by default.\n   - Verify with real logs\u002FAPI\u002FLambda behavior, not assumptions.\n\n6. **Completion gate**\n   - Before any claim of completion, require `verification-before-completion`.\n   - No success claim without fresh evidence.\n\n## Stop Conditions\n\nMove to `accepted` only when every acceptance criterion has matching evidence.\n\nMove to `escalated` when any of these happen:\n- DoD still fails after `2` full rounds\n- missing secrets\u002Fpermissions\u002Fexternal dependency blocks progress\n- task needs production action or destructive operation approval\n- review instructions conflict and cannot both be satisfied\n\n## Human Gates\n\nAlways stop for human confirmation on:\n- prod\u002Fstage deploys beyond agreed scope\n- destructive git\u002Fdata operations\n- billing or security posture changes\n- missing user-provided acceptance criteria\n\n## Output Contract\n\nWhen reporting status, always include:\n- `Status`: intake \u002F executing \u002F accepted \u002F escalated\n- `Acceptance Criteria`: pass\u002Ffail checklist\n- `Evidence`: commands, logs, API results, or runtime proof\n- `Open Risks`: anything still uncertain\n- `Need Human Input`: smallest next decision, if blocked\n\nDo not report \"done\" unless status is `accepted`.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,58,1160,"2026-05-16 13:00:41",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"其他","other","mdi-page-next-outline","其他类型Skill",5,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"职场发展","career","mdi-briefcase-outline","面试准备、简历优化、职业规划",4,575,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"adf4802a-ab0e-4e7e-b820-fced685751b7","1.0.0","acceptance-orchestrator.zip",1789,"uploads\u002Fskills\u002Fef2fb039-eeee-44b2-8cc4-7e8e0514d99a\u002Facceptance-orchestrator.zip","c8b1ec409195e6e5fd4653e95c1685165ccda2a761cfe3c40436dae1e6d7a68c","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":3612}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]