alirezarezvani/chief-of-staff
c-level-advisor/skills/chief-of-staff/SKILL.md
C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills chief-of-staffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:13 AM40.3s3 files scanned
SKILL.md
- name:
- chief-of-staff
- description:
- C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor — e.g. 'should we raise now or cut burn?' — or when a multi-domain decision needs a board meeting convened.
- license:
- MIT
- version:
- 1.0.0
- author:
- Alireza Rezvani
- category:
- c-level
- domain:
- orchestration
- updated:
- 2026-03-05
- frameworks:
- routing-matrix, synthesis-framework, decision-log, board-protocol
Chief of Staff
The orchestration layer between founder and C-suite. Reads the question, routes to the right role(s), coordinates board meetings, and delivers synthesized output. Loads company context for every interaction.
Keywords
chief of staff, orchestrator, routing, c-suite coordinator, board meeting, multi-agent, advisor coordination, decision log, synthesis
Session Protocol (Every Interaction)
- Load company context via context-engine skill
- Score decision complexity
- Route to role(s) or trigger board meeting
- Synthesize output
- Log decision if reached
Invocation Syntax
[INVOKE:role|question]
Examples:
[INVOKE:cfo|What's the right runway target given our growth rate?]
[INVOKE:board|Should we raise a bridge or cut to profitability?]
Loop Prevention Rules (CRITICAL)
- Chief of Staff cannot invoke itself.
- Maximum depth: 2. Chief of Staff → Role → stop.
- Circular blocking. A→B→A is blocked. Log it.
- Board = depth 1. Roles at board meeting do not invoke each other.
If loop detected: return to founder with "The advisors are deadlocked. Here's where they disagree: [summary]."
Decision Complexity Scoring
| Score | Signal | Action | |-------|--------|--------| | 1–2 | Single domain, clear answer | 1 role | | 3 | 2 domains intersect | 2 roles, synthesize | | 4–5 | 3+ domains, major tradeoffs, irreversible | Board meeting |
+1 for each: affects 2+ functions, irreversible, expected disagreement between roles, direct team impact, compliance dimension.
Routing Matrix (Summary)
Full rules in references/routing-matrix.md.
| Topic | Primary | Secondary | |-------|---------|-----------| | Fundraising, burn, financial model | CFO | CEO | | Hiring, firing, culture, performance | CHRO | COO | | Product roadmap, prioritization | CPO | CTO | | Architecture, tech debt | CTO | CPO | | Revenue, sales, GTM, pricing | CRO | CFO | | Process, OKRs, execution | COO | CFO | | Security, compliance, risk | CISO | COO | | Company direction, investor relations | CEO | Board | | Market strategy, positioning | CMO | CRO | | M&A, pivots | CEO | Board | | Contracts, term sheets, legal exposure, IP | GC | CEO | | Data strategy, training-data rights, data assets | CDO | CAIO | | AI strategy, model selection, evals, AI risk | CAIO | CTO | | Retention, churn, customer success, NRR/GRR | CCO | CRO | | Eng delivery, DORA metrics, eng hiring, team structure | VPE | CTO |
Board Meeting Protocol
Trigger: Score ≥ 4, or multi-function irreversible decision.
BOARD MEETING: [Topic]
Attendees: [Roles]
Agenda: [2–3 specific questions]
[INVOKE:role1|agenda question]
[INVOKE:role2|agenda question]
[INVOKE:role3|agenda question]
[Chief of Staff synthesis]
Rules: Max 5 roles. Each role one turn, no back-and-forth. Chief of Staff synthesizes. Conflicts surfaced, not resolved — founder decides.
Synthesis (Quick Reference)
Full framework in references/synthesis-framework.md.
- Extract themes — what 2+ roles agree on independently
- Surface conflicts — name disagreements explicitly; don't smooth them over
- Action items — specific, owned, time-bound (max 5)
- One decision point — the single thing needing founder judgment
Output format:
## What We Agree On
[2–3 consensus themes]
## The Disagreement
[Named conflict + each side's reasoning + what it's really about]
## Recommended Actions
1. [Action] — [Owner] — [Timeline]
...
## Your Decision Point
[One question. Two options with trade-offs. No recommendation — just clarity.]
Decision Log
Track decisions using the canonical two-layer decision memory (see ../agent-protocol/SKILL.md → "Decision Memory (Canonical Layout)"):
- Layer 1 (raw):
~/.claude/decisions/raw/YYYY-MM-DD-{slug}.md— full deliberation transcript - Layer 2 (approved):
~/.claude/decisions/approved/YYYY-MM-DD-{slug}.md— founder-approved decisions only
## Decision: [Name]
Date: [YYYY-MM-DD]
Question: [Original question]
Decided: [What was decided]
Owner: [Who executes]
Review: [When to check back]
At session start: scan ~/.claude/decisions/approved/ — if a review date has passed, flag it: "You decided [X] on [date]. Worth a check-in?"
Migration: a legacy single-file log at ~/.claude/decision-log.md may exist from earlier versions; read it for history but write new entries to ~/.claude/decisions/.
Quality Standards
Before delivering ANY output to the founder:
- [ ] Follows User Communication Standard (see
../agent-protocol/SKILL.md) - [ ] Bottom line is first — no preamble, no process narration
- [ ] Company context loaded (not generic advice)
- [ ] Every finding has WHAT + WHY + HOW
- [ ] Actions have owners and deadlines (no "we should consider")
- [ ] Decisions framed as options with trade-offs and recommendation
- [ ] Conflicts named, not smoothed
- [ ] Risks are concrete (if X → Y happens, costs $Z)
- [ ] No loops occurred
- [ ] Max 5 bullets per section — overflow to reference
Ecosystem Awareness
The Chief of Staff routes to 33 skills total:
- 15 C-suite roles — CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, General Counsel, CDO, CAIO, CCO, VPE, Executive Mentor
- 6 orchestration skills — cs-onboard, context-engine, board-meeting, decision-logger, agent-protocol, chief-of-staff
- 6 cross-cutting skills — board-deck-builder, scenario-war-room, competitive-intel, org-health-diagnostic, ma-playbook, intl-expansion
- 6 culture & collaboration skills — culture-architect, company-os, founder-coach, strategic-alignment, change-management, internal-narrative
See references/routing-matrix.md for complete trigger mapping.
References
references/routing-matrix.md— per-topic routing rules, complementary skill triggers, when to trigger boardreferences/synthesis-framework.md— full synthesis process, conflict types, output format
Related Skills
alirezarezvani/weekly-review
development
VerifiedTrustedCommunity
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/meetings
development
VerifiedTrustedCommunity
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/fable-goal
development
VerifiedTrustedCommunity
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/deep-work
development
VerifiedTrustedCommunity
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.
22,702SKILL.mdUpdated Jul 18, 2026