strategy-decisions
Skill0 starsChanged 2 months agoMITView on GitHub
Apply Reid Hoffman's two-rule strategy framework whenever Nick is making a strategic decision, evaluating options, debating whether to pursue something, or feeling stuck on a choice. Trigger on any signal of decision-making: "should I", "we're deciding", "thinking about", "weighing options", "not sure whether to", "is it worth", or any discussion of tradeoffs. This is Nick's North Star framework — use it proactively, even if he doesn't explicitly ask. IMPORTANT: Before applying Hoffman's framework, always run the execution-first diagnostic (Rule 0) to determine whether this is actually a strategy problem. If it's an execution problem, route to execution-compounding instead. This pre-check exists because idea-oriented people persistently misdiagnose execution problems as strategy problems.
In this repository15 other files it gives its agents.
- blog-cold-readSkill
- content-proportion-checkSkill
- defensibility-checkSkill
- giving-feedbackSkill
- hamming-taste-principlesSkill
- idea-to-briefSkill
- learning-mediumSkill
- linear-write-cleanupSkill
- portable-handoffSkill
- saddles-positioningSkill
- session-stateSkill
- skill-auditSkill
- transcript-auditSkill
- uncertainty-killerSkill
- writing-craftSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 49
If the answer is no, the new decision may be a form of avoidance — the excitement of deciding replacing the grind of executing.
- Distinctive: line 80
When there are many possible paths, group them into three intensity tiers:
- Distinctive: line 91
If you're building a list of reasons, you're convincing yourself — don't do it
- Distinctive: line 99
When Nick presents a decision:
- Distinctive: line 108
If he's overthinking or collecting too many reasons, name it directly.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Strategy Decision Framework (Reid Hoffman)
Three rules. Rule 0 runs first on every decision. Rules 1 and 2 apply only after Rule 0 confirms this is actually a strategy problem.
Rule 0: The Execution-First Diagnostic
Before applying Hoffman's framework, classify: is this a strategy problem or an execution problem?
This pre-check exists because creative, idea-oriented people — including most marketers — have a persistent bias toward diagnosing every problem as a strategy problem. When results disappoint, the instinct is to find a new narrative, a new channel, a new approach. That instinct is often wrong. The existing approach, executed significantly better, would frequently solve the problem without the cost and disruption of a strategic pivot.
Run These Four Questions
- "Have you executed the current plan at the level you know is possible?" Not "pretty well" — at the level the best team you've seen would execute it. If the honest answer is no, stop. This is an execution problem.
- "Can you point to a specific step in the process that could be significantly better?" If yes, you already know where to focus. That's execution, not strategy.
- "How many full cycles have you run?" Fewer than 3-5 complete cycles means you haven't generated enough signal to distinguish bad execution from bad strategy. Strategy conclusions from poorly-executed attempts are unreliable.
- "Are you excited about a new idea right now?" This is the tell. If the "strategy problem" diagnosis arrives packaged with enthusiasm for a bold new direction, suspect the bias. New ideas generate energy. Execution improvement doesn't. The less exciting diagnosis is usually the correct one.
Routing
- Execution problem → Route to
execution-compounding. Map the process chain, find the leverage point, improve execution. Do not apply Rules 1 and 2. - Strategy problem → Continue to Rules 1 and 2 below. Apply Hoffman's framework.
- Unclear → Default to execution. The base rate for "it's actually an execution problem" is much higher than most people estimate. You can escalate to strategy later; you can't un-abandon a process you pivoted away from.
The Completion Check
One additional question, especially when Nick is considering a new strategic initiative:
"Have you fully executed the last decision you made?"
If the answer is no, the new decision may be a form of avoidance — the excitement of deciding replacing the grind of executing. Name this if you see it.
Rule 1: Speed
Default bias: decide now, disprove later.
The pattern to avoid: limited info → punt → information-gathering spiral → world changes.
The correct pattern:
- Make a provisional decision instinctively based on current info
- Identify the specific information that would disprove that decision
- Go get only that — nothing else
Accepting ~10-20% error rate is the cost of speed. That's a feature, not a bug.
Context sensitivity:
- Startup / early-stage context: speed is near-paramount
- Larger org context: don't compete on pure speed — find strategies where your slowness becomes a structural strength
Apply this by asking:
"What's your instinctive call right now? What single piece of info would change that?"
Rule 2: Simplicity (which enables speed)
Two tools for cutting complexity:
Tool A: Light / Medium / Heavy bucketing
When there are many possible paths, group them into three intensity tiers:
- Light (basic) — minimum viable action
- Medium (intermediate) — meaningful effort
- Heavy (advanced) — full commitment
Then ask: "How intensively do we want to go after this?" Pick a tier, execute that tier's actions.
Tool B: The One Decisive Reason rule
For any potentially expensive action (time, money, focus):
- There must be one single decisive reason to do it
- Secondary reasons can backfill after the primary reason clears
- If you're building a list of reasons, you're convincing yourself — don't do it
"If I can't name one reason that alone justifies this, it's a no."
How to apply in conversation
When Nick presents a decision:
- Run the execution-first diagnostic — is this actually a strategy problem? If not, route to execution-compounding. If Nick is excited about a new direction while the current one is under-executed, name the pattern.
- Surface his instinct — don't let him skip this step
- Name the disprove condition — what single fact would flip the call?
- Bucket the options — light/medium/heavy if there are multiple paths
- Test for one decisive reason — especially for resource-heavy commitments
- Push toward a decision — the framework exists to move, not to analyze indefinitely
If he's overthinking or collecting too many reasons, name it directly.
Source
Reid Hoffman's decision-making principles, as documented by Ben Casnocha (former chief of staff). Grounded in entrepreneurial contexts where the battlefield is foggy, the ground is shifting, and inaction is its own risk.
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.

