tradeoff-decision-framework
Skill0 starsChanged 5 months agoMITView on GitHub
Structures consequential technical and product decisions by making options, criteria, and reversibility explicit. Use when choosing between architectures, tools, or approaches with real tradeoffs, when a team is stuck debating, or when a decision needs to be documented and defensible later.
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 19
Criteria that actually matter, weighted: not a feature checklist — the 2-3 dimensions that dominate (e.g., operational cost, team …
≈ “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
Tradeoff Decision Framework
Most "hard decisions" are hard because the criteria are implicit and the options are unstated, not because the answer is close. Make the decision space explicit and the choice usually becomes obvious — or its true difficulty becomes visible.
Classify the decision first — it sets how much rigor to spend
- Reversible (two-way door): cheap to undo. Decide fast, with less analysis; the cost of being wrong is small and the cost of delay is real.
- Irreversible (one-way door): expensive or impossible to undo (public API, data model, schema, vendor lock-in, security posture). These deserve disproportionate analysis.
- Misclassifying a reversible decision as irreversible wastes time; the reverse wastes the company. Spend rigor proportional to reversibility × blast radius.
Make the space explicit
- Options including "do nothing": the status quo is always a candidate; a third option usually exists beyond the false binary being debated.
- Criteria that actually matter, weighted: not a feature checklist — the 2-3 dimensions that dominate (e.g., operational cost, team familiarity, failure blast radius). Weight them before scoring to avoid rationalizing a favorite.
- Consequences across time: cheap now / expensive later (tech debt) vs expensive now / cheap later. Name the time horizon you're optimizing.
Adversarial validation
- Steelman the option you dislike: argue its strongest case. If you can't, you don't understand the decision.
- Pre-mortem: assume you chose option A and it failed badly in a year — what was the cause? Then do it for B. The failure modes, not the benefits, usually decide.
- Reversibility check under stress: "we can change it later" — can you actually, once there's data/users/integrations depending on it? Most "reversible" decisions calcify.
- Whose incentives?: who benefits from each option, and is the loudest advocate optimizing for the system or their local incentive?
- Second-order effects: what does this decision make easy or hard next? Decisions constrain future decisions more than they solve present ones.
Non-obvious risks
- Analysis paralysis on reversible decisions is itself a costly decision (to delay).
- Consensus-seeking averages options into a compromise that has the weaknesses of both and the strengths of neither.
- The "obvious" choice often optimizes the visible criterion while ignoring the operational/maintenance cost that dominates total cost of ownership.
Output structure
Deliver: the decision classified by reversibility and blast radius, the real options (including do-nothing and a non-obvious third), the weighted criteria set before scoring, the pre-mortem failure mode for the leading option, and a clear recommendation with the single condition that would change it.
In this repository29 other files it gives its agents.
- adversarial-code-reviewSkill
- api-contract-designSkill
- attack-surface-mappingSkill
- authn-authz-design-reviewSkill
- benchmark-designSkill
- capacity-scalability-planningSkill
- concurrency-race-analysisSkill
- data-consistency-modelingSkill
- data-exfiltration-analysisSkill
- distributed-consensus-designSkill
- error-handling-architectureSkill
- event-driven-architectureSkill
- experiment-designSkill
- hypothesis-falsificationSkill
- incident-rca-postmortemSkill
- legacy-refactoring-strategySkill
- literature-synthesisSkill
- metrics-designSkill
- multi-layer-caching-strategySkill
- mvp-scope-cuttingSkill
- performance-profilingSkill
- rate-limiting-designSkill
- requirements-disambiguationSkill
- secrets-management-auditSkill
- statistical-validity-analysisSkill
- supply-chain-risk-analysisSkill
- system-decomposition-synthesisSkill
- threat-modelingSkill
- user-failure-mode-mappingSkill
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.

