From agentic-office
Activate for: situation brief, bring me up to speed, prep me for, pre-meeting brief, decision brief, context brief, catch me up, quick brief, what do I need to know before, background on, what's the situation with, before I call, what's the history on. NOT for: daily digest (use digest), meeting prep (use meeting-intelligence), cross-domain context injection (use context-loader).
npx claudepluginhub panaversity/agentfactory-business-plugins --plugin agentic-officeThis skill uses the workspace's default tool permissions.
Read `work.local.md` in the current working directory.
Generates tailored meeting prep docs for 1:1s, team syncs, stakeholder reviews, planning by pulling context from past meetings, decisions, action items, sprint status.
Produces private strategic meeting prep document capturing stakes, stakeholder positions, ranked outcomes, key messages, Q&A responses, risks, asks, and success signals for high-stakes meetings.
Activate for: load context, inject context, cross-domain context, context for this endeavour, relevant background, multi-domain context, what context do I need, before I work on this, context from HR, context from finance, context from ops, combine context, cross-domain brief, what should I know before starting. NOT for: situation briefs (use executive-brief), search queries (use workplace-search).
Share bugs, ideas, or general feedback.
Read work.local.md in the current working directory.
If it does not exist, tell the user to run /agentic-office:setup first.
TYPE 1: PRE-MEETING BRIEF Purpose: Everything you need to know before a specific meeting. Input: Meeting name / attendees / agenda Output: Context per agenda item; stakeholder notes; decisions needed; prior meeting summary
TYPE 2: PRE-DECISION BRIEF Purpose: All relevant context before making a specific decision. Input: Decision to be made; who is affected; constraints Output: Decision context; options; relevant precedents; stakeholder positions
TYPE 3: PERSON BRIEF Purpose: Quick profile of someone you are about to interact with. Input: Person name Output: Role; current focus; communication style; today's context; approach tips
TYPE 4: PROJECT BRIEF Purpose: Current status of a project you need to speak about. Input: Project name Output: Status; current milestone; risks; decisions made; key contacts
TYPE 5: TOPIC BRIEF Purpose: Everything in workplace memory relevant to a topic. Input: Topic name Output: What is known across all memory layers; relevant decisions; open questions
OUTPUT STRUCTURE:
SITUATION BRIEF — [Subject]
Prepared: [Date/Time] | For: [Name from work.local.md]
================================================================
THE SITUATION IN ONE SENTENCE:
[Most important thing to know — written as a colleague would say it]
CONTEXT:
[Background — what led to this; relevant history; decisions already made]
WHAT YOU NEED TO KNOW NOW:
[Current status; what is live; what has changed recently]
THE KEY QUESTION:
[The one thing that needs resolving — decision / answer / commitment]
STAKEHOLDER POSITIONS (if relevant):
[Person]: [Their likely position; what they need; how to approach]
RISKS:
[What could go wrong in this conversation / decision]
YOUR RECOMMENDED APPROACH:
[Specific guidance — not generic; based on work.local.md context]
================================================================
QUICK BRIEF (< 5 minutes to read): Use for: routine meetings; familiar topics; regular stakeholders Length: 3-4 short sections; bullet points acceptable
FULL BRIEF (5-15 minutes to read): Use for: high-stakes meetings; new stakeholders; complex decisions Length: All sections; narrative where context is nuanced