t1k:routing-gap-remediate
| Field | Value |
|---|---|
| Module | t1k-base |
| Version | 5.15.36 |
| Effort | medium |
| Tools | — |
Keywords: agent not matched, fork spawn, general-purpose spawn, generic agent spawned, missing agent, missing skill, routing gap, routing protocol gap, routing-gap-remediate
How to invoke
Section titled “How to invoke”/t1k:routing-gap-remediate[subagent-type] [description] [cwd]Routing-Gap Remediation
Section titled “Routing-Gap Remediation”Closes ONE routing gap generic-agent-detector.cjs already detected — a generic (general-purpose
/ claude / fork / omitted) spawn that matched a specific T1K agent’s keywords but did not use it.
Do not run this ad hoc; it exists for the t1k-routing-gap-remediator background agent the
[t1k:routing-gap-remediate] frame instructs the session to spawn. That agent is the judge
(facts, classification, decision, review); it spawns t1k-routing-gap-fixer to apply and land
the fix.
Full procedure
Section titled “Full procedure”references/procedure.md — the four-way classification → fix → delivery decision table.
When NOT to use
Section titled “When NOT to use”- You are choosing which agent to spawn for a NEW task — that is
docs/orchestration-rules.md§ “Task-Type → Agent Routing”, not this skill.
A spawn enforceAgentRouting BLOCKED is still remediated, not skipped (PR #3130 review, item C) —
a deny only means the model’s FIRST choice was generic; the habit that produced it is exactly what
this skill exists to close, whether or not the spawn itself went through.