subagent-router

Route subagents to pipeline stages using a four-trigger priority table.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill subagent-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-router
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/subagent-router
Command: npx skills add https://github.com/yiwei79/azoth --skill subagent-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assign subagent_type and isolation triggers to pipeline stages to enforce isolation and governance without per-pipeline hardcoding, providing auditable routing.

Core Features & Use Cases

  • Fresh-context routing: assigns subagent_type per stage using a four-trigger priority table.
  • Spawn-prompt contract: defines a compact YAML payload for subagents and forwards prior stage summaries.
  • Stage briefs & governance: ensures consistent stage briefs and governance checks across pipelines like auto, deliver, and deliver-full.

Quick Start

Spawn a fresh-context subagent for a given stage by selecting the matching trigger and subagent_type.

Frequently Asked Questions about subagent-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce fresh-context isolation across pipeline stages?

Fresh-context isolation is enforced by assigning subagent_type per stage via a four-trigger priority table and a spawn-prompt contract. This prevents cross-stage context leakage and provides auditable routing across pipeline executions.

What is a spawn-prompt contract for subagent orchestration?

A spawn-prompt contract is a compact YAML payload that defines the instructions and data forwarded to subagents. It carries prior stage summaries to ensure fresh-context isolation and consistent governance during subagent orchestration.

How do I assign subagent_type dynamically without hardcoding per pipeline?

You assign subagent_type dynamically by matching pipeline stages against a canonical four-trigger routing policy. This provides auditable routing and consistent governance without modifying the orchestrator code for each pipeline.

Can I use subagent routing for governance checks across multiple pipelines?

Yes, subagent routing can be used for governance checks across multiple pipelines like auto, deliver, and deliver-full. The routing policy enforces consistent stage briefs and governance considerations, providing auditable routing without hardcoding.

What is the best way to forward prior stage summaries to a new subagent?

The best way to forward prior stage summaries is by using a spawn-prompt contract. This compact YAML payload passes the necessary context to the newly spawned subagent while maintaining fresh-context isolation across the pipeline.

Why does my pipeline lose context isolation between orchestration stages?

Pipelines lose context isolation when subagent_type assignments and triggers are hardcoded per pipeline. Implementing a four-trigger routing policy with a spawn-prompt contract enforces fresh-context isolation and prevents context bleeding.