🔀 Coupling Router — Architectural Delegation, Skill-Stack & Concurrency Router

Evaluates the topological coupling of a task breakdown and audits active skill stacks before dispatching subagents. Deterministically routes tightly coupled tasks (shared types, schema migrations, rendering pipelines) to a single sequential builder, dispatches truly orthogonal tasks (isolated test suites, independent docs, separate microservices) to parallel fan-out subagents, and audits installed skills to enforce a Minimal Viable Skill Set (MVSS) that eliminates prompt contradictions and token bloat.

When to Use

Trigger Conditions

Execute this skill when:

1. Planning Multi-Agent Delegation: You have a task list or project plan with 2 or more subtasks.
2. Auditing Skill-Stack Compatibility: Multiple agent skills are installed or active, risking prompt contradictions, overlapping triggers, or token budget exhaustion.
3. Enforcing Minimal Viable Skill Set (MVSS): Trimming secondary/redundant skills when a primary dominant skill (e.g., ai-ready, git, refactor-ui, code-review) already covers the execution scope.
4. Preventing Merge Collisions: Multiple files or modules share mutable state, type contracts, or lifecycle flows.
5. Deciding Concurrency Strategy: Resolving whether to spawn subagents concurrently in parallel or pipeline them sequentially.
6. Complex Refactors: Multi-layer changes spanning database schemas, API controllers, and frontend clients.
7. Shared Checkout, Multiple Sessions (/worktree-lease): Another agent session (or a human) may be working in the same git clone — acquire or respect the worktree lease before switching branches, touching stashes, or staging shared files.