A team of AI apps, run by a Project Manager.
One Project Manager (PM) leads up to six seats on one project, and each seat runs on its own AI app: Claude, ChatGPT, Gemini or Grok.
- Goal
- Plan
- Briefs
- Build
- Review
- Memory
- Ask
Build your team.
Give each seat an AI app, a model and a speciality, or start from a recommended team like Balanced or Cross-check.
Build your team
One PM leads. Add up to six seats, each on its own AI app.
Lead (PM)
Plans the work, splits it and routes each piece to the right seat.
ClaudeUI designer
Builds the screens people see and makes them look right.
GeminiDeep builder
Takes the hardest and riskiest work.
ClaudeQuick coder
Small, well-specified changes, done fast and cheap.
ChatGPTHelper
Takes the supporting work off the other seats.
Grok
- ClaudeLeads or takes a seat
- ChatGPTLeads or takes a seat
- GeminiLeads or takes a seat
- GrokTakes a seat
When an AI app hits its limit.
Give a seat a second AI app. A limit of 30 minutes or more moves the seat there, and it picks up from its handoff. It moves back once the limit resets.
Seat 2
Deep builder
GeminiA limit of 30 minutes or more moves this seat to Claude, which picks up from its handoff. It moves back to Gemini once the limit resets.
On Claude while Gemini waits out its usage limit. It moves back once the limit resets.
Add a seat while the team works.
Open the live team map, add a seat, and it joins the running team. Your PM is told it joined, and reads what the new seat is for before it hands out work.
Your team
- coder-5
coder-5 joins the running team, and your PM is told it joined.
How the work moves.
From your goal to reviewed work, in six steps. The messages travel between the seats on their own.
You give the goal.
Tell the PM what you want, in your own words.
The plan goes on the roadmap.
The PM keeps STATE.md, ROADMAP.md and DECISIONS.md at the project root. It offers to create them once and never overwrites one of yours.
Each seat gets the work it is for.
The app writes each seat’s AI app, speciality and what not to send it into one file. The PM reads it and routes every job to the right seat.
comms/TEAM.mdThe coders build at once.
Every brief carries an objective, a scope and acceptance criteria, and the PM splits the jobs so two seats never edit the same files.
## Objective## Scope## Acceptance criteriaThey report back.
Each seat works on its own branch, runs the tests and sends one report. The app delivers it to the PM.
The PM reviews.
It checks what came back before it tells you the work is done.
What the Project Manager (PM) handles.
- Runs the team
- Splits the work into one bounded job per seat, each with a clear finish line.
- Keeps the decisions
- Makes the calls that stay inside what you agreed, and writes each one in DECISIONS.md with the date and the reason.
- Keeps its place across a compaction
- It keeps a handoff file with its exact next step and asks the app for a compaction when it is ready. Afterwards the app reads that step back to it and the work carries on.
Asks you one precise question, only when it must
About money, work beyond what you agreed, anything that cannot be undone, brand and taste, or a second failed attempt. It says what it recommends, and the question arrives in your inbox in the app.