Walk Into Every Meeting Already Oriented
You need to prepare for a meeting without scrambling through inboxes and chat threads for context on who you are meeting and what is outstanding with them.
Prerequisites
Complete Keep Track of Context Without Effort first. That guide covers knowledge base setup, agent scheduling, and the knowledge graph structure. The steps below assume your Outpost agents are running and your knowledge graph has been accumulating context from email and calendar syncs.
Check your schedule
Start by seeing what is coming up. The calendar query script reads synced events and filters by time window:
node .claude/skills/sync-apple-calendar/scripts/query.mjs --upcoming 2h
=== 2026-05-04 (today) ===
09:00-09:30 | Daily standup | Engineering Team [in 45min]
10:00-10:30 | Auth migration sync | Sarah Chen, Bob Kumar [in 105min]
2 event(s) | now: 2026-05-04T08:15:00.000Z
The --upcoming 2h flag shows meetings starting within
two hours, with a countdown. Use --today for the full
day or --tomorrow to prepare the evening before.
Look up attendees in the knowledge graph
Before generating a briefing, search the knowledge graph for each attendee. This is the step that turns a generic calendar entry into useful preparation:
rg "Sarah Chen" ~/Documents/Personal/knowledge/
People/Sarah Chen.md:3:Engineering Manager at Acme Corp
People/Sarah Chen.md:8:Last seen: standup 2026-05-02
People/Sarah Chen.md:15:- 2026-04-28: Raised concern about auth migration timeline
Projects/Auth Migration.md:12:Lead: [[Sarah Chen]]
Projects/Auth Migration.md:18:Status: blocked on identity provider contract
Topics/Platform Reliability.md:5:Raised by [[Sarah Chen]] in Q1 review
The results span entity types -- people, projects, and topics --
because the librarian agent links entities with
[[backlinks]] as it processes your email and calendar.
A single search surfaces the full picture rather than a single file.
Read the person note for the full picture:
cat ~/Documents/Personal/knowledge/People/Sarah\ Chen.md
The note contains context (role, what they focus on), a reverse-chronological interaction history, and an Open Items section with unresolved commitments -- the details that disappear from memory between meetings but determine whether someone feels heard.
Wake the concierge for a fresh briefing
The concierge agent prepares meeting briefings automatically on its schedule. If you want a briefing now rather than waiting for the next cycle, wake it on demand:
npx fit-outpost wake concierge
Waking concierge...
Synced 4 calendar events
Prepared briefing for 10:00 AM Auth migration sync
Done (5.1s)
The concierge checks for meetings within the next two hours, looks up each attendee in the knowledge graph, and assembles a briefing. If no meetings are imminent, it reports idle.
Read the daily briefing
The chief-of-staff agent compiles a broader daily briefing that includes meeting prep alongside email highlights, open threads, and action items:
npx fit-outpost wake chief-of-staff
Waking chief-of-staff...
Compiled daily briefing (14 items)
Done (7.2s)
The result is saved to
knowledge/Briefings/2026-05-04-morning.md. It includes
today's schedule (meetings marked PREPPED have
attendee context already assembled), priority actions linked to
today's meetings, and open commitments to the people you are
seeing.
Prepare for a specific meeting on demand
When you want to go deeper than the scheduled briefing, ask for meeting prep directly in your knowledge base:
cd ~/Documents/Personal && claude "prep me for my 10am meeting"
The meeting-prep skill identifies the meeting from your calendar, looks up every attendee in the knowledge graph, and produces a structured briefing with sections for each person:
Meeting Brief: Auth Migration Sync
10:00 today / Sarah Chen, Bob Kumar
About Sarah
Engineering Manager at Acme Corp. Leading the Auth Migration project
since Q4 2025. Focused on platform reliability and compliance deadlines.
Your History
- 2026-05-02: Standup -- mentioned identity provider contract unsigned
- 2026-04-28: Raised concern about auth migration timeline
Open Items
- Review staffing plan she shared 2026-04-15
Suggested Talking Points
- Identity provider contract status -- [[Auth Migration]] is blocked on this
- Staffing plan feedback -- Sarah asked 2026-04-15, still pending
Each section draws from a different part of the knowledge graph: person notes, project status, and interaction history. Talking points are specific to this meeting and these attendees, not generic templates.
For interview meetings, the briefing also surfaces candidate briefs
from knowledge/Candidates/ and pipeline status from
knowledge/Roles/.
Verify
You have reached the outcome of this guide when:
-
You can query your calendar with
--todayor--upcoming 2hand see meetings with attendee names. -
Searching the knowledge graph with
rg "name" knowledge/returns cross-referenced context about the people you are meeting. -
npx fit-outpost wake conciergeproduces a briefing for an upcoming meeting, drawing on knowledge graph data rather than generic placeholders. -
The chief-of-staff's daily briefing in
knowledge/Briefings/includes your schedule, priority actions tied to today's meetings, and open commitments to the people you are seeing.
If attendee context is thin, your knowledge graph may need more time
to accumulate data. Check that the postman and librarian agents are
running -- npx fit-outpost status -- and that email
sync is producing notes under knowledge/People/.
What's next
- Keep Track of Context Without Effort -- return to the full Outpost setup guide for agent configuration, schedule customization, and knowledge graph maintenance
- Agent Teams -- how agent skills are generated from your organization's engineering standard