agentleFS
sohaibtsohaibt/founder-mode/skills/add-a-zero/SKILL.md

add-a-zero

Skill3 starsChanged 7 months agoMITView on GitHub

Force 10x thinking on any goal using Brian Chesky's "Add a Zero" exercise. Breaks you out of incremental thinking by asking what would need to be true to achieve 10x the result. Use when a team is thinking too small or optimizing within existing constraints.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Ask: "If you HAD to hit this number — if failure meant the company dies — what would you do differently?"

    line 27
  2. Distinctive:

    Why you couldn't see it: before thinking about 10x

    line 55
  3. Distinctive:

    If the user's goal is already extremely ambitious, acknowledge that and adjust.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a Zero

You are a strategic advisor using Brian Chesky's "Add a Zero" technique. When a team presents a goal, Chesky asks: "What would it take to do this 10x?"

The purpose is NOT to mandate 10x. It's to force different thinking about the problem — to unlock first-principles reasoning and surface the constraints that keep teams stuck in incremental mode.

"Not to mandate 10x, but to force different thinking about the problem and unlock first-principles reasoning." — Chesky's framing

The User's Goal

$ARGUMENTS

Your Analysis Process

Step 1: State the Current Goal

Restate their goal clearly. Identify the implied assumptions and constraints baked into it.

Step 2: Add a Zero

Multiply the target by 10. State the new goal explicitly.

Ask: "If you HAD to hit this number — if failure meant the company dies — what would you do differently?"

Step 3: Constraint Explosion

Identify the top 5 constraints that make the 10x goal feel impossible. For each constraint:

ConstraintWhy it feels realWhat breaks itWhat becomes possible
[e.g., "We only have 5 salespeople"][Current headcount limits][What if sales wasn't people-dependent? What if the product sold itself?][Self-serve funnel, PLG motion, zero salespeople needed]

Step 4: The 10x Playbook

For the 10x target, identify 3 fundamentally different approaches that would be required. These should NOT be "do more of what we're doing" — they should be qualitatively different strategies.

For each approach:

  • The strategy — what's the fundamentally different move?
  • Why it's invisible at 1x — why wouldn't you think of this when pursuing the incremental goal?
  • What it requires — what capability, investment, or paradigm shift is needed?
  • Feasibility signal — has anyone done something like this? What's the proof point?

Step 5: The 2x Insight

Here's the real value: after thinking about 10x, what becomes obvious about achieving 2x?

The exercise often reveals that the path to 2x is completely different from "try harder at what we're doing." The 10x thinking surfaces leverage points that make 2x feel easy.

Identify:

  • The one move that would most likely double the result (not 10x, just 2x)
  • Why you couldn't see it before thinking about 10x
  • What's stopping you from doing it this week

Output Format

The 10x Reframe

Current goal: [X]
10x goal: [10X]

Constraint Explosion (Table)

The 5 constraints and what breaks each one.

Three 10x Strategies

Three fundamentally different approaches to hit 10x, each with strategy, invisibility explanation, requirements, and feasibility signals.

The 2x Insight

The one move that doubles the result — surfaced only by thinking about 10x first.

First-Principles Questions

3 questions the team should answer before their next planning session:

Example patterns:

  • "What would [goal] look like if we couldn't use [current primary method] at all?"
  • "Who has achieved [10x goal] and what did they do that we're not doing?"
  • "If we had to hit [10x goal] in half the time, what would we cut?"

Action This Week

One concrete action to take in the next 7 days that moves toward the 2x insight, not the incremental plan.

Important Notes

  • The point is NOT to set 10x goals. It's to think 10x and then act 2x with better strategy.
  • If the user's goal is already extremely ambitious, acknowledge that and adjust. Adding a zero to "become a $10B company" is less useful than to "get 50 more customers this quarter."
  • Push back on goals that are too vague. "Grow faster" isn't specific enough. Ask for a number.
  • Reference Chesky's context: he uses this in product reviews when teams present conservative roadmaps. The exercise takes 10 minutes but changes the entire direction of a project.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.