Before the PRD is finalized. Use this to turn vague success metrics into measurable, trackable targets.
When NOT to use
Do not use if you don't have access to current baseline data. Baseline is critical; if you can't measure it now, the metric is not valid.
Instructions
Read the PRD's success metrics section.
For each metric, define:
Baseline: Where is this metric right now? (e.g., "Avg onboarding time is currently 45 min")
Target: Where do you want it after the feature ships? (e.g., "Reduce to 30 min by end of quarter")
Measurement plan: How will you track it? (e.g., "Track via analytics event 'onboarding_complete' + timestamp")
Confidence: How certain are you this change is caused by your feature, not external factors? (0–100%)
Check for SMART criteria:
Specific: "Increase DAU" is vague; "increase DAU from 50k to 56k" is specific.
Measurable: defined baseline + target + measurement method.
Achievable: is a 12% lift realistic given industry benchmarks?
Relevant: does this metric tie to business outcome (revenue, retention, NPS)?
Time-bound: by when should the target be achieved?
Flag any metrics that can't be measured or don't have a baseline.
Output Format
# Success Metrics — [Feature Name]
## Validated Metrics
**Metric 1: [Name]**
- Baseline: [current value + date] | Target: [goal value] | Timeline: [by when]
- Measurement plan: [how we measure; tool/event/report]
- Confidence: [0–100]% that feature causes this change
- SMART check: ✓ (Specific, Measurable, Achievable, Relevant, Time-bound)
---
**Metric 2: [Name]**
- Baseline: [current value] | Target: [goal] | Timeline: [by when]
- Measurement plan: [method]
- Confidence: [0–100]%
- SMART check: ✓
---
## Flagged Metrics (Needs Definition)
**Original:** "Improve user satisfaction"
**Issue:** Vague; no baseline or measurement plan
**Suggested:** "Increase NPS from [current score] to [target score] as measured by [survey frequency]"
---
## Summary
[X] metrics approved | [Y] metrics flagged for revision
Overall readiness: [Ready to launch / Needs refinement]
1---2name: success-metrics-definer3description: Success Metrics Definer4---56# Success Metrics Definer78## When to activate9Before the PRD is finalized. Use this to turn vague success metrics into measurable, trackable targets.1011## When NOT to use12Do not use if you don't have access to current baseline data. Baseline is critical; if you can't measure it now, the metric is not valid.1314## Instructions15161. Read the PRD's success metrics section.172. For each metric, define:18 - **Baseline:** Where is this metric right now? (e.g., "Avg onboarding time is currently 45 min")19 - **Target:** Where do you want it after the feature ships? (e.g., "Reduce to 30 min by end of quarter")20 - **Measurement plan:** How will you track it? (e.g., "Track via analytics event 'onboarding_complete' + timestamp")21 - **Confidence:** How certain are you this change is caused by your feature, not external factors? (0–100%)223. Check for SMART criteria:23 - Specific: "Increase DAU" is vague; "increase DAU from 50k to 56k" is specific.24 - Measurable: defined baseline + target + measurement method.25 - Achievable: is a 12% lift realistic given industry benchmarks?26 - Relevant: does this metric tie to business outcome (revenue, retention, NPS)?27 - Time-bound: by when should the target be achieved?284. Flag any metrics that can't be measured or don't have a baseline.2930## Output Format3132```33# Success Metrics — [Feature Name]3435## Validated Metrics3637**Metric 1: [Name]**38- Baseline: [current value + date] | Target: [goal value] | Timeline: [by when]39- Measurement plan: [how we measure; tool/event/report]40- Confidence: [0–100]% that feature causes this change41- SMART check: ✓ (Specific, Measurable, Achievable, Relevant, Time-bound)4243---4445**Metric 2: [Name]**46- Baseline: [current value] | Target: [goal] | Timeline: [by when]47- Measurement plan: [method]48- Confidence: [0–100]%49- SMART check: ✓5051---5253## Flagged Metrics (Needs Definition)5455**Original:** "Improve user satisfaction"56**Issue:** Vague; no baseline or measurement plan57**Suggested:** "Increase NPS from [current score] to [target score] as measured by [survey frequency]"5859---6061## Summary62[X] metrics approved | [Y] metrics flagged for revision63Overall readiness: [Ready to launch / Needs refinement]64```6566---
Run npx skillmds@latest add uitbreidenos/success-metrics-definer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Success Metrics Definer It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.