# IDEA-024: Tech-lead as task dispatcher with specialist coder routing

**Date:** 2026-03-05
**Source:** user
**Status:** raw

## Idea

Tech-lead becomes the dispatcher between architect and coder. After receiving a PLAN, tech-lead scans available agents in `.claude/agents/`, determines which specialist is best suited for the task (e.g., pydantic-ai-specialist for LLM code, coder for general Python), and assigns it. If no suitable specialist exists, tech-lead proposes creating one via `/create-agent` ("hiring").

Shared developer rules (TDD, coverage, commit style) move to iEVO.md "Developer Standards" section — all coder-type agents read this at session start rather than duplicating rules in each agent file.

Pipeline becomes:
```
Spec-writer → Architect → Tech-lead (dispatch) → Coder/Specialist → QA → Acceptance
```

## Why

Currently architect always delegates to generic `coder`. But as the team grows with specialists (pydantic-ai-specialist, future rust-specialist, etc.), there's no routing logic. Tech-lead already knows the domain from the plan and is the right agent to decide who should implement it. If no specialist exists, the "hire" flow via `/create-agent` keeps the team composable.
