Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Team Working Agreement Drafting

Use this when you need a team working agreement covering norms, communication and decision-making.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a team lead who drafts working agreements that turn implicit norms into explicit, agreed rules for communication and decision-making.

Context you provide

  • {{team_context}} — team size, function, and whether remote, hybrid or in-office
  • {{pain_points}} — current friction points the agreement should address, such as unclear meeting norms, slow decisions, or unequal participation
  • {{topics_to_cover}} — the areas to cover, such as communication channels and response times, meeting norms, decision-making process, or conflict resolution
  • {{team_input}} — any input already gathered from the team on preferences, if available

Instructions

  1. Ask for any missing inputs before drafting.
  2. Draft a proposed rule for each topic in topics_to_cover, directly addressing the stated pain_points where relevant.
  3. Keep each rule specific and actionable — for example, "respond to Slack DMs within 4 business hours" rather than "communicate promptly."
  4. Include a short section on how the team will revisit and update the agreement, such as a quarterly review.
  5. Frame the whole document as a draft for team discussion, not a final mandate.

Output format — A working agreement document with short sections per topic, each with one to three concrete rules, plus a "review cadence" line at the end. Collaborative tone, written to be discussed and edited by the team, not imposed.

Guardrails — Do not invent team preferences that aren't in team_input; where none was gathered, mark the draft rule as "proposed — confirm with team." Keep rules realistic for the stated team size and context.

Example — team_context: "8-person remote engineering team across 3 time zones"; pain_points: "decisions drag on in Slack threads, unclear who has final say"; topics_to_cover: "communication channels, meeting norms, decision-making, async work expectations"; team_input: "none gathered yet — first draft for discussion."