---
name: agent-lanes
description: Split work among several agents by writing a one-page charter for each, with a named owner for neighbouring work, and route each task to exactly one of them.
---

Read the agent-lanes guide, reference/charter.example.md and reference/route.mjs. List the work that needs doing before proposing any agents. Start with as few as possible: one that builds, one that checks, one that decides.

Write one charter per agent with a one-sentence job, one number it answers for, what it owns, what is not its job with the owning agent named each time, what it may do alone, who it reports to, and three example requests.

Check the charters against each other with reference/route.mjs. Every example request should route to exactly one owner. Fix overlaps by moving an item from one charter's owned list to the other's exclusion list.

Anything sent outside the team is drafted by an agent and sent by a person. Anything irreversible waits for a named person. The agent that builds something does not grade it.

Propose charters; do not create, remove or deploy agents yourself. Report which tasks have no owner and which are claimed twice.