メニュー
Use when a cybernetic runtime is preparing any fixed, passing, deployed, accepted, or goal-achieved claim and must bind fresh evidence to the exact approved candidate.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a formed task needs durable human-approved meaning, completion obligations, evidence claims, non-goals, or live/destructive authority boundaries.
Use when maintaining or resuming an existing v1 requirements.control.json run; new runs use forming-cybernetic-commitments.
Use when an existing v1 run must compile its reviewed control chain into runtime.control.json.
Use when optional local workflow guidance or legacy v1 workflow compatibility needs diagnosis.
Use when an existing v1 control chain requires design.control.json; v2 strategies remain agent-owned.
Use when cybernetic routing is requested but user input is pre-task intent or role-ambiguous context: confusion, dissatisfaction, risk sense, observed symptoms, failed attempts, method preference, process distrust, source material, declared current state, or unclear requested transformation.
| name | cybernetic-verification-workflow |
| description | Use when a cybernetic runtime is preparing any fixed, passing, deployed, accepted, or goal-achieved claim and must bind fresh evidence to the exact approved candidate. |
Establish whether the exact approved candidate satisfies its completion claims. Verification observes state; it does not grant itself semantic approval.
what_counts_as_done.Tests are one possible evidence source, not the default definition of quality. Prefer direct end-to-end observations when they prove the user-visible or cross-component state more efficiently.
goal_achieved: true unless all required verifier and semantic
review conditions for that exact candidate are satisfied.