Strategy Brief Generator

/cs:brief — One-Page Strategy Brief

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline.

---
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
```

Overview

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

Manual install (npx, ZIP)

Claude Codenpx skills add alirezarezvani/claude-skills --skill brief -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \
  | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/c-level-agents/skills/brief

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/b7745647b9d065d4e01e/brief.zip" -OutFile "$env:TEMP\brief.zip"; Expand-Archive "$env:TEMP\brief.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.8 KB

Read the files here

alirezarezvani/19392f71 file

SKILL.md3.8 KB

Shared references3SKILL.md reads these from elsewhere in the repo. Not in the ZIP.

Get them on GitHub ↗

SKILL.md

Show the full text119 lines

brief/SKILL.md119 lines · 3.8 KB

PreviewCode

Outline

RawView on GitHub

/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. **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
[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

## 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 that this was the wrong call]
- <metric, threshold, action if missed>

Workflow

Load company-context.md via context-engine
If input is office-hours output, parse the 6 answers
If input is a raw topic, prompt the founder for the missing pieces
Draft 2-3 options (never just one — every brief needs a counterfactual)
Make assumptions and constraints explicit
Identify affected roles → drives panel composition for /cs:boardroom
Write success + kill criteria BEFORE the decision (this is the rigor moment)
Save to ~/.claude/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, not your memory.

Routing

/cs:boardroom <brief> — multi-role deliberation
/cs:cross-eval <brief> — multi-model sanity check before boardroom (for high-stakes)
/cs:freeze <brief> — cooldown lock for irreversible decisions

Agent: cs-chief-of-staff
Skills: context-engine, board-meeting

Version: 1.0.0

1	---
2	name: "brief"
3	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."
4	---
5
6	# /cs:brief — One-Page Strategy Brief
7
8	Command: `/cs:brief <topic>` or `/cs:brief <office-hours-output>`
9
10	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.
11
12	## Pipeline Position
13
14	```
15	/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
16	↑ you are here
17	```
18
19	## Inputs
20
21	- A topic string, or
22	- An office-hours brief (preferred — more rigor)
23	- `~/.claude/company-context.md` (loaded automatically)
24
25	## Output
26
27	A single Markdown file under `~/.claude/briefs/YYYY-MM-DD-<slug>.md` with this structure:
28
29	```markdown
30	# Strategy Brief: <topic>
31	Date: YYYY-MM-DD
32	Author: cs-chief-of-staff
33	Status: DRAFT \| UNDER REVIEW \| APPROVED \| RETIRED
34
35	## Context
36	[1-2 paragraphs: where the company sits today on this topic — pulled from company-context.md]
37
38	## Question
39	[The one sentence question the boardroom must answer]
40
41	## Options
42	1. Option A: <name> — <one-sentence summary>
43	2. Option B: <name> — <one-sentence summary>
44	3. Option C: <name> — <one-sentence summary>
45
46	(Minimum 2 options. "Do nothing" is always an option.)
47
48	## Assumptions
49	- <assumption 1 — explicit>
50	- <assumption 2>
51	- <assumption 3>
52
53	## Constraints
54	- Time: <by when must this decide>
55	- Money: <budget envelope>
56	- People: <who can / can't be reallocated>
57	- Reversibility: <one-way door \| two-way door>
58
59	## Affected Roles
60	[Which cs-* advisors should weigh in. Used to route to /cs:boardroom panel composition.]
61
62	- [ ] cs-ceo-advisor
63	- [ ] cs-cfo-advisor
64	- [ ] cs-cto-advisor
65	- [ ] cs-cmo-advisor
66	- [ ] cs-cro-advisor
67	- [ ] cs-cpo-advisor
68	- [ ] cs-coo-advisor
69	- [ ] cs-chro-advisor
70	- [ ] cs-ciso-advisor
71	- [ ] cs-general-counsel-advisor
72	- [ ] cs-cdo-advisor
73	- [ ] cs-caio-advisor
74	- [ ] cs-cco-advisor
75	- [ ] cs-vpe-advisor
76	- [ ] cs-chief-of-staff
77
78	## Success Criteria
79	[Measurable outcomes that define success — set BEFORE the decision]
80	- <metric 1, threshold, timeframe>
81	- <metric 2, threshold, timeframe>
82
83	## Kill Criteria
84	[What signal would tell you in 90 days that this was the wrong call]
85	- <metric, threshold, action if missed>
86	```
87
88	## Workflow
89
90	1. Load company-context.md via context-engine
91	2. If input is office-hours output, parse the 6 answers
92	3. If input is a raw topic, prompt the founder for the missing pieces
93	4. Draft 2-3 options (never just one — every brief needs a counterfactual)
94	5. Make assumptions and constraints explicit
95	6. Identify affected roles → drives panel composition for `/cs:boardroom`
96	7. Write success + kill criteria BEFORE the decision (this is the rigor moment)
97	8. Save to `~/.claude/briefs/`
98
99	## Why This Step Exists
100
101	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.
102
103	This is also the artifact handoff — the next command consumes this file, not your memory.
104
105	## Routing
106
107	- `/cs:boardroom <brief>` — multi-role deliberation
108	- `/cs:cross-eval <brief>` — multi-model sanity check before boardroom (for high-stakes)
109	- `/cs:freeze <brief>` — cooldown lock for irreversible decisions
110
111	## Related
112
113	- Agent: [`cs-chief-of-staff`](../../agents/cs-chief-of-staff.md)
114	- Skills: [`context-engine`](../../../c-level-advisor/skills/context-engine/SKILL.md), [`board-meeting`](../../../c-level-advisor/skills/board-meeting/SKILL.md)
115
116	---
117
118	Version: 1.0.0
119