brief

Original：🇺🇸 English

Translated

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

3installs

Sourcealirezarezvani/claude-skills

Added on2026-05-14

NPX Install

npx skill4agent add alirezarezvani/claude-skills brief

SKILL.md Content

View Translation Comparison →

/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:

markdown

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