name: alfred-team-briefings description: > [Alfred] Align team to 100% productivity. Synthesize all signals, track continuity from previous briefings, draft update for Master approval. Soft dependency on cowork — run after a cowork session for fresh data. Use when: "send team briefing", "brief the team", "team email", "align the team". allowed-tools: Read, Write, Edit, Glob, Grep, Bash(git:), Task, mcp__claude-in-chrome__

Alfred Team Briefings

Goal: Align the entire team to 100% productivity.

The briefing email is the output, not the goal. The goal is ensuring every team member has clarity on their priorities, blockers are surfaced, and nothing falls through the cracks.

Dependency

Soft dependency on cowork session.

Typical workflow:

Cowork → Master & Alfred collaborate → Insights accumulate → Team briefings

This skill reads from today's triage outputs and cowork log. If cowork hasn't run today, data may be stale.

Scorecard

Process

Step 1: Load Intelligence

Read silently:

1. agents/agent-alfred/context/TEAM.md — Team roster
2. agents/agent-alfred/outputs/*-cowork.md (today) — Session insights
3. agents/agent-alfred/outputs/*-triage.md (today) — All channel triages (email, WhatsApp, FB, LinkedIn, iMessage, etc.)

If no cowork output exists for today, warn Master that data may be stale.

Step 2: Build Team Status from Email Thread (Source of Truth)

The email thread IS the memory system. Not markdown files. The briefing email threads contain all assignments, replies, updates, and Master's notes.

Find and Read Email Thread History

1. Search Gmail for previous briefings:

   • Search: subject:"Worca Team Briefings" from:me
   • Find the most recent briefing thread
   • Read the ENTIRE thread — all replies from team AND Master
   • Look for "--- STEVEN ADDS ---" sections in Master's replies

2. Extract ALL items from the thread:

   • Every task assigned in previous briefings
   • Every update/reply from team members
   • Every note Master added via reply (often contains new tasks or delegation updates)
   • Nothing gets lost — if it's in the thread, it's tracked

3. Determine item states:

Key rule: "Will do" ≠ Resolved. Only specific outcomes resolve items:

• ✅ "Done", "Sent", "Invoice revised", "Meeting scheduled for Tuesday"
• ❌ "Will do", "On it", "I'll handle it", "Working on this"

Build Status Table

For each team member, extract from the email thread:

Supplement with Today's Intelligence

After reading the email thread, layer in fresh data:

• Today's triage outputs (new items to assign)
• Cowork session notes (verbal updates, decisions)
• WhatsApp/Messenger (informal confirmations)

Step 3: Log Draft

Log first, then present. This allows feedback collection during cowork or independent sessions before finalizing.

Write to: agents/agent-alfred/outputs/YYYY-MM-DD-HHmm-team-briefings.md

# Team Briefings — YYYY-MM-DD HH:mm

**Status:** Draft (pending approval)
**Recipients:** [names]

## Continuity Check

### From Previous Briefing (YYYY-MM-DD)
| Person | Assigned | Their Reply | Current Status |
|--------|----------|-------------|----------------|
| Name | Task | What they said | Resolved/Pending/Blocked |

### Stale Items (3+ days)
| Person | Item | Days Old | Last Update |
|--------|------|----------|-------------|
| Name | Task | N days | Last status |

## Draft Email

[Email content here]

## Master Feedback

> [Fill after review]

## Changes Made

| Feedback | Action |
|----------|--------|
| [What Master said] | [How it was incorporated] |

Step 4: Present Draft

Show Master:

1. Continuity summary — What was assigned, who replied, what's still open
2. Stale items — Anything 3+ days without update
3. The email draft
4. Recipients list
5. Missing team members — No updates = skip or include?

Ask: "Ready to send, or any changes?"

Step 5: Incorporate Feedback

If Master provides feedback:

1. Update the draft in the logged file
2. Record feedback in "Changes Made" table
3. Present revised draft
4. Repeat until approved

Step 6: Send

After Master approval:

1. Open Gmail (steven@worca.io)
2. Compose → To: team members with updates
3. Subject: Team Daily Briefing - YYYY-MM-DD
4. Paste body
5. Confirm with Master before clicking Send
6. Send
7. Update log file: Status: Sent

Email Template

Use plain text format — no markdown tables (Gmail doesn't render them).

Subject: YYYY-MM-DD Worca Team Briefings

Hi team,

Quick sync to start the week.

=== HOW TO REPLY ===
- Reply-all with your name header (--- YOURNAME ---)
- For each item: [DONE], [IN PROGRESS], or [BLOCKED]
- Add new items you're working on
- Keep thread clean — one reply per person per briefing

=== OPEN ITEMS ===
Items still tracked from previous briefings:

- Alvin: [Item from last briefing] [STATUS]
- Alec: [Item from last briefing] [STATUS]

=== TODAY'S UPDATES ===

--- ALVIN ---
- Item 1 — context
- Item 2 — context
Action: [Specific action needed]

--- ALEC ---
- Item 1 — context
- Item 2 — context

--- IVAN ---
- Item 1 — context

--- LINDA ---
- Item 1 — context

--- LYDIA ---
- Item 1 — context

--- WILSON ---
- Item 1 — context

Steven

Reply Format (for team members)

Team members should reply with:

--- YOURNAME ---
- Item 1 [DONE] — outcome achieved
- Item 2 [IN PROGRESS] — current status
- Item 3 [BLOCKED] — what's blocking
- New item I'm working on [NEW]

Status markers:

Master Reply-Add Format

When Master adds tasks via reply to the thread:

--- STEVEN ADDS ---

@Alvin:
- INV-1995 Tactic Growth — revise invoice for Mae Faith credit [NEW]

@Linda:
- TSMC AZ contact — prioritize this week [PRIORITY]

@All:
- Reminder: Semiconductor sourcing is #1 priority

Alfred must scan for "--- STEVEN ADDS ---" in thread replies and capture all items.

Parsing Team Replies

When reading the email thread, Alfred extracts status from replies:

Key rule: Absence of explicit [DONE] = still tracked.

Anti-Patterns

Success Criteria

• Search Gmail for previous briefing threads
• Read ENTIRE thread — all team replies AND Master replies
• Extract every task/item from thread history
• Zero items lost from previous threads
• Identify stale items (3+ days)
• Build continuity: assigned → replied → current status
• Draft logged before presenting
• Every team member accounted for
• Draft reviewed by Master
• Feedback incorporated
• Sent only after explicit approval
• Final status updated in log