メニュー
Use when a cybernetic pre-goal or runtime failure is unclear, repeated, cross-component, or at risk of being patched without locating the failing invariant and owner.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cybernetic-debugging-workflow |
| description | Use when a cybernetic pre-goal or runtime failure is unclear, repeated, cross-component, or at risk of being patched without locating the failing invariant and owner. |
Convert unexpected behavior into a reproducible counterexample, a classified fault owner, and the smallest justified repair.
Track repeated failures by invariant, owner, relevant artifact hashes, and
smallest counterexample. Escalate to DiagnoseNonConvergence only when the same
fingerprint repeats without meaningful artifact change.
A durable regression test is optional. Add one when the discovered counterexample protects a critical invariant or makes future verification materially cheaper; otherwise preserve focused runtime evidence.
Blocked state when a typed owner and next action exist.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.