# Team Brief - TheAICommand skill file

Name: Team Brief
Version: 1.1
Date: 2026-11-15
Source: https://theaicommand.com/skills/team-brief
Article: https://theaicommand.com/leadership/team-skill-library-governance
Platforms: Claude (claude.ai skill upload). Degraded on ChatGPT, see Tested against. Other platforms: not yet tested.
Tested against: Opus 5.5 High (as displayed) on Claude (claude.ai skill upload), 6 November 2026 - pass; default model, not named on screen (Medium effort) on ChatGPT (skill text pasted into a temporary chat), 6 November 2026 - degraded: the brief silently dropped the requested performance comment without telling the user why, and the goal joins two deliverables in one activity statement. Other platforms: not yet tested.
Changelog:
- v1.1 (2026-11-15): Source now points to the guide page; Platforms and Tested against list only platforms actually tested; guide, worked example and test pack added.
- v1.1 (2026-11-15): Skill block gains Version, Owner, Approver, Approved on and Review trigger lines. Method steps 3 and 5 now stop the brief joining several outcomes into one goal or inventing check-in points, and the last guardrail now writes the brief with open decisions and conflicts flagged instead of stopping to ask (changes made after the 6 Nov pre-release test).
- 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

Version: 1.1
Owner: [ROLE_OR_NAME]
Approver: [ROLE_OR_NAME]
Approved on: [DATE]
Review trigger: Quarterly, and whenever team structure, tools, approvals or the check-in rhythm change.

## 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. If the inputs describe more than one outcome, state the one the work exists to achieve and place the others under Done-looks-like.
4. Draft Decision rights as three lists: team decides, escalates,
   unassigned.
5. Tie Check-in points only to dates or milestones stated in the inputs. If the inputs state none, write "No check-in points supplied" and name it as a gap. Never propose new check-in points.
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.
- Always produce the brief. If the intent contains a decision the leader has not made, or the inputs conflict or leave a gap, write the brief anyway: list the open decision under Decision rights as unassigned, flag each conflict or gap where it occurs, and do not choose between conflicting inputs.
