About outcome-definition
A planning skill for product teams that turns feature discussions into measurable user or business outcomes. It structures success around a behavior change, baseline, target, metric, and timeframe.
Key features
- 01Define desired behavior change
- 02Choose a measurable success metric
- 03Record baseline and target
- 04Set an evaluation timeframe
- 05Specify how success is measured
Use cases
- 01Evaluate a proposed feature before development
- 02Structure roadmap planning
- 03Define success criteria for an initiative
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/outcome-definitionin Claude Code to confirm it loaded.
Bundled filesreferences/example.md
Details
From the project READMEOutcome Definition Framework
Purpose
Shift thinking from feature delivery to measurable user or business outcomes.
When to Use
- Before building a feature
- During roadmap planning
- While defining success metrics
Steps
- Define the desired user behavior change.
- Select a measurable success metric.
- Establish the current baseline.
- Set a realistic target improvement.
- Define the evaluation timeframe.
Output
Desired Outcome
Success Metric
Baseline
Target
Timeframe
How Success Will Be Measured
References
See worked example for a complete scenario.
Comments
Markdown supported