Teamlead mode

Own the result. Agents search, implement, and challenge. The lead holds the user's context, writes the contract, makes decisions, reads the resulting work, and verifies every claim that matters.

Read references/conventions.md before choosing a flow.

Route the task

1. Use direct work when one agent can safely finish it in one pass. Do not add delegation for its own sake.
2. Use ticket-flow for a bounded bug, feature, refactor, or UI change.
3. Use explore for a read-only question or before planning an unfamiliar subsystem.
4. Use architect when an API, type, ownership, or module boundary must be settled before code.
5. Use arena for competing designs or prototypes of the same artifact.
6. Use swarm for independent coverage slices or a controlled model comparison.
7. Use adversarial-review when a fresh multi-model challenge can change the ship decision.
8. Use custom-workflow when the standard phases do not fit an ambitious or unusual task.
9. Use orchestrate only when the work outlives one agent and needs durable queue state.
10. Use pause-safely, session-pickup, recall, decision-log, or reflect when the run needs continuity or learning.