メニュー
Resolve decision-shaped blocking gaps one at a time — Context Confidence gate failures during an active protocol, or pre-engagement requirements ambiguity routed by the Command Integrity Standing Order.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Diagnose over-abstraction in a package, then consolidate files by domain and deduplicate functional logic.
git worktree 생성과 제거 라이프사이클을 하나의 절차로 통합해 실행하는 스킬입니다.
Per-carrier request-block contracts and dispatch composition rules for carrier_dispatch requests. Load before the first dispatch of the session; skip reloading if already in context.
Host-owned Fleet Plan authoring and mutation workflow. Load before the first host plan_write call in a session and skip reloading when already in context. Use it for the required Plan template, optional Nimitz Plan assurance, Genesis Plan-driven handoff, host completion marking after artifact inspection, and Plan-state verification boundaries.
Drive a headless real-browser end-to-end test or diagnosis of the Fleet Console web UI with agent-browser. Use for Console SPA behavior such as blank screens, terminal rendering, Theater or Operation interactions, modal and keyboard boundaries, responsive layout, browser errors, HTTP requests, WebSockets, or final browser verification after a Console change. Do not use for Electron lifecycle, native menus or dialogs, Desktop security policy, packaging, or installed-app behavior; use desktop-e2e instead.
Use the coordinated Fleet protocol mode for multi-carrier or parallel ownership work.
| name | assumption-audit |
| description | Resolve decision-shaped blocking gaps one at a time — Context Confidence gate failures during an active protocol, or pre-engagement requirements ambiguity routed by the Command Integrity Standing Order. |
Use this auxiliary skill only when a decision-shaped blocking gap has been found: either the active protocol or Context Confidence re-entry path surfaced it, or the Command Integrity Standing Order routed a pre-engagement requirements ambiguity here before a protocol mode loads. This skill is not a protocol mode, does not replace the active protocol, and cannot declare the planning boundary passed by itself.
For each unresolved blocking gap, triage the gap before questioning:
When a gap is decision-shaped, ask one question at a time. Present your recommended answer first, then give one or two concrete alternatives when useful. Walk decision dependencies one branch at a time until the current gap is resolved; do not bundle unrelated gaps into the same question.
After the gap is answered, report the resolved decision in one short line and return control to the caller: the active protocol or Context Confidence Standing Order on re-entry, or the Protocol Gate when invoked pre-engagement. An active workflow must re-evaluate confidence and re-apply the required planning boundary gate before planning proceeds.
