# TEAM-PLAYBOOK.md — How to Get the Best From Each Agent
# Gerri reads this before routing. Updated by Kitt when patterns emerge.

## Ogilvy (Copy)
- **Needs:** Clear audience + context for what this replaces. Without audience, he defaults to generic.
- **Reads:** `COPY-STANDARDS.md` before every task — remind him if the brief is for CE work.
- **Watch for:** Safe copy. If the first draft is pleasant but not memorable, push back: "This is safe. Where's the reframe?"
- **Best at:** Strategy copy, headlines, positioning language, manifestos.
- **Weakest at:** Very short social copy (tends to over-think). For tweets/social, give tight word limits.

## Tatiana (Visuals)
- **Needs:** A mood reference or style direction. Without it, she'll ask — save time by including one.
- **Watch for:** First attempts that are close but not CE-level. She iterates well — give specific feedback, not vague "try again."
- **Best at:** Image generation, visual concepts, style direction.
- **Pair with:** Jessica for layout decisions, Anton for quality review.

## Jessica (Art Direction / Layout)
- **Needs:** Content before layout. She can't design a page without knowing what goes on it.
- **Reads:** CE styleguide. Brand specs are in her DNA.
- **Watch for:** Screenshot and crop quality — she now has visual curation instinct. Hold her to VISUAL-STANDARDS.md.
- **Best at:** Layout, typography, brand systems, visual curation.
- **Weakest at:** Copy decisions — route those to Ogilvy.

## Julia (Research / Publishing)
- **Needs:** Clear research question, not open-ended exploration. "Find X about Y for Z purpose."
- **Watch for:** Scope creep. She'll go deep — set boundaries upfront.
- **Best at:** Trend research, cultural intelligence, competitive analysis, publishing.
- **Weakest at:** Needs LinkedIn/Substack creds for publishing (pending setup).

## Thibault (Dev / Engineering)
- **Needs:** Specs, not descriptions. "Build X with Y constraints" not "make something cool."
- **Watch for:** Over-engineering. If the task is simple, say so explicitly.
- **Best at:** Pages, scripts, APIs, deployment, infrastructure.
- **Pair with:** Jessica for design implementation, Anton for code review.

## Anton (Quality / Critic)
- **Needs:** The brief context — what was the goal? Without it, he reviews blind.
- **Always include:** "Original brief: [goal]. Review against: STANDARDS.md + [relevant standards file]."
- **Watch for:** Nothing — Anton watches for everything. Trust his verdicts.
- **Invoke DURING work:** After Ogilvy's first draft, after Tatiana's first visual, after Thibault's first deploy. Not just at the end.

## Common Mistakes (Don't Repeat)
- Routing copy to Tatiana or visual work to Ogilvy — stay in lanes
- Sending Anton work without the original brief — he needs context to review properly
- Letting "waiting on feedback" stall the pipeline — if feedback is late, escalate
- Passing a vague brief downstream — clarify with Kitt first

---
*Last updated: 2026-02-26*
*Updated by: Kitt*