value-vs-effort
Skill33 starsChanged 9 months agoMITView on GitHub
Prioritizes features using structured scoring across user impact, revenue potential, strategic alignment, confidence, and engineering effort. Use when deciding which feature to build next or comparing competing priorities.
Files
Feature Value vs Effort Scorer
Purpose
Prioritize features using structured, transparent scoring.
Criteria
- User impact
- Revenue potential
- Strategic alignment
- Confidence level
- Engineering effort
Steps
- Score each criterion (1–5).
- Calculate value score vs effort score.
- Rank relative priority.
Output
Feature Name
Value Score
Effort Score
Priority
High / Medium / Low
Recommendation
Build Now / Later / Do Not Build
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
- outcome-definitionSkill
- post-launch-learningSkill
- prd-criticSkill
- problem-claritySkill
- retention-drop-diagnoserSkill
- roadmap-reality-checkerSkill
- stakeholder-alignment-checkerSkill
- tradeoff-articulatorSkill
- user-segment-prioritizerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.