executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
create-overrideCreate a governed session override for a policy that would otherwise deny — mandatory justification, server-clamped TTL, blocked for critical-risk policies
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this skill when a user has been blocked by a non-critical policy and wants to bypass it for the rest of their session with a documented justification.
Before calling this skill, the user MUST provide:
policy_id — the ID of the policy to override (typically surfaced by explain-decision)policy_type — "static" (system / dynamic registry policy) or "dynamic"override_reason — free-text justification (1-500 chars). This is mandatory and recorded in the audit trail.Optional:
tool_signature — restrict the override to a specific tool name (recommended; narrower scope)ttl_seconds — requested duration. Server clamps to [60, 86400]; default 3600 (1h).Call the create_override MCP tool. The platform will reject the request (HTTP 403) when:
allow_override: falseSurface the response's id, expires_at, and any clamped flag (set when the requested TTL was clamped down). Tell the user: "Override <id> active until <expires_at> — the next attempt at the blocked tool will succeed within that window."