From flywheel-pm
Design complete metrics frameworks with outcome-intermediate-leading hierarchy, activation funnels, and engagement dimensions. Use when defining how to measure product success.
npx claudepluginhub abhitsian/compound-pm-marketplace --plugin flywheel-pmThis skill uses the workspace's default tool permissions.
Provide structured guidance for designing complete, measurable metrics frameworks. Adapts to the PM's preferred hierarchy from their profile.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Provide structured guidance for designing complete, measurable metrics frameworks. Adapts to the PM's preferred hierarchy from their profile.
Outcome Metrics measure business impact:
Intermediate Metrics measure product outcomes:
Leading Metrics measure user behavior:
North Star → L1 → L2:
Business → Product → Feature:
| Stage | Definition | How to Measure |
|---|---|---|
| Setup | User has completed initial configuration and can use the product | % of users who complete setup; time to complete |
| Aha | User has experienced the core value for the first time | % of users who perform the key value action; time to Aha |
| Habit | User has developed a repeated pattern of value extraction | % of users who perform the value action [X] times in [Y] period |
| Dimension | What It Measures | Example |
|---|---|---|
| Breadth | How many features are used | Avg features used per week |
| Depth | How frequently features are used | Avg actions per week |
| Intensity | How much time/effort is invested | Avg session duration |
| Segment | Default Definition | Implications |
|---|---|---|
| Casual | 1-2 sessions per week | At risk of churn, need engagement |
| Core | 3-4 sessions per week | Healthy engagement, focus on deepening |
| Power | 5+ sessions per week | Champions, leverage for expansion |
Every optimization has a cost. Always define what might get worse:
| If Optimizing | Watch For Decline In |
|---|---|
| Adoption rate | Quality of users adopted |
| Engagement depth | Breadth of feature usage |
| Self-service rate | Satisfaction with complex cases |
| Speed to market | Code quality, tech debt |
| Revenue per user | Total addressable users |