CxOPack
Board
Orchestration layer

The Board

Your 5 kits stop being 5 kits. They become a team.

The Board is the orchestration layer included with the All-Access Pass. A Chief of Staff subagent (Sam) routes any request to the right executive persona; a /board:weekly ritual runs all 5 in sequence; a shared founder-log/ workspace gives them collective memory. Without the Board, you have 5 kits. With it, you have an AI executive team that remembers, hands off, and disagrees — like a real one.

#1. Review, plan, brainstorm

The Board is included with the All-Access Pass — but it only works if the kits beneath it are installed first. Before you install Board, install at least one kit and run it once end-to-end. The routing is only as smart as the personas it routes to.

Answer these first

  1. Do you have at least 2 of the 5 kits installed and have you run one skill from each?
  2. Do you have a `founder-log/` folder yet? (If not, the Board's first job is to initialize it.)
  3. What's the single decision you're stuck on right now? (That's your first /board:decision.)
  4. How often do you find yourself saying 'I don't know who to ask about this'? That's the frequency with which you'll run /founder.

Brainstorm prompts

  • If you had a real Chief of Staff sitting next to you, what's the first meeting you'd have them set up?
  • Which of your last 10 decisions were made without input from the function that mattered most? (Those are the ones to re-run via /board:decision.)
  • What's a decision you've quietly been deferring because it touches too many parts of the business? Run /board:brief on it first, then /board:decision.

#2. Connect MCPs and tools

Install these MCP servers (or their equivalent integrations) to make the The Board 10× more useful. Not all are required — pick the top 1–2 to start.

All kit-level MCPs

The Board inherits every MCP you've installed for the individual kits. It doesn't add new ones — it reads the same data through the persona agents.

Docs
File system (built-in)

The `founder-log/` shared workspace is just files in your project. Every persona reads + writes here. No external service.

Docs
Don't have MCP set up yet?
MCP is the Model Context Protocol — Anthropic's standard for letting AI tools read from your software. Install guides: Claude Code MCP setup. ChatGPT uses Actions (OpenAPI) instead of MCP — same capabilities, different protocol.

#3. Define your cadence

The The Board works because you run it consistently. Block the weekly ritual in your calendar now — even 15 minutes, non-negotiable, beats 2 hours every 3 months.

Daily

  • Morning·30 sec
    If in doubt, /founder <whatever's on your mind> instead of forcing a specific kit.

Weekly

  • Monday 09:00·20 min/board:weekly
    The cornerstone ritual. All 5 personas give a read, Chief of Staff synthesizes into one weekly brief.

Monthly

  • First Monday·30 min
    Review open handoffs in founder-log/handoffs/. Kill anything >30 days old with no movement.

Ad-hoc

  • Any big decision·20 min/board:decision
    Get each relevant exec's POV + one recommendation. Logs to decisions/ automatically.
  • Any cross-functional exploration·10 min/board:brief
    1-3 personas brief you with 'the question you haven't asked' on a topic.
  • Any time one exec needs to pass work to another·3 min/board:handoff
    Structured handoff with deadline, kill criteria, explicit deliverable.

#4. Use the skills

Every asset in the The Board — with when to trigger it, the exact step-by-step, an example in/out, and the common pitfalls. Read them once; refer back as you run the cadence.

chief-of-staffSubagent
Trigger
Invoked automatically by /founder or /board:* commands.
When to use
Any request you don't know who to route to, or any request touching multiple functions.
Step-by-step
  1. Reads the request.
  2. Reads founder-log/weekly/ for last week's context.
  3. Decides which personas to call (1 to 5). Over-consult before under-consulting.
  4. Invokes each persona in parallel or sequence with their function-specific slice.
  5. Synthesizes into one brief: by function + consolidated recommendation + proposed handoffs + the decision you need to make.
Example input
"/founder Should I raise prices from $29 to $49?"
Example output
Brief with CEO (strategic framing), CFO (model of impact), Sales (how deals respond), CMO (narrative around change). Disagreements surfaced. Single recommendation: yes, with 30-day notice and a kill criterion. 2 handoffs queued: CFO → model, CMO → rewrite pricing page.
Pitfalls
  • Asking the Chief of Staff to *execute* — it routes + synthesizes, not executes. That's the personas' job.
  • Skipping the `founder-log/` initialization — without it, personas operate without shared memory.
ceo / cto / cfo / sales-director / cmoSubagent
Trigger
Called by the Chief of Staff, or directly: 'call the ceo agent for <X>'.
When to use
Each persona is the function's voice. Talk to them like a person, not a script.
Step-by-step
  1. Each persona reads founder-log/ on invocation (priorities, metrics, recent decisions, last weekly).
  2. They use their kit's skills under the hood (CEO uses weekly-priorities, board-update, build-buy-kill, etc.).
  3. They can request handoffs to other personas if the work crosses function.
  4. They push back in their voice — CEO on 4th priorities, CFO on unsourced numbers, CMO on banned words, Sales on stale pipeline.
Example input
"Ask the CFO if we can afford to hire a designer in Q3"
Example output
CFO reads cash-flow-13w + runway-scenarios. Replies: 'At €9k/mo for the designer, Base runway drops from 11 → 8 months. Below the fundraise-prep threshold. Recommendation: delay hire OR start fundraise prep this week. Handoff to CEO: decide which.'
Pitfalls
  • Bypassing the persona and calling skills directly — works, but you lose voice consistency and cross-function awareness.
  • Running multiple personas in parallel on genuinely sequential work (e.g., CMO needs CFO's numbers first).
/board:weeklySlash command
Trigger
Type /board:weekly on Mondays.
When to use
The non-negotiable cornerstone ritual. 20 minutes.
Step-by-step
  1. Reads last week's weekly brief.
  2. Asks for 2 minutes of raw founder thoughts.
  3. Invokes all 5 personas in parallel: '3-bullet read for this week.'
  4. Synthesizes weekly brief: by-function section, cross-functional pattern, 3 locked priorities, open handoffs, one provocative question.
  5. Writes founder-log/weekly/YYYY-WW.md. Updates priorities.md.
Example input
(Monday 9am ritual)
Example output
Weekly brief across all functions. Cross-functional pattern detected: 'outbound response rate dropped same week positioning changed — causal?' 3 priorities set with kill criteria. 2 handoffs surfaced. Question: 'Is the positioning test working on new segment but breaking cold outbound?'
Pitfalls
  • Skipping the 2-min raw dump — that's where the shadow backlog lives.
  • Letting one persona's section dominate — Chief of Staff should weight evenly.
  • Not re-reading the weekly brief mid-week — it's a living document.
/board:decisionSlash command
Trigger
Type /board:decision <topic>.
When to use
Any decision big enough to warrant the full board's input — typically those costing >€500, spanning >1 week, or crossing functions.
Step-by-step
  1. Narrow the decision to a concrete choice with named options (include status quo).
  2. All relevant personas answer 4 questions: upside, downside, what must be true, one pushback.
  3. Surface disagreements — don't smooth them over.
  4. Single recommendation + kill criteria.
  5. Logs to founder-log/decisions/ via /ceo:decision-log.
Example input
"/board:decision Launch a referral program?"
Example output
Options: A) full referral program now, B) ambassador test with 5 customers, C) don't do it. CEO / CTO / CFO / Sales / CMO each with 4 answers. Disagreements: CTO says 2-week build, CMO says narrative isn't sharp yet. Recommendation: Option B (ambassador test) by <date>. Kill: if <5 referrals in 30 days, close.
Pitfalls
  • Decisions without named options — always include 'don't do it.'
  • Personas giving 'I have nothing to add' — re-prompt for the one thing they'd push back on.
  • Smoothing over disagreements.
/board:handoffSlash command
Trigger
Type /board:handoff <FROM> <TO> <task>.
When to use
After any brief where work needs to pass between executives.
Step-by-step
  1. Parse FROM and TO (both valid persona names).
  2. Write handoff file with: TASK, CONTEXT, DELIVERABLE, DUE, KILL CRITERIA.
  3. Receiving persona acknowledges (confirms understanding, names missing context, confirms deadline).
  4. Status moves: Open → Confirmed → Complete.
  5. Open handoffs past DUE surface in next /board:weekly.
Example input
"/board:handoff CEO CTO Scope the 2-week MVP for the referral feature by Friday"
Example output
Handoff file at founder-log/handoffs/2026-04-19-ceo-cto-referral-mvp.md. CTO acknowledges: 'Will use /cto:mvp-scope, need CEO\'s kill criteria for the referral program first (what defines success for the test?). Deliverable: specs/referral-mvp.md by Friday 17:00.'
Pitfalls
  • Unstructured handoffs in Slack — drift, fail silently.
  • No kill criteria — handoffs that 'complete' without a success signal are the most dangerous.
  • Ignoring open handoffs past due — they compound into dropped balls.
Your first win
Next Monday at 9am, run /board:weekly. If the synthesized brief changes one decision you were about to make, the Board has paid for itself.