Purpose: Help your team co-create a TEAM.MD — a shared context file that tells AI tools who you are, how you work, and what guardrails apply.
Time needed: 45–60 minutes as a group, or async over 1–2 days
Before the session
Share the board link with everyone on the team
Ask people to read the prompt in each column header before adding stickies
Nominate one person as the owner who will commit the final file to GitHub
Running the session
Setup:
Purpose of this workshop: generate a shared TEAM.MD file that will give our AI tools the essential context to generate better responses for our team's day-to-day work
Agenda:
For each section, the team brainstorms responses. Teammates should call out where there's ambiguity or conflicting responses, and add/change/delete sticky notes accordingly. Anything on the board will then be converted into the team's TEAM.MD file.Â
Step 1 — Who we are (5 min) One person drafts a 2–3 sentence description of what the team owns. Everyone reacts/edits via stickies.
Step 2 — Team members (10 min) Each person adds their own sticky: Name + Role + What I own + How I work best. Be honest — this is for the AI, not performance review.
Step 3 — How we decide (10 min) List your actual decision rights, not your aspirational ones. Who has final call on what? What needs escalation?
Step 4 — How we communicate (5 min) Channels, tone, review gates. Focus on what a new person (or AI) would get wrong without guidance.
Step 5 — How we use AI (10 min) Split into two parts: what we actively use AI for, and what tasks we consciously keep human. Both matter.
Step 6 — AI guardrails (10 min) This is the most important section. What data must never go into a prompt? What always needs human sign-off?
Step 7 — Key workflows (10 min) Name your 3–5 most important repeating workflows. For each: where does AI help? Where does a human stay in the loop?
After the session
Run the AI flow "Run Prompt" (to the right of the canvas)
Review the generated TEAM.MD together — 15 min is usually enough
Export the document as an .MD file
Owner commits to the repo
Review quarterly, or when the team changes significantly
A TEAM.MD that grows from real problems is more useful than one written speculatively.
