Janus Router

IPurpose

Pick the smallest janus sub-skill that fits the request. Do not load other janus references unless the chosen sub-skill needs them.

IITier Auto-Detection

| Signal | Tier | |---|---| | Single quick question, no project state, one-line answer | Tier 1 | | "Fix this", "update", "add a feature", "continue work", routine repo or content task | Tier 2 | | "Audit", "deploy production", "build the X system", judge engine, automation pipeline, multi-file multi-folder change, security review | Tier 3 |

When in doubt: Tier 2.

IIIMode Auto-Detection

• Implementation-heavy code work → Build Mode ($janus-build-mode).
• Warhammer 40K rules question or event judging → Judge Mode ($janus-judge-mode).
• Copy, scripts, social, email, packet, video metadata → Content Mode ($janus-content-mode).
• User wants checkpoints / gated progress → Operator Mode (handled inline by the chosen tier skill).

IVRouting Table

| Request shape | Route to | |---|---| | Tier 1 quick task | $janus-tier1-quick | | Tier 2 normal project | $janus-tier2-project | | Tier 3 system / production | $janus-tier3-system | | Code work in Build Mode | $janus-build-mode | | Warhammer 40K judge work | $janus-judge-mode | | Content / copy / video / packet | $janus-content-mode | | End-of-session continuity log | $janus-worklog | | Onslaught code, gates, deploy matrix | $onslaught-engineering | | Building a new Claude Code plugin | $janus-plugin-build |

VOperating Rules

• Classify tier and mode before acting.
• Load only the sub-skill's own SKILL.md. Do not pre-load references.
• References under references/ are demand-loaded by Tier 3.
• Templates under templates/ are demand-loaded by scripts/new_project.py or by the worklog skill.
• Stop expanding context when the answer is in reach.
• Two strikes then ask. Never repeat a failed approach with cosmetic tweaks.

VIOutput

Return: selected tier, selected mode, selected sub-skill, and the next concrete action. No preamble.