Menu
Intercept explicit doc-update requests and route to the correct command
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Provide orientation to the Knowledge Graph system architecture and guidance for knowledge capture
Enforce zero-deviation plan execution when user invokes plan implementation
Auto-surface ADR creation when user makes architectural decisions or chooses between technical approaches
Auto-invoke knowledge graph search when user asks about project history, past decisions, or previously solved problems
Ensure the knowledge graph is consulted before any recommendation is made
Route capture-that / remember-that requests to the correct destination via auto-detection
Baseado na classificação ocupacional SOC
| name | kmg-doc-update-router |
| description | Intercept explicit doc-update requests and route to the correct command |
Purpose: Intercept explicit doc-update requests and route to the correct command. Prevents doc edits from bypassing the /kmgraph:kmg-update-doc wizard, standards validation, and changelog enforcement.
Trigger Patterns (match any):
Do NOT trigger on:
session-wrapRouting Logic (check in this order):
If intent includes "session summary" / "current session" / "today's session":
→ Dispatch to session-summary-agent (or /kmgraph:kmg-session-summary on Claude Code)
If intent includes "changelog":
→ Dispatch to document update handler with CHANGELOG.md (or /kmgraph:kmg-update-doc --user-facing CHANGELOG.md on Claude Code)
If intent includes "adr":
→ Dispatch to ADR creation handler (or /kmgraph:kmg-create-adr on Claude Code)
If a doc filename or name can be resolved from the intent:
→ Dispatch to document update handler with {resolved_path} (or /kmgraph:kmg-update-doc --user-facing {resolved_path} on Claude Code)
If intent is ambiguous (e.g., "update the docs"): → Ask: "Which doc would you like to update?" → Then dispatch to document update handler
ECC Compatibility Note: The routing above describes agent and function-based dispatch in platform-agnostic terms. The parenthetical Claude Code command syntax is provided for reference but should not be hard-coded in ECC implementations. Each platform dispatches through its native agent/command system.
Conflict with session-wrap: These skills serve different intents and do not conflict.
| Skill | Fires on |
|---|---|
doc-update-router | Explicit request: "update the session summary" |
session-wrap | End-of-session signals: "stop", "I'm done", context limit |
If both could fire simultaneously (e.g., "update the session summary and stop"), doc-update-router takes precedence for the explicit intent; session-wrap adds end-of-session wrap-up on top.
User-Facing Language:
[resolved doc] through the update wizard..."