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
explain-decisionFetch the full reasoning behind an AxonFlow policy decision — matched policies, risk level, override availability, recent hit count
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this skill when a user asks "why was that blocked?", "what policy fired?", or wants the context behind an allow/deny before retrying or requesting an override.
Call the explain_decision MCP tool with the decision_id returned in the original policy-check response (e.g. decision_id on a check_policy response or in the deny block reason).
The response includes:
policy_matches[] — every matched policy with policy_id, policy_name, risk_level, and allow_overridedecision — "allow" or "deny"reason — human-readable summaryrisk_level — critical, high, medium, lowoverride_available — whether the caller can request a session overridehistorical_hit_count_session — how often this exact decision_id pattern has fired in the rolling 24h windowPresent the result as a short summary: which policy fired, the risk level, whether an override is available, and (if so) suggest the user invoke create-override with a justification.