prioritize-assumptions
Skill1 starsChanged 26 days agoMITView on GitHub
Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- yuusakuri/agent-skillsword for word, first seen Nov 1, 2026
- stefanomartiradonna/claude-skillsword for word, first seen Aug 14, 2026
- Adhamxon/claude-code-skillsword for word, first seen Jul 30, 2026
- maeng777/claude-skillsword for word, first seen Jun 19, 2026
- miovrag/claude-skillsword for word, first seen Jun 12, 2026
- skytiger6724/qwen-skillsword for word, first seen Apr 9, 2026
Other versions6 projects use a version of this.
Word for word · 6
- Adhamxon/claude-code-skills★ 2100% same
- skytiger6724/qwen-skills★ 2100% same
- yuusakuri/agent-skills★ 2100% same
- miovrag/claude-skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- architecture-diagramSkill
- criteria-auditSkill
- disk-space-auditSkill
- frontend-slidesSkill
- gpt-researcherSkill
- banner-designSkill
- brandSkill
- designSkill
- design-systemSkill
- slidesSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- intended-vs-implementedSkill
- cohort-analysisSkill
- brainstorm-okrsSkill
- create-prdSkill
- job-storiesSkill
- outcome-roadmapSkill
- pre-mortemSkill
- prioritization-frameworksSkill
- release-notesSkill
- retroSkill
- sprint-planSkill
- stakeholder-mapSkill
- strategy-red-teamSkill
- summarize-meetingSkill
- test-scenariosSkill
- user-storiesSkill
- wwasSkill
- beachhead-segmentSkill
- competitive-battlecardSkill
- growth-loopsSkill
- gtm-motionsSkill
- gtm-strategySkill
- ideal-customer-profileSkill
- marketing-ideasSkill
- north-star-metricSkill
- positioning-ideasSkill
- product-nameSkill
- value-prop-statementsSkill
- competitor-analysisSkill
- customer-journey-mapSkill
- market-segmentsSkill
- market-sizingSkill
- sentiment-analysisSkill
- user-personasSkill
- user-segmentationSkill
- analyze-feature-requestsSkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- identify-assumptions-existingSkill
- identify-assumptions-newSkill
- interview-scriptSkill
- metrics-dashboardSkill
- opportunity-solution-treeSkill
- prioritize-featuresSkill
- summarize-interviewSkill
- ansoff-matrixSkill
- The first 60 shown.
The file
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 14
If the user provides files with assumptions or research data, read them first.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Prioritize Assumptions
Triage assumptions using an Impact × Risk matrix and suggest targeted experiments.
Context
You are helping prioritize assumptions for $ARGUMENTS.
If the user provides files with assumptions or research data, read them first.
Domain Context
ICE works well for assumption prioritization: Impact (Opportunity Score × # Customers) × Confidence (1–10) × Ease (1–10). Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1 (Dan Olsen). RICE splits Impact into Reach × Impact separately: (R × I × C) / E. See the prioritization-frameworks skill for full formulas and templates.
Instructions
The user will provide a list of assumptions to prioritize. Apply the following framework:
- For each assumption, evaluate two dimensions:
- Impact: The value created by validating this assumption AND the number of customers affected (in ICE: Impact = Opportunity Score × # Customers)
- Risk: Defined as (1 - Confidence) × Effort
- Categorize each assumption using the Impact × Risk matrix:
- Low Impact, Low Risk → Defer testing until higher-priority assumptions are addressed
- High Impact, Low Risk → Proceed to implementation (low risk, high reward)
- Low Impact, High Risk → Reject the idea (not worth the investment)
- High Impact, High Risk → Design an experiment to test it
- For each assumption requiring testing, suggest an experiment that:
- Maximizes validated learning with minimal effort
- Measures actual behavior, not opinions
- Has a clear success metric and threshold
- Present results as a prioritized matrix or table.
Think step by step. Save as markdown if the output is substantial.
Further Reading
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.

