agent-routing

Agent Routing -- Choose the Right Execution Pattern

Before spinning up agents or teams, run this decision framework. The goal is to match the execution pattern to the task, not default to the most complex option.

---

Step 0: Decision-Lock Check

Before analyzing execution pattern, check for an existing CONTEXT.md:

1. CONTEXT.md exists in the feature working directory -- Read the ## Decisions section. Use locked decisions to inform the 5-dimension analysis below. Do not re-ask anything already decided.

2. No CONTEXT.md AND task is complex (3+ files across 2+ concerns) -- Recommend /discuss first:

   This task touches [N] files across [concerns]. Recommend running /discuss to lock decisions before routing.

   If the user says "skip" or "just go", proceed to Step 1 without a CONTEXT.md.

3. Task is small (1-2 files, single concern) -- Skip directly to Step 1. No discussion needed.

---

Step 1: Task Analysis

Evaluate the task against these 5 dimensions. Be honest -- do not inflate complexity to justify a team.

1. File Count

How many files will be WRITTEN or EDITED (not read)?

• 1-2 files: Single session territory
• 3-4 files: Subagent territory
• 5+ files across different concerns: Team territory

2. Concern Separation

Are the outputs independent or do they need coordination?

• All outputs go in the same file or closely related files: Single session
• Outputs are in different files but follow the same pattern: Subagents (each mirrors a known pattern independently)
• Outputs are in different files AND require different expertise (content vs code vs config vs deploy): Team

3. Handoff Requirement

Does any task need the OUTPUT of another task before it can start?

• No handoffs -- all tasks can run with existing context: Subagents
• Linear handoff -- A feeds B feeds C: Single session (sequential in one context is faster than agent-to-agent messaging)
• Fan-out handoff -- A feeds B, C, D simultaneously: Team (A completes, then B/C/D run in parallel)