Percerno Skillsbeta
← everything it can do · marketing

Brief TEXT

Generates a structured one-page strategy brief from a raw topic or office-hours intake, defining the core question, options, assumptions, constraints, and success criteria. It serves as the first step in the strategic sprint pipeline, preparing the context for boardroom deliberation.

6 uses this weeksource alirezarezvanilicence MIT
Quality gate: PASS · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift +1.5 points (specificity, structure, method, fit).
won 1/2, lift +1.5, tokens ×18.39
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Lav en strategi-brief om vores mulige ekspansion til Asien.”
“Konverter outputtet fra vores seneste office-hours session til en formel brief om prisstrategi.”
“Jeg har brug for at ramme beslutningen om at skifte CRM-leverandør. Lav en brief med muligheder og succeskriterier.”
“Create a strategy brief for our potential pivot to B2B SaaS.”
“/c-level-agents:brief Should we acquire Competitor X or build in-house?”
“I have the output from our last office hours on pricing. Turn that into a formal brief.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

strategybriefdecision-makingplanningc-levelframeworkoptionssuccess-criteria

Not for

Do not use this for executing the decision or analyzing post-decision outcomes; use /c-level-agents:execute or /c-level-agents:post-mortem instead. It is not for general brainstorming without the intent to structure a formal decision; use /c-level-agents:office-hours for initial exploration. Do not use it for operational tasks that do not require strategic framing.

Details

When it is the right choice

Use this skill when a strategic question needs to be formally framed before high-level discussion. It is appropriate when you need to lock down specific options, assumptions, and measurable success criteria for a major decision like market entry or pricing changes. It is the correct step after an office-hours intake but before convening a boardroom panel.

The full recipe the assistant reads

/c-level-agents:brief — One-Page Strategy Brief

Command: /c-level-agents:brief <topic> or /c-level-agents: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

/c-level-agents:office-hours  →  /c-level-agents:brief  →  /c-level-agents:boardroom  →  /c-level-agents:decide  →  /c-level-agents:execute  →  /c-level-agents: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 /c-level-agents: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

  1. Load company-context.md via context-engine
  2. If input is office-hours output, parse the 6 answers
  3. If input is a raw topic, prompt the founder for the 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 /c-level-agents:boardroom
  7. Write success + kill criteria BEFORE the decision (this is the rigor moment)
  8. 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

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

Related

Version: 1.0.0

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/brief, licence MIT. The upstream licence file ships inside the skill.