From c-level-agents
/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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-agents:cro-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Command:** `/cs:cro-review <plan>`
Command: /cs:cro-review <plan>
The pipeline-paranoid operator pressure-tests revenue assumptions. Six questions that surface next-quarter pain this quarter.
What is pipeline coverage for the current quarter, by stage?
What's win rate this quarter vs the last 4 — and what's the leak point?
What's gross retention, contraction, and expansion separately?
For the last 4 hires, how many days to first deal and to quota?
What's the median discount this quarter vs last 4? Where is it creeping?
What % of pipeline is marketing-sourced, sales-sourced, partner-sourced?
python ../../../skills/cro-advisor/scripts/revenue_forecast_model.py
python ../../../skills/cro-advisor/scripts/churn_analyzer.py
# 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]
/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 REDcs-cro-advisorcro-advisor../../../../business-growth/Version: 1.0.0
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
8plugins reuse this skill
First indexed Jun 30, 2026
Showing the 6 earliest of 8 plugins
npx claudepluginhub sandeepyadav1478/claude-skills --plugin c-level-agents