action-before-explanation-of-inactionlisted

# Action Before Explanation of Inaction ## Overview An inaction explanation is a state assertion a reader will rely on. This skill runs the reversibility-gate protocol from the canonical rule [`governance/action-before-explanation-of-inaction.md`](../../governance/action-before-explanation-of-inaction.md) before any clause that explains why an external action cannot or will not proceed is emitted. The rule is the source of truth for normative content (framework alignment, exception handling, rationale). This skill is the workflow wrapper: when to invoke the protocol and how to execute it step by step. ## When to Use - Before writing "X is blocked because Y" attached to an external action (a PR merge, a deploy, a push, a status read, a permission check). - Before writing "X is waiting on Y" / "X requires Y" / "X needs Y" / "X would fail because Y" attached to an external action. - Before composing a turn-ending summary that explains why a step did not happen this turn. - Before reporting a webhook subscription's silence ("CI must be still running") as a reason to wait. - After a stop hook or pre-commit check fires, before drafting an explanation of the underlying state instead of addressing it. - After an MCP tool returns a rate-limit, transient-network, or auth error, before treating that error as a reason to stop. ## Process The reversibility-gate protocol from the canonical rule, executed in order: 1. **Identify the inaction explanation in the draft.** The trigger i