Free Agent Skill
Focus and Tradeoffs
Cut a bloated plan, roadmap, or list of priorities down to the one or two things that actually matter, in the tradition associated with Steve Jobs's product focus — "innovation is saying no to a thousand things."
Use when: the user has a long list of priorities/features/goals with no clear ranking, describes something as "trying to do everything," is building a roadmap or plan that keeps growing, or asks for help prioritizing. This is about forcing real tradeoffs, not just reordering a list — the output should include things explicitly cut, not just resequenced.
Install this skill
- Create a folder named `focus-and-tradeoffs`.
- Save the skill content below as `SKILL.md` inside that folder.
- Place the folder in `~/.codex/skills/` for Codex, `.cursor/skills/` for Cursor or `.claude/skills/` for Claude Code.
- Describe the task normally. Your agent loads the skill when its description matches.
---
name: focus-and-tradeoffs
description: Cut a bloated plan, roadmap, or list of priorities down to the one or two things that actually matter, in the tradition associated with Steve Jobs's product focus — "innovation is saying no to a thousand things." Use whenever the user has a long list of priorities/features/goals with no clear ranking, describes something as "trying to do everything," is building a roadmap or plan that keeps growing, or asks for help prioritizing. This is about forcing real tradeoffs, not just reordering a list — the output should include things explicitly cut, not just resequenced.
---
# Focus and Tradeoffs
A list where everything is "important" hasn't actually been prioritized —
it's been left unprioritized with a rank order attached. Real focus means
some things get cut, not just moved to the bottom.
## The technique
**1. List everything, without judgment first.** Get the full list out
before ranking anything — premature cutting during listing loses good
ideas along with bad ones.
**2. Force a hard constraint.** Ask or propose: if only ONE of these
could happen this cycle, which is it, and why? Not "top 3" — one. The
discomfort of choosing one is the point; it's what surfaces the real
priority instead of a comfortable spread.
**3. For everything else, ask what it's actually trading against.**
Every "yes" to one thing is implicitly a "no" to something else
(capacity, attention, coherence). Make that trade explicit: "doing this
means NOT doing ___, because ___." If the tradeoff can't be named, the
priority list probably hasn't been thought through yet, it's just been
listed.
**4. Distinguish "important" from "urgent" from "easy."** Long lists
often mix these up — something gets kept because it's easy to do, not
because it matters. Flag items that seem to be on the list for that
reason specifically.
**5. Say what gets cut, out loud.** The output of this exercise should
include an explicit "not doing" list, not just a reordered "doing" list.
Saying no to something is the actual deliverable — a prioritized list
that quietly keeps everything hasn't done the work.
**6. Check for coherence, not just individual value.** A focused plan is
usually a small number of things that reinforce each other, not just the
individually highest-scoring items picked independently. Ask whether the
top items actually combine into one clear story.
## Output
A short "doing" list (ideally 1-3 items) and an explicit "not doing, and
here's why" list. Resist the pull to soften the cuts by saying "later" for
everything — some things should be a real no, not a deferred yes.
More free skills
Prompt Refiner
Turns a vague request into an executable brief without silently inventing missing requirements.
Decision Framer
Separates the real choice from noise, then tests options against explicit criteria and uncertainty.
Meeting to Actions
Converts messy notes into decisions, owned actions, deadlines and unresolved questions.
Calibrated Forecasting
Turn a vague prediction or unstated confidence level into an explicit, calibrated probability estimate, following the practices Philip Tetlock found separated "superforecasters" from everyone else — breaking questions into sub-questions, checking base rates, updating in small increments as new information arrives, and tracking predictions against outcomes.
Decision Memo
Structure a real, consequential decision as a written narrative memo in the style Jeff Bezos used at Amazon — full sentences and paragraphs rather than bullet points, forcing the logic to be checked rather than gestured at, plus explicit classification of whether the decision is reversible (a "two-way door") or not (a "one-way door").
Feynman Teachback
Test and build genuine understanding of a concept using the Feynman technique — explain it as simply as possible, notice exactly where the simple explanation breaks down, and treat that break point as the thing to actually go learn.
First Principles
Rebuild a problem from fundamental truths (physics, economics, unit costs, what's actually true regardless of convention) rather than by analogy to how things are normally done — the reasoning style associated with Elon Musk's approach to manufacturing cost problems and Richard Feynman's approach to physics problems.
Jobs to Be Done
Diagnose what "job" a customer is actually hiring a product, service, or workaround to do, using the Jobs-to-be-Done framework (Clayton Christensen's "progress in a specific circumstance," Bob Moesta's forces-of-progress and switch interview, Tony Ulwick's job statements and desired-outcome scoring).
Mental Models
Apply Charlie Munger's "latticework" approach — a small set of cross-disciplinary thinking tools (inversion, second-order effects, incentives, circle of competence, opportunity cost, base rates) to frame a vague or general problem.
Moat Analysis
Assess whether a competitive advantage is durable (a real "moat," in Warren Buffett and Charlie Munger's terms) or temporary, by checking it against the standard sources of durable advantage — switching costs, network effects, economies of scale, brand/trust, and regulatory or IP protection — rather than taking "we're ahead right now" at face value.
Negotiation Prep
Prepare for a high-stakes negotiation or hard conversation using tactical-empathy techniques associated with former FBI negotiator Chris Voss — labeling emotions, calibrated open-ended questions, mirroring, and getting to genuine "that's right" rather than a grudging "yes."
Postmortem / Retro
Extract a specific, reusable lesson after something succeeded or failed, following the principle (associated with Ray Dalio's "pain plus reflection equals progress") that outcomes only compound into better judgment if they're deliberately converted into a written, checkable lesson rather than just felt and moved past.
Premortem
Run a premortem — psychologist Gary Klein's technique of imagining a plan has already failed and working backward to explain why, which surfaces risks that forward planning misses because it counteracts the social and psychological pressure to seem confident.
Want this skill connected to a complete workflow?
Every skill is free and works independently. We can connect it to your tools, context, approval steps and other agents as a designed, tested pipeline for your business.