brief

---
name: brief
description: Use when framing a strategic decision before boardroom deliberation. Outputs one-page brief with context, options (min 2), assumptions, constraints, affected roles, success/kill criteria.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# /cs:brief — One-page strategy brief

Turns intake (raw question or office-hours output) into a one-page strategy brief the boardroom can deliberate on. This is **Step 1** of the strategic sprint pipeline.

## Inputs

- A topic string, or
- An office-hours brief (preferred—more rigor)
- Company context (loaded automatically)

## Output structure

```markdown
# Strategy brief: <topic>
**Date:** YYYY-MM-DD  
**Author:** chief-of-staff  
**Status:** DRAFT | UNDER REVIEW | APPROVED | RETIRED

## Context
[1–2 paragraphs: where the company sits today on this topic—pulled from company context]

## Question
[The one sentence the boardroom must answer]

## Options
1. **Option A:** <name> — <one-sentence summary>
2. **Option B:** <name> — <one-sentence summary>
3. **Option C:** <name> — <one-sentence summary>

(Minimum 2 options. "Do nothing" is always an option.)

## Assumptions
- <assumption 1—explicit>
- <assumption 2>
- <assumption 3>

## Constraints
- Time: <by when must this decide>
- Money: <budget envelope>
- People: <who can/can't be reallocated>
- Reversibility: <one-way door | two-way door>

## Affected roles
Checkboxes for which C-suite advisors should weigh in.
- [ ] CEO
- [ ] CFO
- [ ] CMO
- [ ] CRO
- [ ] CPO
- [ ] CTO
- [ ] COO
- [ ] CHRO
- [ ] CISO
- [ ] GC
- [ ] CDO
- [ ] CAIO
- [ ] CCO
- [ ] VPE

## Success criteria
[Measurable outcomes that define success—set BEFORE the decision]
- <metric 1, threshold, timeframe>
- <metric 2, threshold, timeframe>

## Kill criteria
[What signal would tell you in 90 days this was wrong]
- <metric, threshold, action if missed>
```

## Workflow

1. Load company context
2. If input is office-hours output, parse the 6 answers
3. If input is raw topic, prompt for missing pieces
4. Draft 2–3 options (never just one—every brief needs a counterfactual)
5. Make assumptions and constraints explicit
6. Identify affected roles → drives panel composition for `/cs:boardroom`
7. Write success + kill criteria BEFORE the decision (the rigor moment)
8. Save to `briefs/`

## Why this step exists

The biggest decision-making failure is debating implementation before agreeing on the question. The brief locks the question, options, and success criteria so the boardroom can deliberate without scope creep. This is also the **artifact handoff**—the next command consumes this file.