shynlee04/hivemind-plugin/hm-l2-lineage-router

The Iron Law

Every task has a lineage. Route to the bundle that matches the task's category. Max 5 skills per bundle.

Lineage Router

Overview

Given a task intent, determine which hm-* skills should be loaded. This skill maps task categories to skill loading bundles. It does NOT execute skills — it only determines which skills to load and in what order.

Six task categories, six skill bundles:

On Load

1. Read references/routing-map.md — the complete routing map with priority ordering and dependency chains
2. Identify the task intent from the current context
3. Classify the task into one of the six categories

Trigger Phrases

• "route task" / "route this task"
• "classify intent" / "classify task intent"
• "which skill to load" / "what skills do I need"
• "task routing" / "lineage routing"
• "skill bundle for task" / "load skills for"
• "skill loading order" / "determine skill lineage"
• "map task to skills" / "skill selection for workflow"

Routing Map

Category 1: Research Tasks

Intent signals: "investigate", "research", "find out", "analyze", "look into", "explore"

Loading order: hm-tech-stack-ingest (if stack cache needed) → hm-detective → hm-deep-research

Category 2: Planning Tasks

Intent signals: "plan", "spec", "requirements", "design", "architect"

Loading order: hm-planning-persistence (setup) → hm-spec-driven-authoring (content)

Category 3: Execution Tasks

Intent signals: "implement", "build", "execute", "run the phase", "code"

Loading order: hm-phase-execution (primary) → hm-cross-cutting-change (when touching multiple layers)

Category 4: Quality Tasks

Intent signals: "test", "verify", "quality", "validate", "TDD", "red-green-refactor"

Loading order: hm-test-driven-execution (implementation) → hm-gate-orchestrator (validation)

Category 5: Debug Tasks

Intent signals: "debug", "fix", "broken", "failing", "error", "investigate issue"

Loading order: hm-debug (investigation) → hm-completion-looping (verification)

Category 6: Review Tasks

Intent signals: "review", "audit", "readiness", "deploy check", "ship ready"

Loading order: hm-production-readiness (evidence collection) → hm-gate-orchestrator (gate verification)

Loading Rules

1. Max 5 skills per bundle. If a task needs more than 5, split the task.
2. Load in priority order. Lower-numbered skills load first.
3. Respect dependencies. If Skill B depends on Skill A's output, load A first.
4. Classify before loading. Determine the category before loading any skills.
5. Multi-category tasks. If a task spans 2 categories, load the primary category's bundle first, then add 1-2 skills from the secondary category (staying within the 5-skill limit).

Multi-Category Decision Tree

Task spans 2 categories?
  → YES: Primary category gets full bundle (2-3 skills)
         Secondary category gets 1-2 skills from its bundle
         Total must be ≤ 5
  → NO:  Load single bundle (2-3 skills)
 
Task spans 3+ categories?
  → SPLIT THE TASK. No single task should span 3+ categories.

Self-Correction

Anti-Pattern 1: Overloading

Detection: More than 5 skills being loaded for a single task. Correction: Split the task into subtasks. Each subtask gets its own bundle. Signal: "Task too broad — split into [A] and [B], then route each independently."

Anti-Pattern 2: Wrong Lineage

Detection: Loading hf- skills for an hm- task, or vice versa. Correction: This router handles hm-* lineage only. If the task is a meta-builder task (creating skills, agents, commands), route to hf-meta-builder instead. If the task is a product-dev task, use this router.

Anti-Pattern 3: Missing Input

Detection: Task intent cannot be classified into any of the 6 categories. Correction: If the task is genuinely new (e.g., "monitor production"), route to the closest category and flag: "No exact match. Routed to [closest category]. Verify the bundle covers the task's needs."

Anti-Pattern 4: Stale Bundles

Detection: A loaded skill references another skill not in the current bundle, and the referenced skill is critical for the task. Correction: Add the missing skill to the bundle if the total stays ≤ 5. If adding would exceed 5, remove the lowest-priority skill from the current bundle and document the trade-off.

Quality Contract (HMQUAL Compliance)

Cross-References