brief

name	brief
description	/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation — e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision.

/cs:brief — One-Page Strategy Brief

Command: /cs:brief <topic> or /cs:brief <office-hours-output>

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

Pipeline Position

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                       ↑ you are here

Inputs

• A topic string, or
• An office-hours brief (preferred — more rigor)
• ~/.claude/company-context.md (loaded automatically)

Output

A single Markdown file under ~/.claude/briefs/YYYY-MM-DD-<slug>.md with this structure:

# Strategy Brief: <topic>
**Date:** YYYY-MM-DD
**Author:** cs-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.md]

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

## Options
1.   — 
   — 
   — 

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


 
 
 


 Time: 
 Money: 
 People: 
 Reversibility: 


[Which cs-* advisors should weigh in. Used to route to /cs:boardroom panel composition.]

 [ ] cs-ceo-advisor
 [ ] cs-cfo-advisor
 [ ] cs-cto-advisor
 [ ] cs-cmo-advisor
 [ ] cs-cro-advisor
 [ ] cs-cpo-advisor
 [ ] cs-coo-advisor
 [ ] cs-chro-advisor
 [ ] cs-ciso-advisor
 [ ] cs-general-counsel-advisor
 [ ] cs-cdo-advisor
 [ ] cs-caio-advisor
 [ ] cs-cco-advisor
 [ ] cs-vpe-advisor
 [ ] cs-chief-of-staff


[Measurable outcomes that define success — set BEFORE the decision]
 
 


[What signal would tell you in 90 days that this was the wrong call]