boardroom

---
name: boardroom
description: Use when a decision spans multiple C-suite domains (e.g., pricing change, funding vs. cuts). Runs 6-phase deliberation: context, isolated analysis, criticism, synthesis, founder review, logging.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# /cs:boardroom — Multi-role boardroom deliberation

Runs the 6-phase board-meeting protocol across the C-suite for a single strategy brief.

## The 6 phases

### Phase 1 — briefing
- Chief of Staff distributes brief to all advisors marked in **Affected Roles**.
- Each advisor reads company context + brief.
- No discussion yet.

### Phase 2 — independent thinking (ISOLATION)
- **Critical:** each advisor produces their position independently, without seeing others' positions.
- This prevents groupthink and surfaces dissent.
- Each writes: opening, recommendation, top 3 concerns, top 3 supports.

### Phase 3 — cross-examination
- Positions revealed simultaneously.
- Each advisor critiques the others' positions on the dimensions they own:
  - CFO critiques the math
  - CISO critiques the risk
  - CPO critiques the JTBD
  - CMO critiques the positioning
  - CRO critiques the revenue math
  - etc.

### Phase 4 — devil's advocate pass
- Adversarial agent runs `/em:challenge` on the leading option.
- Surfaces three concerns with severity ratings.

### Phase 5 — synthesis
- Chief of Staff synthesizes: which option commands majority, what are unresolved dissents.
- Produces the **board memo** with recommendation + dissent.

### Phase 6 — decision hand-off
- Memo presented to founder.
- Founder accepts, modifies, or rejects.
- Approved memo routes to `/cs:decide` for logging.

## Output: board memo

Saved to `decisions/YYYY-MM-DD-<slug>.md`:

```markdown
# Board Memo: <topic>
**Date:** YYYY-MM-DD  
**Status:** AWAITING FOUNDER DECISION | APPROVED | REJECTED

## Question
[One sentence from brief]

## Recommended option
**<Option name>** — chosen because <reasoning>

## Vote tally
| Advisor | Vote | One-Sentence reason |
|---|---|---|
| CEO | A | <reason> |
| CFO | A | <reason> |
| CTO | B | <reason> |

## Dissent
- **<dissenter>:** <unresolved concern>

## Devil's advocate concerns
1. **CRITICAL** — <concern> — Mitigation: <plan>
2. **HIGH** — <concern> — Mitigation: <plan>
3. **MEDIUM** — <concern> — Mitigation: <plan>

## Success & kill criteria
[From brief, refined by panel]

## Recommended decision path
- `/cs:decide` → log the decision
- `/cs:execute` → 90-day plan
- `/cs:cross-eval` → multi-model sanity check (optional)
- `/cs:freeze N` → cooldown lock (optional, irreversible)
```

## Why Phase 2 isolation matters

If advisors see each other's positions before forming their own, they anchor. Phase 2 isolation surfaces the dissents that sycophancy would have suppressed.

## Workflow

1. Read brief from `briefs/<file>`
2. Identify affected roles
3. Invoke each C-suite advisor independently (Phase 2)
4. Collect positions
5. Run cross-examination round (Phase 3)
6. Run adversarial challenge on leading option (Phase 4)
7. Synthesize memo (Phase 5)
8. Hand off to founder (Phase 6)