brief

Featured

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

AI & Automation 25,834 stars 3639 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
alirezarezvani
Repository
alirezarezvani/claude-skills
Created
10 months ago
Last Updated
1 weeks ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ce-brief

Turn an ambiguous idea into an optional, approved intent brief for /core-engineering:ce-plan. Use when problem, users, scope, outcomes, or constraints need discovery; skip it when those are already clear. Records product intent only—no codebase profile, solution design, architecture selection, or decomposition.

0 Updated 1 months ago
relusion
AI & Automation Listed

create-brief

Co-author a product brief (docs/product/brief.md) with the human through a structured interview, then quality-gate it against best practices. The brief is the single human-authored input that anchors every scope / YAGNI decision the team makes — in both human and autonomous modes. It anchors the Requirement Definition interview (the Requirements Analyst reads it first and reconciles requirements against it) and, in autonomous mode, is the Product Owner's source of truth. Use when no brief exists yet, when a brief is thin or unmeasurable, or when the operator runs `/create-brief`.

17 Updated 4 days ago
sohei56
AI & Automation Listed

brief-me

Slash-invoked as `/brief-me`. The user's single trigger to receive a converged multi-model team advisory report on a decision or research topic the conversation already established. The agent assembles the brief from six required team voices (Researcher, Advisor, Kaizen 1, Kaizen 2, Linter, Builder), renders it into a single self-contained local HTML file from the shipped template, opens it on the user's screen, and the user clicks "Copy my answers" and pastes their picks back into chat. The assembling agent is never a voice in the brief.

0 Updated 4 weeks ago
MyAiFreedomSystems