outcome-definition
Skill33 starsChanged 9 months agoMITView on GitHub
Shifts thinking from feature delivery to measurable user or business outcomes. Use before building a feature, during roadmap planning, or while defining success metrics to ensure work ties to real results.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before building a feature
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Outcome 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.
In this repository14 other files it gives its agents.
- assumption-mapperSkill
- experiment-designSkill
- feature-adoption-analyzerSkill
- jtbd-extractorSkill
- launch-readinessSkill
- post-launch-learningSkill
- prd-criticSkill
- problem-claritySkill
- retention-drop-diagnoserSkill
- roadmap-reality-checkerSkill
- stakeholder-alignment-checkerSkill
- tradeoff-articulatorSkill
- user-segment-prioritizerSkill
- value-vs-effortSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.