一键导入
completion-interlock
Fires right before declaring a code-changing task "complete". Final gate that verifies the presence and quality of all artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Fires right before declaring a code-changing task "complete". Final gate that verifies the presence and quality of all artifacts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fires when deciding whether a report or explanatory document needs figures, when designing a figure, or when writing the figures declaration in frontmatter. Designs cognitive-load-reducing figures via the trigger table, quantitative limits, and templates
Fires when generating or verifying deterministic HTML from report MDs. Runs render / verify / lint / selftest / check via the bundled md2html.cjs
Fires when producing a report or completion notice. Generates a report that includes the interlock verification section.
Discipline for preventing the stop bug (malformed tool call -> self-priming). Fires when the stopbug-observe hook emits a trip-wire (migration advice) or the time-based timer (calibration prompt), or as a minimal focus-check right before heavy processing.
報告書・説明文書で図を使うか判断する際、図を設計する際、frontmatter の figures 宣言を書く際に発火する。図トリガー表・定量上限・雛形で「認知負荷を減らす図」を設計する
報告書 MD から決定論 HTML を生成・検証する際に発火する。md2html.cjs(同梱)で render / verify / lint / selftest / check を実行する
| name | completion-interlock |
| description | Fires right before declaring a code-changing task "complete". Final gate that verifies the presence and quality of all artifacts. |
Fires right before declaring a code-changing task "complete". Functions as the final gate immediately after testable-impl Step E.
Before declaring a code-changing task complete, verify ALL of the following. If even one is missing, do NOT declare completion.
| Artifact | Verification |
|---|---|
| Report MD file | File exists directly under _Prompt\02_buildai\ (legacy _Prompt\01_FromBuilderAi\ also accepted) |
| "Readers and Purpose of This Report" section | Explicitly stated at the top of the report MD, right after the frontmatter |
frontmatter audience / purpose / expected_action | Provisionally written in the report MD frontmatter (optional) |
| Before / After measured values | Written inside the report MD (not in-conversation text) |
| Every concrete completion criterion | Verified inside the report MD with measured values |
| Two-tier structure: dev log + canonical report | Where applicable: both the dev log in the working repo and the canonical report in the upstream doc repo are placed |
_Research/ subdirectoryChanges that do not affect logic (comment fixes, typo fixes, whitespace adjustments, etc.) are out of scope for this interlock. When in doubt, treat the change as in scope.
This skill is CC's self-verification (checks content quality). hooks/report-gate is external verification (mechanically checks only the existence of the report MD). The two are independent dual-layer defenses; neither alone is sufficient.