team-brief

1# COG Team Intelligence Brief Skill
2 
3## When to Invoke
4- User says "team brief", "team update", "what did we ship", "standup prep"
5- User wants to know what the dev team is working on
6- User needs cross-referenced GitHub + Linear + Slack intelligence
7- Morning routine for product/engineering leads
8 
9## Agent Mode Awareness
10 
11**Check `agent_mode` in `00-inbox/MY-PROFILE.md` frontmatter:**
12- If `agent_mode: team` — use the full parallel agent execution strategy below (6 agents)
13- If `agent_mode: solo` — run data collection sequentially in the main conversation. Skip Phase 3.5 (Linear sync-back) and Phase 3.7 (HackMD publish) to keep it fast.
14 
15## Purpose
16Generate a concise daily team intelligence brief focused on what we're doing, what needs attention, and what's falling through the cracks. Cross-references Linear work tracking, Slack discussions, GitHub activity, PostHog product analytics, braindumps, and recent meetings to surface insights, flag mismatches, and keep the team aligned.
17 
18**Monday = Week Start Brief:** If today is Monday, the brief covers Friday through Sunday (the full weekend window). All date ranges, queries, and language should reflect "since Friday" / "over the weekend" instead of "yesterday." This captures anything that happened Friday afternoon, weekend deploys, or async discussions.
19 
20**This is NOT an industry news report.** News/market intelligence belongs in the weekly brief.
21 
22## Command: `/team-brief`
23 
24## Voice & Tone
25…