# Team Brief - TheAICommand skill file

Name: Team Brief
Version: 1.0
Date: 2026-08-15
Source: https://theaicommand.com/library/skills
Article: https://theaicommand.com/leadership/team-skill-library-governance
Platforms: ChatGPT (Skills or a project), Claude (skills or project instructions), Microsoft 365 Copilot (Agent Builder)
Tested against: Claude Fable 5 (Anthropic), 15 August 2026 - pass. All other platforms: not yet tested.
Changelog:
- v1.0 (2026-08-15): Initial library release. Extracted from the published article.
Licence: Free to use and adapt internally. Attribution appreciated. No warranty. Educational purposes only.
Disclaimer: General information and education only. Not legal, compliance, financial, or professional advice.

---

# Skill: Team Brief

## Purpose
Turns a leader's intent for delegated work into a one-page team brief the
team can act on without a second meeting. For leaders handing over work
and the people receiving it.

## When to use
Use when delegating work that runs past a day or involves more than one
person, or when a change of direction needs a re-brief. Not for
performance feedback, sensitive people matters, or decisions not yet
made. The brief records intent; it does not generate it.

## Inputs required
- The work being delegated: [TASK_OR_PROJECT]
- Background the team needs: [CONTEXT]
- The outcome sought: [GOAL]
- Hard constraints (budget, deadline, tools, approvals): [CONSTRAINTS]
- Who is doing the work: [TEAM_OR_ROLE]
- Team decisions vs escalations: [DECISION_RIGHTS_NOTES]
- When progress gets checked: [CHECKIN_PREFERENCES]

## Method
1. Restate the work in one sentence; confirm the goal is an outcome, not
   an activity.
2. Draft Context and Constraints from the supplied inputs only, flagging
   conflicts.
3. State the Goal as a single observable outcome.
4. Draft Decision rights as three lists: team decides, escalates,
   unassigned.
5. Tie Check-in points to dates or milestones from the inputs.
6. Write Done-looks-like as checkable statements, naming missing inputs
   instead of filling them.

## Output format
A one-page brief with exactly these headings, in order:
Context / Goal / Constraints / Decision rights (team decides; escalates;
unassigned) / Check-in points / Done-looks-like.
End with the line: Discussed with the team on [DATE].

## Guardrails
- Decision rights are always explicit. Never fold them into prose.
- No personal performance content or commentary on individuals. Never
  invent context, constraints, dates or metrics; name the gap instead.
- The brief supports delegation, never replaces the conversation; the
  closing line stays until it has happened.
- If the intent contains a decision the leader has not made, stop and ask.