Giving Every Agent a Role

Part of the Vibe Coding: Multi-Agent Engineering course

In the last lesson you designed a team: a product manager, an architect, a developer, a reviewer, and the others, each a role you will hand to the same AI. A list of roles is not yet a team, though. A team is what you get when each role is defined so precisely that the agent knows exactly what it owns, what it does not, and what to do with the work when it is done. This reading lesson is about that craft.

A responsibility is the slice of the work one agent owns and answers for. The first job of any role is to name that slice out loud. The developer agent owns writing the code that makes a feature work. The reviewer agent owns judging whether that code is correct and safe to ship. When ownership is clear, you always know which agent to point at a piece of work, and each agent knows the one thing it is accountable for. ...