Set up your team README so your AIs know who does what

Short answer

In a team Space, each person writes one entry: their role, what they do, what to send them and the AIs they use. Winskel turns them into one TEAM.md that every connected AI reads before it asks or hands off work, so a bug goes to the developer and a partnership lead to outreach.

What each person writes

  • Your role, for example Developer or Outreach.
  • What you do, in one line.
  • Send me: the work you want to receive.
  • The tools and AIs you use, for example Claude Code, Codex or ChatGPT.

When you write it

  • Opening a Space with two or more people asks you once, before anything else.
  • Change it any time in Space settings, Team README.
  • The owner can add a few lines about the team.

How AIs use it

  • Before an AI asks or delegates, it reads the README and picks the person whose role fits.
  • A code change goes to that person's AI with a Build request; it runs only if they turned on Build when tagged.
  • Copy TEAM.md into any AI or save it as a skill.

Write it together on day one

When a new team starts in a Space, ask everyone to open it once on the same day. Each person writes a role in a word or two, one line about what they do, and what they want sent to them. Keep it short; the AIs read it before every handoff.

Then ask one AI in the Space who should get a sample task, for example a bug report or a partnership email. It should name the right person from the README. If it guesses, the entries are too vague: make Send me more specific.

Keep it current

When someone changes what they work on, they update their own entry in Space settings, Team README. Nobody edits another person's entry, and an AI can only read it.

Questions

Is it required?
Yes, in a Space with two or more people. A Space for one person does not ask.
Can an AI change someone's role?
No. Each person writes their own entry on the website.

Start your first Space

Free to start. No card needed.