/cs:cmo-review <plan> — Narrative-first interrogation of positioning, ICP, message house, and channel mix. Use when launching a campaign or repositioning, or when CAC is rising and the one-sentence positioning test fails.
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/cmo-review
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/cmo-review/SKILL.md \
-o ~/.claude/skills/cmo-review/SKILL.md Command: /cs:cmo-review <plan>
The narrative-first strategist pressure-tests positioning before debating tactics.
Name one real person in your ICP. Company, title, what they do daily, what they hate.
What job is the customer hiring this product to do, and what’s the alternative they use today?
One sentence: For [ICP], who needs [job], we are [category] that [differentiator] unlike [alternative].
Where does the customer first hear your name — and is it inbound or outbound at this stage?
Per channel: what’s CAC, what’s payback in months, and is it improving?
If a well-funded competitor copies your messaging tomorrow, what’s still yours?
python ../../../skills/cmo-advisor/scripts/marketing_budget_modeler.py
python ../../../skills/cmo-advisor/scripts/growth_model_simulator.py
# CMO Review: <plan>
**Date:** YYYY-MM-DD
## Positioning
One-sentence statement: <here>
## ICP
- Named persona: <name, title, company>
- JTBD: <one sentence in their words>
## Channel Mix
- Primary: <channel> | CAC $X | Payback Ym
- Secondary: <channel> | CAC $X | Payback Ym
## Verdict
🟢 / 🟡 / 🔴
## Next Steps
[3 concrete actions]
/cs:cro-review — pipeline contribution check/cs:cpo-review — product ↔ positioning alignment/cs:decide — log the verdictcs-cmo-advisorcmo-advisor../../../../marketing-skill/Version: 1.0.0
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment