Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
Install Brief
$ npx skills add alirezarezvani/claude-skills --skill brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-agents/skills/brief .claude/skills/brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .claude/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-agents/skills/brief .agents/skills/brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .agents/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-agents/skills/brief .cursor/skills/brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .cursor/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path c-level-agents/skills/brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-agents/skills/brief .gemini/skills/brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .gemini/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-agents/skills/brief .github/skills/brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .github/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-agents/skills/brief .opencode/skills/brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "brief" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/c-level-agents/skills/brief into .opencode/skills/brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
brief- GitHub stars
- 28k
- Token cost
- ~967 tokens
- SKILL.md length
- 214 words
- Files
- 1
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
- Works in 8 steps: Load company-context.md via context-engine → If input is office-hours output, parse… → If input is a raw topic, prompt the… → …
- A strategic question needs to be framed before boardroom deliberation — e.g
- SKILL.md covers Pipeline Position, Inputs, Output and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brief is an agent skill from alirezarezvani/claude-skills. /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.
Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- A strategic question needs to be framed before boardroom deliberation — e.g
- Tasks that involve Go-to-market strategy
Example prompts
- “/brief”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- 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/
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Brief loads about 967 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 214 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 214 words, ~967 tokens.
Download SKILL.mdSave it as
.claude/skills/brief/SKILL.md (or your agent's skills folder).- 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 hereInputs
- 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
Related
- Agent:
cs-chief-of-staff - Skills:
context-engine,board-meeting
Version: 1.0.0
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in c-level-agents/skills/brief of alirezarezvani/claude-skills.
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Brief this skillalirezarezvani/claude-skills | 28k | — | ~967 | Automated safety check: Pass | MIT | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Jaredrhod Marketingjaredrhod/ai-marketing-skills | 281 | — | ~584 | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Tracking Discoverjtrackingai/analytics-tracking-automation | 142 | 1 repos | ~614 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Jaredrhod Marketing
jaredrhod/ai-marketing-skills
Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.
Tracking Discover
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
Traffic Acquisition
vivy-yi/xiaohongshu-skills
A skill your agent uses when driving traffic to Xiaohongshu account from external sources, acquiring new followers beyond organic discovery, implementing multi-platform growth strategy, or scaling…
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Brief
What does Brief do?
/cs:brief <topic — Generate a one-page strategy brief from an office-hours intake. Brief is an agent skill from alirezarezvani/claude-skills. /cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.
When should I use Brief?
Brief fits situations like: A strategic question needs to be framed before boardroom deliberation — e.g; tasks that involve Go-to-market strategy.
How do I install Brief in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill brief -a claude-code`. Or copy the skill folder (c-level-agents/skills/brief in alirezarezvani/claude-skills) into .claude/skills/brief in your project. Claude Code loads it when a task matches its description.
How do I install Brief in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill brief -a codex`. Or copy the skill folder (c-level-agents/skills/brief in alirezarezvani/claude-skills) into .agents/skills/brief in your project. Codex loads it when a task matches its description.
Can I use Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/brief, .gemini/skills/brief, .github/skills/brief and .opencode/skills/brief in your project.
What does Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Brief is instructions for the agent only.
Does Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Brief use?
Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Brief use?
About 967 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Brief?
Skills that share tags, products or a category with Brief: Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars) and Jaredrhod Marketing (jaredrhod/ai-marketing-skills, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brief?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.