cmo-review

Name: cmo-review
Author: alirezarezvani/claude-skills

$npx mdskill add alirezarezvani/claude-skills/cmo-review

Conducts narrative-first CMO review to refine positioning and marketing strategy

Tests positioning, ICP, messaging, and channels before campaigns or repositioning
Uses customer data, market research, and competitive analysis
Applies six forcing questions to uncover gaps in strategy
Delivers actionable insights for marketing teams and leadership

SKILL.md

.github/skills/cmo-reviewView on GitHub ↗

---
name: "cmo-review"
description: "/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."
---

# /cs:cmo-review — CMO Forcing Questions

**Command:** `/cs:cmo-review <plan>`

The narrative-first strategist pressure-tests positioning before debating tactics.

## When to Run

- Before launching any new campaign
- Before changing positioning, tagline, or category
- Before allocating > 10% of marketing budget to a new channel
- Before a major PR moment (funding announcement, product launch)
- When pipeline contribution is declining

## The Six CMO Questions

### 1. ICP (One Real Person)
**Name one real person in your ICP. Company, title, what they do daily, what they hate.**
- Persona ≠ ICP. ICP is real.
- If you can't name one, the ICP isn't sharp enough.

### 2. JTBD
**What job is the customer hiring this product to do, and what's the alternative they use today?**
- One sentence the customer would say out loud.
- "We use spreadsheets" is a valid alternative. So is "we don't."

### 3. Positioning Statement
**One sentence: For [ICP], who needs [job], we are [category] that [differentiator] unlike [alternative].**
- This is the headline. Everything cascades.
- If it doesn't fit in one sentence, it's not positioning yet.

### 4. Distribution Channel
**Where does the customer first hear your name — and is it inbound or outbound at this stage?**
- Name the channel, intent, and the path to first contact.
- PLG, sales-led, content-led, partnership-led — pick a primary.

### 5. CAC Payback
**Per channel: what's CAC, what's payback in months, and is it improving?**
- If a channel's payback is > 18 months, it isn't a channel — it's a hobby.

### 6. Defensibility of Brand
**If a well-funded competitor copies your messaging tomorrow, what's still yours?**
- Category position, founder-market fit, customer love, distribution lock — name one.

## Workflow

1. **Run the models:**
   ```bash
   python ../../../skills/cmo-advisor/scripts/marketing_budget_modeler.py
   python ../../../skills/cmo-advisor/scripts/growth_model_simulator.py
   ```
2. **Answer the six questions** in writing.
3. **Apply the verdict:**
   - 🟢 GREEN — story is sharp, channel mix sound
   - 🟡 YELLOW — sharpen positioning before scaling
   - 🔴 RED — positioning broken; do not spend

## Output Format

```markdown
# 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]
```

## Routing

- `/cs:cro-review` — pipeline contribution check
- `/cs:cpo-review` — product ↔ positioning alignment
- `/cs:decide` — log the verdict

## Related

- Agent: [`cs-cmo-advisor`](../../agents/cs-cmo-advisor.md)
- Skill: [`cmo-advisor`](../../../skills/cmo-advisor/SKILL.md)
- Execution domain: `../../../../marketing-skill/`

---

**Version:** 1.0.0

More from alirezarezvani/claude-skills

Skill	Description
a11y-audit	Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
ab-test-setup	When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
ad-creative	When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.
adversarial-reviewer	Adversarial code review that breaks the self-review monoculture. Use when you want a genuinely critical review of recent changes, before merging a PR, or when you suspect Claude is being too agreeable about code quality. Forces perspective shifts through hostile reviewer personas that catch blind spots the author's mental model shares with the reviewer.
aeo	Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.
agent-designer	Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
agent-protocol	Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
agent-workflow-designer	Design production-grade multi-agent workflows with clear pattern choice (sequential, parallel, hierarchical), handoff contracts, failure handling, and cost/context controls. Use when architecting a multi-step agent pipeline, choosing between single-agent vs multi-agent approaches, or refactoring an LLM workflow that suffers from context bloat or unreliable handoffs.
agenthub	Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
agile-product-owner	Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.