Engineering Blueprint

Claude + Engineering managers lose context on... Playbook

Dan K.VP of EngineeringG2.comApril 2026

Automatically synthesize pre-1:1 context for engineering managers by aggregating recent signals from Slack, GitHub, Confluence, and Drive into a structured brief with suggested discussion topics.

1 File Included

1on1-prep-briefs-playbook.md
4 KB

What problem does this solve?

Engineering managers lose context on 6–10 direct reports as signals go stale. By 1:1 time, they're working from memory or scrambling to skim Slack for 20 minutes before calls. Relevant signals—recent PRs, active threads, Confluence pages, OKR updates—are scattered across four disconnected tools with no unified view, making 1:1s reactive and generic instead of specific and high-value.

How does it work?

Before each 1:1, provide Claude with the direct report's name. Claude queries four tools in parallel via MCPs: Slack (searches user's recent messages across public and private channels for workstreams, blockers, cross-team asks, tone); GitHub (finds recent PRs authored or reviewed, noting merge status, age, and notable comments); Confluence (surfaces pages authored or mentioned in, including design docs and proposals); Google Drive (finds owned or recently edited documents like goal docs or PDPs). Claude synthesizes all sources into a structured brief covering team context, this week's work (Slack), recent shipping (GitHub), longer-form artifacts (Confluence/Drive), and 4–5 ranked suggested 1:1 topics with specific questions and potential blockers.

What's the biggest win?

Recover 2–3 hours/week per manager across a typical 1:1 schedule. Walk into every 1:1 with exact knowledge of what the person has shipped, said, and has in flight—without manual research. Suggested topics shift from generic status checks to specific, actionable conversations (e.g., 'PR #38216 has been open since February—what's the status?'), meaningfully raising 1:1 quality while cutting prep time.

What should I know technically?

Workflow uses Slack MCP, GitHub MCP, Confluence (Atlassian MCP), and Google Drive MCP. Quality scales with tool adoption—engineers active in Slack and shipping frequently to GitHub produce rich briefs. Private Slack channel access surfaces the most candid signals. GitHub PR descriptions are particularly valuable for Claude's synthesis. Requires access to search both public and private channels for comprehensive signals.

What are the constraints?

Workflow reads visible signals, not ground truth—a quiet GitHub week could mean blocked, vacationing, doing deep design work, or in a slow sprint. Brief is a starting point, not a performance verdict. Partial picture if direct report primarily works in unconnected tools (Linear, Notion, Figma). Coverage improves as additional tool connectors become available.