From kmgraph
Enforces strict zero-deviation plan execution with file editing constraints, verification-only shell access, prerequisite checks for roadmap/changelog sync, and ADR cascade review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kmgraph:gov-execute-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** Enforce zero-deviation plan execution when user invokes plan implementation.
Purpose: Enforce zero-deviation plan execution when user invokes plan implementation.
Trigger Keywords:
docs/plans/*.md file in conversationBehavior: When triggered, surface the STRICT EXECUTION MODE banner and enforce the 8-step protocol:
═══════════════════════════════════════════════════════════════
STRICT EXECUTION MODE
Allowed Tools: File read, file edit, file write, shell (verification only)
Forbidden: Improvements, assumptions, gap-filling, unauthorized fixes
═══════════════════════════════════════════════════════════════
ECC Compatibility Note: The banner above uses generic tool categories (file read/edit/write, shell) to maintain portability across ECC platforms. On Claude Code, these map to Read, Edit, Write, and Bash tools. On other platforms, the underlying MCP or native tool implementations are used automatically. The constraint semantics remain identical: no authorization changes outside the plan.
Prerequisite Check — Step 6.4 Sync Verification: Before implementing any ENH or issue in scope, verify that Step 6.4 (ROADMAP + CHANGELOG sync) was completed for each item. This check fires at implementation start, not at issue-tracking completion.
For each ENH/issue in the plan:
⚠️ PREREQUISITE CHECK — Step 6.4 Not Completed
Before implementing [ENH-NNN / issue-N], Step 6.4 (ROADMAP + CHANGELOG sync) was not completed.
Options:
[C] Complete now — run ROADMAP + CHANGELOG sync inline, then proceed
[S] Skip — proceed without sync (your choice; noted in commit message)
[X] Cancel — abort implementation
Enter choice (C / S / X):
HALT — Implementation cancelled. Complete Step 6.4 before retrying.This check runs once per item, before the first edit for that item.
Prerequisite Check — In-Plan Cascade Review: Before executing, check for ADR capture flag:
ADR_FLAG="/tmp/kmgraph-adr-captured-$(date +%Y-%m-%d).flag"
If flag EXISTS:
If flag ABSENT: skip this check and proceed normally.
Detection mechanism: flag file written by
adr-guideafter successful ADR creation. Day-scoped via$(date +%Y-%m-%d)— consistent with existingkmgraph-plan-gatepattern. No model self-tracking required.
Subagent fallback: If
gov-execute-planis somehow invoked as a subagent with the flag present (parent failed to gate), output: "Parent must resolve in-plan cascade before dispatching subagents. HALT." Do not attempt to prompt the user — subagents have no interaction channel.
Protocol Steps:
Source: Adapted from .agent/workflows/gov-execute-plan.md
Key Constraint: "No improvements" — even if you spot bugs, better implementations, or missing error handling, DO NOT FIX unless explicitly in the plan.
Example Trigger:
User: "Let's execute the v0.0.10.1 plan from docs/plans/v0.0.10.1-alpha-skills-and-agents.md"
Assistant Response: Output STRICT EXECUTION MODE banner and follow 8-step protocol.
v0.2.1 Decision Note — Agent Dispatch Evaluation: Agent dispatch was evaluated and rejected for this skill. Rationale:
npx claudepluginhub technomensch/knowledge-graph --plugin kmgraphFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.