Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From product-management
Measure what matters: define a North Star metric that captures delivered value, decompose it into 3-5 movable input metrics, distinguish vanity (cumulative totals) from actionable (rates/cohorts/retention), set guardrails, and judge outcomes vs a baseline.
How this skill is triggered — by the user, by Claude, or both
Slash command
/product-management:product-metricsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One metric = value customers get; decompose into **3-5 input metrics** a team can move. Signups-while-ignoring-retention is theater.
One metric = value customers get; decompose into 3-5 input metrics a team can move. Signups-while-ignoring-retention is theater.
Cumulative totals/raw counts flatter; rates, cohorts, retention reveal. Drop metrics you can't act on.
Name what you must not harm (don't grow signups by tanking conversion).
Did the target metric move vs baseline/control? Significance -> applied-statistics. A ship that moved nothing is a learning — say so.
npx claudepluginhub mcorbett51090/ravenclaude --plugin product-managementGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.