outcome-thinking
Skill4 starsChanged 8 months agoLicence not identifiedView on GitHub
Focus product work on outcomes rather than output. Covers defining success, connecting features to results, and knowing the difference between shipping and impact. Use when the team ships lots of features but metrics don't move, when success is defined by delivery dates, or when nobody can say what a feature accomplished.
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 18 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
In this repository72 other files it gives its agents.
- cross-functional-alignmentSkill
- influencing-without-authoritySkill
- managing-upSkill
- working-with-designSkill
- working-with-engineeringSkill
- working-with-gtmSkill
- changelog-voiceSkill
- conversion-copySkill
- microcopySkill
- product-narrativeSkill
- competitive-battlecardSkill
- feature-gap-analysisSkill
- switching-cost-evaluationSkill
- cta-patternsSkill
- form-optimizationSkill
- landing-structureSkill
- pricing-pageSkill
- trust-signalsSkill
- feedback-synthesisSkill
- problem-articulationSkill
- user-research-integrationSkill
- communicating-decisionsSkill
- data-informed-decisionsSkill
- decision-frameworksSkill
- launch-planningSkill
- risk-managementSkill
- sprint-delivery-managementSkill
- empty-statesSkill
- error-recoverySkill
- notification-designSkill
- onboarding-flowSkill
- settings-architectureSkill
- launch-checklistSkill
- referral-mechanicsSkill
- retention-patternsSkill
- value-metricsSkill
- business-acumenSkill
- metrics-measurementSkill
- backlog-managementSkill
- prioritization-frameworksSkill
- time-energy-managementSkill
- prd-writingSkill
- presentation-storytellingSkill
- stakeholder-updatesSkill
- competitive-positioningSkill
- north-star-settingSkill
- roadmap-planningSkill
- freemium-vs-paid-gateSkill
- packaging-strategySkill
- pricing-page-teardownSkill
- willingness-to-paySkill
- opportunity-sizingSkill
- prioritization-frameworksSkill
- roadmap-planningSkill
- feature-adoption-diagnosisSkill
- funnel-drop-off-diagnosisSkill
- metric-interpretationSkill
- quality-judgmentSkill
- trade-off-evaluationSkill
- ux-intuitionSkill
- The first 60 shown.
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.