Chief Of Staff
C-suite orchestration layer.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a big strategic question and it depends on a lot of factors—your runway, your growth rate, your competitive landscape, and what the market is doing right now. You'd probably want to talk to people in different roles: someone focused on finance might have different priorities than someone running product. There are pros and cons to both raising and bootstrapping. The right answer depends on your specific situation. What's your current runway and burn rate? How fast are you growing? That would help clarify things.
FOUNDER QUESTION ROUTED → Chief of Staff convening board review (Finance, Growth, Product) BOARD SESSION OUTPUT FINANCE ADVISOR summary: • Current runway: 11 months (if burn stays flat at 85K/month) • Raise pros: 18-month runway gives you market expansion window; easier to hire • Bootstrap pros: avoid dilution; keep full control; prove unit economics first GROWTH ADVISOR summary: • MRR growing 12% month-over-month (trending well) • Market window: 18-month lead on competitor X before they scale • Raise recommendation: Needed IF you want to capture category leadership; otherwise bootstrap works PRODUCT ADVISOR summary: • Roadmap: 8-week sprint to hit "table stakes" features before fundraising makes sense • Risk: Competitor launch in Q4 may force a funding decision SYNTHESIS & DECISION GATE If you want to own the category: Raise Series A in Oct 2026 (after product milestone) If you want to own your destiny: Extend runway to 24 months, hit 30% MoM growth, then decide Nov 2026 Unanswered: Do you want exit in 5 years or long-term business? (CTO needs to weigh in) NEXT STEP: Board reconvenes after Q3 metrics close.
About this skill
name: chief-of-staff description: Use when C-suite orchestration layer.
Chief Of Staff
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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the chief-of-staff skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Chief Of Staff; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: chief-of-staff
description: Use this skill as the entry point for any founder question that needs routing to the right advisor role, or when a multi-domain decision needs a full board meeting convened.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Chief Of Staff
Acts as the C-suite orchestration layer: loads company context automatically, routes a founder's question to the right advisor role or roles, convenes multi-role board meetings for complex decisions, and tracks what was decided.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.