64-team-brief-global

name	64-team-brief-global
description	Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.
metadata	{"version":"1.0.1","category":"operations"}
license	MIT
triggers	["assign a task","brief for my team","team brief","1:1 brief","definition of done","meeting agenda template","marketing standup agenda","delegate work to the team"]
output	File .md — a task brief by role (writer / designer / media buyer / channel owner) or meeting notes with an agenda and action items carrying owners and deadlines
related	["product-marketing-context-global","02-campaign-brief-global","62-marketing-review-global","65-team-performance-review-global","41-campaign-asset-list-global","67-agency-vendor-brief-global"]

Team Brief and Meeting Template (Global)

A good brief means the recipient knows exactly what to make, by when, and what "done" looks like. "Make some good content" is not a brief. "Write 3 Facebook captions on the pain angle, 200 words each, submitted Wednesday before 9:00 CET" is. Thirty minutes writing a proper brief saves three hours of rework.

Information gathering

Read .agents/product-marketing-context-global.md and the current campaign brief if available. If missing, ask up to 4 questions:

1. What is the task, and which campaign or objective does it serve? Describe the deliverable concretely.
2. Who is it assigned to, and do they have capacity? What role (writer, designer, media buyer, sales)?
3. What is the real deadline? A date and a time with a timezone — "end of week" and "ASAP" are not deadlines.
4. What does "done" mean? Measurable acceptance criteria, and where the work gets submitted.

Principles

1. Deadlines carry a time and a timezone. On a distributed team, "Friday" means five different moments. Write "Friday 17:00 UTC" and let people convert.
2. Important tasks get a written brief. Do not brief verbally and then blame the maker for getting it wrong.
3. State what is NOT needed. This blocks over-delivery and scope drift.
4. Briefing is not micromanaging. Lock the output and the standard, respect how the person works.
5. Repeated misses mean the brief is broken. If the same person keeps missing, fix the brief before fixing the person.
6. Two-way confirmation. The task is not assigned until the recipient confirms they understand it and accept the deadline.

Workflow

1. Scope the task and check the recipient

Check capacity before assigning: how many tasks do they hold, and which deadline comes first? If they are overloaded, choose between moving the deadline, cutting the scope, or reassigning — do not stack work and hope they absorb it.

2. Write the brief using the role template

Pick the role template below. Every brief needs: context (why), deliverable (what), done criteria (when it is finished), references (a good example and an anti-example), and constraints (hard limits).

3. Set check-in points for complex tasks

For tasks over 3 days or with multiple deliverables, set a draft checkpoint for a mid-way review. Do not discover at the deadline that the work went in the wrong direction.

4. Assign and confirm