From kmgraph
Enforces user approval gates after planning completes and before push/PR — requires explicit "Proceed" or "Start" to continue.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kmgraph:gov-plan-gateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Purpose:** Enforce user approval gates after superpowers planning and execution skills complete — require explicit "Proceed" or "Start" before implementation begins, and explicit approval before any push or PR.
Purpose: Enforce user approval gates after superpowers planning and execution skills complete — require explicit "Proceed" or "Start" before implementation begins, and explicit approval before any push or PR.
Trigger Keywords:
Behavior:
After a plan file is written, output ONLY:
"Plan saved at
<path>. Review it, then say Proceed or Start to continue."
Before pushing or opening a PR, output ONLY:
"Ready to push
<branch>and open PR. Say Proceed to continue."
Then STOP in both cases. Do not:
git push or gh pr create without explicit approvalGate Rules (from ~/.kmgraph/rules.md):
"Wait for explicit 'Proceed' or 'Start' before beginning a new branch or implementation task." "Stop and ask before pushing, creating PRs, merging, or any other action visible to others." "Wait for user confirmation after any 'Next Steps' summary."
These gates apply to ALL planning and execution outputs regardless of which skill ran.
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.