agent-completion-gate

Use before declaring a long, multi-stage, or artifact-producing task done — prepare a completion CANDIDATE (not a completion). Enumerate touched user-visible surfaces, reconcile thread expectations against the plan, gather real evidence paths, and run the external gate; any uncovered surface, failed check, or review item forces blocked. Use at task wrap-up for long/high-stakes work. Do not use to declare completion yourself — only an external verifier grants `complete`.

Use when the user asks to set up / install / initialize the completion gate in their project (e.g. "set up the completion gate", "add the completion gate to this repo"). Runs the bundled deterministic scaffolder (scripts/init.sh) to create gate/, control/, state/, and a CI workflow, then tells the user what THEY must protect. Does NOT make the gate authoritative — branch protection + CODEOWNERS are the human's job and must not be done by the agent.

Use when the user sets a substantial, multi-step or long-running goal/task — naturally phrased, no prefix needed: "设计goal: ...", "goal: ...", "我的目标是...", "帮我完成这个任务/目标", "help me build/implement X", "做一个X". For work that produces a user-visible artifact (feature, page, report, export, copy/文案, schema, release, migration, experiment) — short length does not exempt it — or spans multiple files/steps. Do NOT use for typo fixes, one-line tweaks, one-off questions, lookups, or trivial edits — handle those directly unless the user explicitly asks for the gate. STEP 1: read this SKILL.md (path given) in full first. HARD RULE — the user stating a goal is NOT approval of scope or done; you only DRAFT criteria. Before ANY draft, outline, sample, placeholder, artifact, file edit, or command, reply with the acceptance criteria in plain language and STOP for the user's explicit OK. Do not preview or partially produce the deliverable before that OK. Only the external gate grants complete; never self-certify.