Prepare decision-ready briefings from remembered people, projects, commitments, and ingested signals. Use when the user needs follow-up context, stakeholder status, or what matters now.
Installs into .claude/skills of the current project.
Are you the author of Chief Of Staff Briefing?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/borhen68-chief-of-staff-briefing)
---
name: chief-of-staff-briefing
description: "Prepare decision-ready briefings from remembered people, projects, commitments, and ingested signals. Use when the user needs follow-up context, stakeholder status, or what matters now."
metadata: { "phantom": { "emoji": "🗂️", "category": "chief-of-staff" } }
---
# Chief-of-Staff Briefing
## When to Use
- The user asks for a briefing, follow-up summary, stakeholder update, or priority scan.
- The task involves commitments, counterparties, deadlines, or project context across multiple prior signals.
- The right answer is a prioritized summary rather than a raw memory dump.
## When Not to Use
- The task is just to list stored rows without interpretation.
- There is no people/project/commitment context and a normal task answer is enough.
- The user needs full source material quoted verbatim rather than synthesized.
## Workflow
- Pull together people, projects, commitments, and recent signals into one operating picture.
- Emphasize what is due, blocked, risky, or waiting on another person.
- Prefer action-oriented output: what changed, what matters now, and what follow-up should happen next.
- Keep the briefing compact and decision-ready instead of verbose.
## References
- Use `references/briefing-template.md` when you need a stable briefing shape.
