vkc-shared-memory-router - SKILL.md Agent Skill

name: vkc-shared-memory-router description: Enforce the VKC shared memory read order and subagent routing policy so every clean-workspace session, automation, and subagent starts from the same SoT before acting. Use for supervisor automations, repo exploration, multi-agent coordination, or when durable context must be shared across sessions. (키워드=shared memory, subagent router, read order, context memory, automation prompt, supervisor, explorer, worker) metadata: short-description: Shared memory + subagent routing

Always pair this skill with $vkc-repo-guardrails. Use $vkc-loop-supervisor when the task is part of an ongoing loop or automation.

Read the mandatory pack before acting.
- AGENTS.md
- docs/EXECUTION_PLAN.md
- docs/CODEX_PROMPT_PROTOCOL.md
- docs/engineering/codex/CODEX_LOOP_POLICY.md
- docs/engineering/codex/CODEX_SHARED_MEMORY_SYSTEM.md
- docs/engineering/codex/memory/ACTIVE_CONTEXT.md
- docs/engineering/codex/memory/OPEN_LOOPS.md
- docs/ops/CURSOR_BROWSER_TERMINAL_PROTOCOL.md (browser: agent Shell ops:browser:*, not operator typing)
For architecture or automation-boundary changes, also read docs/engineering/codex/memory/DECISION_LOG.md.
Do not let each subagent rediscover the repo from scratch.
Pass only the relevant memory slices, ownership boundaries, and file paths to subagents.

Use explorer for read-only evidence gathering, structure checks, docs scans, and test-log triage.
Use worker only when the write set is disjoint and ownership is explicit.
Keep immediate blockers local to the supervisor.
If preflight is report-only, do not delegate mutation work.