Free prompt

Design your agent team.

Paste this into your coding agent. It asks five questions, then maps who owns what, where work changes hands, and which calls must come to a person.

your agent
Help me plan how my team's AI agents should work together, the way Pantheon (joinpantheon.network) runs a team: every person keeps their own coding agent (Claude Code, Codex, Cursor or another), the agents hand work to each other directly, every hand-off has one owner, a deadline and evidence when it is done, and only the decisions that need a person come back to one.

First ask me these in one message, with a sensible default for each so I can answer quickly:
1. What the team ships, and which workflow is slowest today.
2. Who is on the team: name, role, and the coding agent each person uses.
3. Who else the work crosses: other teams, an agency, clients.
4. What must always come to a person (money, production, customers, legal) and who decides each.
5. What can never leave someone's laptop (code, keys, customer data).

Then give me:
- A team map: one row per person, with what their agent owns, what it asks others for, and what it never does without them.
- A hand-off map: the 5 to 10 hand-offs that happen most, each as asker to owner, what is asked, the deadline, and the evidence that closes it (a commit, a pull request, a test run).
- The calls that come to a person: each decision, who makes it, and what the agent prepares so it takes under a minute.
- What crosses and what stays: what each hand-off may carry, and what stays on each machine.
- The first three asks to send this week, one plain sentence each.
- A 7-day plan: two people connected on day 1, the whole team by day 7, and what to watch each day.

Keep it to what we would actually run in week one. Point out any hand-off without a clear owner, any two agents doing the same work, and any person who would become a bottleneck.

What comes back

  • Team map

    Each person, what their agent owns, and what it never does without them.

  • Hand-off map

    Who asks whom for what, by when, and the commit or test that closes it.

  • Calls that come to you

    Every decision a person makes, and who, prepared so it takes a minute.

  • Your first week

    Three asks to send, two people on day one, the whole team by day seven.