From founder-os
Price a bet by what it costs when it is wrong and cap the downside in writing before it starts — run before any bet enters goals.md
How this skill is triggered — by the user, by Claude, or both
Slash command
/founder-os:bet-sizingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The founder has already computed the upside. That arithmetic is why they are in
The founder has already computed the upside. That arithmetic is why they are in the room, and it is not in dispute. This skill computes the other number.
The cap is the product here. A maximum spend chosen now, before anything is sunk, is a real constraint. The same number chosen in month three, with 60 hours already in the ground, is a rationalization with a spreadsheet attached.
Before any bet is written into goals.md — every bet in quarterly-planning
passes through here.
Also whenever an opportunity arrives mid-quarter and the founder wants to know whether it is worth doing. It usually is, at some size. The question is which size.
Read first — house rule 1:
metrics.md — the effective hourly rate, cash position, and runway, with
their datesgoals.md — what is already committed, because the founder's hours are
already spent on paperdecisions/ — has a bet of this shape been made before, and what did it
actually cost?goals.md had already committed to something else.metrics.md. Founder hours are the most
expensive input in the company and the only one that gets called free. If
metrics.md has no effective rate, stop and hand to the CFO — you cannot
size a bet in a currency that does not exist.goals.md now, while
saying a small number is free.metrics.md, this is not a bet — it is a bet-the-company move. It goes
through the Board Member (premortem) first, and it gets logged in
decisions/ by the Chief of Staff whichever way it goes. At this size,
ask the Chief of Staff to convene first: the two or three agents whose
files the bet touches each state a written position — two or three
sentences from their own book, numbers and dates — before the premortem
runs. The premortem then attacks a plan whose owners are already on record,
and the record follows the decision into decisions/.red-team before committing. Irreversibility is the
only thing that earns a delay.goals.md. A bet whose size lives
in the conversation is unsized.Append to the bet's block in goals.md:
Cost: <hours> h @ <rate from metrics.md, dated> + <cash>
Cap: stop at <hours> h or <cash>, or <date> — whichever comes first
If wrong: <what is lost, concretely> — reversible in <time>
Never size a bet without metrics.md. A cost estimate with no rate and no
runway behind it is a wish with units.
Never size the upside. It is not this skill's job, the founder has done it, and adding a second optimistic number to the page will not improve the decision — it will balance it, which is worse.
Refuse to size a bet with no judgement date. Send it back to
quarterly-planning. Without a date, "the cap or the date, whichever comes
first" has no second half, and the cap will be quietly renegotiated instead.
Do not decide whether to take the bet. You price it. Taking it is the founder's call, and if the price kills it, that is the price talking.
npx claudepluginhub msolecki/founder-os --plugin founder-osGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.