agent-acceptance-gate
Use when about to commit or push a diff that touches two or more locale variants of one file stem, adds catalog or listing…
Use when a consequential decision has two plausible, materially different options and you are about to pick one. Runs two opposed reviewers on the same evidence with a stated round cap, then hands the human a synthesis that names the deciding evidence.
Claude Code
$ npx -y skills add WenyuChiou/agent-collab-skills --skill agent-debate --agent claude-code
Codex
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a codex -y
Cursor
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a cursor -y
Gemini CLI
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a gemini-cli -y
GitHub Copilot
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a github-copilot -y
OpenCode
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a opencode -y
Windsurf
$ npx skills add WenyuChiou/agent-collab-skills --skill agent-debate -a windsurf -y
name: agent-debate description: Use when a consequential decision has two plausible, materially different options and you are about to pick one. Runs two opposed reviewers on the same evidence with a stated round cap, then hands the human a synthesis that names the deciding evidence.
A bounded adversarial review of one consequential trade-off. Debate makes the evidence visible to the decision maker; it does not settle truth by vote and does not authorize implementation.
Do not debate a factual question that a direct check can settle, a naming preference, or a decision an authorized human already made.
1. Write one evidence packet: the decision and who owns it, the two positions as testable statements, shared evidence paths, and the criteria for judging. Template: [references/debate_protocol.md](references/debate_protocol.md). 2. Launch two `reviewer` lanes in parallel, one position each, both on a strong model tier, both read-only, both with the same packet. Each argues the strongest form of its side and cites evidence. 3. State the round cap before launch and stop there. A rebuttal round, if the cap allows one, answers the other side's strongest point. In harness mode the policy's `max_cycles` limit sets the cap; evaluate the policy before each reviewer spawn. 4. A reviewer that changes its conclusion says so plainly; do not simulate disagreement.
The primary-agent, or a separate `synthesizer` with no search tools, writes:
Nothing is implemented and no canonical memory changes until the human decides. If the outcome is worth keeping, write a memory proposal as described in `agent-context-budget`.
繁體中文 · Public harness contract · Native lanes · 0.6 migration · 0.5 goal-slice migration · 0.4 migration Provider-neutral collaboration skills plus an optional, standard-library-first Python harness for bounded, resumable, human-authorized agent work.
Use when about to commit or push a diff that touches two or more locale variants of one file stem, adds catalog or listing…
Use when launching parallel or background subagents, or when a handoff, log, or result would be more than a short summary…
Use when a plan, prompt, or doc still names agent-output-reconciler. Since 0.6.0 reconciliation is step 1 of…
Use when a plan, prompt, or doc still names agent-plan-act-reflect. Deprecated in 0.6.0; ordinary iterate-until-it-passes work…
Use when a plan, prompt, or doc still names agent-shared-memory. Since 0.6.0 proposal-only coordination memory is the Durable…
Use when about to run two or more subagents, workflow lanes, or delegated CLI executors on one goal. Gives each lane a role, a…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.