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):

"update [filename or doc name]" — e.g., "update quickstart.md", "update the command guide"
"update this doc" / "update the doc" — resolves to most recently referenced doc
"update today's session summary" / "update the session summary" / "update the current session"
"update the changelog"
"update the ADR" / "update the adr"

Do NOT trigger on:

"update the code" / "update the tests" / "update the function" — not doc updates
"let's update" with no doc reference — too ambiguous
End-of-session signals like "I'm done" / "wrapping up" — those belong to session-wrap

Routing 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:

Address the user directly; never expose command names or internal routing mechanics unprompted
Confirm the resolved target before dispatching: "Got it — updating [resolved doc] through the update wizard..."
Use the appropriate command naturally: "I'll use the update-doc wizard to make sure standards are applied."

Más de este repositorio

mismo repositorio

kmg-knowledge-graph-usage

technomensch/knowledge-graph

Provide orientation to the Knowledge Graph system architecture and guidance for knowledge capture

2026-07-165

kmg-execute-plan

technomensch/knowledge-graph

Enforce zero-deviation plan execution when user invokes plan implementation

2026-07-135

kmg-adr-guide

technomensch/knowledge-graph

Auto-surface ADR creation when user makes architectural decisions or chooses between technical approaches

2026-06-225

kmg-auto-recall

technomensch/knowledge-graph

Auto-invoke knowledge graph search when user asks about project history, past decisions, or previously solved problems

2026-06-225

kmg-brainstorm-recall

technomensch/knowledge-graph

Ensure the knowledge graph is consulted before any recommendation is made

2026-06-225

kmg-capture-router

technomensch/knowledge-graph

Route capture-that / remember-that requests to the correct destination via auto-detection

2026-06-225

Skill: kmg-doc-update-router

Trigger Patterns (match any):

"update [filename or doc name]" — e.g., "update quickstart.md", "update the command guide"

"update this doc" / "update the doc" — resolves to most recently referenced doc

"update today's session summary" / "update the session summary" / "update the current session"

"update the changelog"

"update the ADR" / "update the adr"

Do NOT trigger on:

"update the code" / "update the tests" / "update the function" — not doc updates

"let's update" with no doc reference — too ambiguous

End-of-session signals like "I'm done" / "wrapping up" — those belong to session-wrap

Routing 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

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:

Address the user directly; never expose command names or internal routing mechanics unprompted

Confirm the resolved target before dispatching: "Got it — updating [resolved doc] through the update wizard..."

Use the appropriate command naturally: "I'll use the update-doc wizard to make sure standards are applied."