cro-review
/cs:cro-review <plan> — Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team.
Estimated installs are a discovery signal based on public repository popularity and source completeness, not recorded Dokki installation events.
Repository
alirezarezvani/claude-skills
Pinned commit
f2bac0a8f29b
License
MIT
Execution
Instructions only
Complete source instructions
SKILL.md
/cs:cro-review — CRO Forcing Questions
Command: /cs:cro-review <plan>
The pipeline-paranoid operator pressure-tests revenue assumptions. Six questions that surface next-quarter pain this quarter.
When to Run
- Before committing to a quarterly revenue target
- Before changing sales motion (PLG ↔ sales-led, mid-market ↔ enterprise)
- Before hiring a batch of reps
- When pipeline coverage drops below 3x
- When NRR is trending down
The Six CRO Questions
1. Pipeline Coverage
What is pipeline coverage for the current quarter, by stage?
- Inbound-heavy: 3x. Outbound-heavy: 4x. Below either threshold = act now.
- Stage-weighted, not just total.
2. Win Rate Trajectory
What's win rate this quarter vs the last 4 — and what's the leak point?
- Stage-by-stage conversion.
- If a single stage softens, identify why before forecasting.
3. NRR Decomposition
What's gross retention, contraction, and expansion separately?
- NRR alone hides churn.
- A 110% NRR with 95% gross retention is different from 110% with 80%.
4. Ramp Time
For the last 4 hires, how many days to first deal and to quota?
- If ramp > 90 days at growth stage, hiring profile or enablement is broken.
- Forecasted hires must build in ramp.
5. Discount Discipline
What's the median discount this quarter vs last 4? Where is it creeping?
- Discount creep is the leading indicator of pricing or positioning weakness.
- Cap discounts by approver tier.
6. Pipeline Source Mix
What % of pipeline is marketing-sourced, sales-sourced, partner-sourced?
- If one source dominates > 80%, you have concentration risk.
- Cross-check with cs-cmo-advisor.
Workflow
python ../../../c-level-advisor/skills/cro-advisor/scripts/revenue_forecast_model.py
python ../../../c-level-advisor/skills/cro-advisor/scripts/churn_analyzer.py
Output Format
# CRO Review: <plan>
**Date:** YYYY-MM-DD
## Pipeline
- Coverage: X.Xx (target 3x+)
- Win rate: X% (4Q trend: ↑ / → / ↓)
- Top leaking stage: <name>
## Retention
- Gross retention: X%
- NRR: X%
- Expansion: X%
- Contraction: X%
## Ramp
- New hires last quarter: N
- Median days to first deal: X
- Median days to quota: X
## Discount
- Median discount this quarter: X%
- Trend vs 4Q ago: <delta>
## Source Mix
- Marketing: X% | Sales: X% | Partner: X%
## Verdict
🟢 ON PLAN | 🟡 GAP | 🔴 PIPELINE CRISIS
## Next Steps
[3 concrete actions]
Routing
/cs:cfo-review— does this hit the cash plan?/cs:cmo-review— is pipeline source-mix healthy?/cs:execute— quarterly plan if GREEN/cs:boardroom— if RED
Related
- Agent:
cs-cro-advisor - Skill:
cro-advisor - Execution:
../../../business-growth/
Version: 1.0.0
Same repository
Related Skills
agent-launcher-orchestrator
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a managed agent", "run this on a schedule", "grade my agent against a rubric", "set up a nightly worker". Reads the per-session goal (./my-agent/goal.json), routes deterministically to one of five phase sub-skills (interview → stage-launch → grade-iterate → run-without-you → wrap-up) via goal_router.py, and compiles the goal+phase into an execution shape (single-pass workflow / bounded grade→iterate loop / recurring cron deployment loop) via loop_compiler.py. Forks context so heavy intake (build sheets, payloads, eval cases) stays out of the parent thread. All launches are emitted as BYOK curl the user runs with their own key; no tool makes API calls. Inspired by anthropics/launch-your-agent (Apache-2.0). Distinct from engineering/agent-harness (generic domain loop) and engineering/write-a-skill (authors Claude Code skills, not CMAs).
View detailsagent-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.
View detailsarquiteto-de-empresa
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.
View detailsarquiteto-de-empresa
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.
View detailsboard-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
View detailsboard-meeting
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
View details