CommunityCoding & Developmentgithub.com

kill-or-build

Your business planner. Compiles everything the other Shark Tank Proof skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations, the launch plan and the evidence ledger) into one business plan with a verdict at the top that is computed, never written by hand: Profitable (the numbers pass and a real buyer has paid, signed or booked), Unproven (works on paper, no real buyer yet), Not yet (with the failing numbers) or Incomplete. A simulated panel can fail a plan but never pass one. Adds an executive summary and a one-page version. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the Shark Tank Proof pack.

What is kill-or-build?

kill-or-build is a Claude Code agent skill that your business planner. Compiles everything the other Shark Tank Proof skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations, the launch plan and the evidence ledger) into one business plan with a verdict at the top that is computed, never written by hand: Profitable (the numbers pass and a real buyer has paid, signed or booked), Unproven (works on paper, no real buyer yet), Not yet (with the failing numbers) or Incomplete. A simulated panel can fail a plan but never pass one. Adds an executive summary and a one-page version. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the Shark Tank Proof pack.

Works with✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/peaknr35/shark-Tank-proof/tree/main/skills/kill-or-build

Installed? Explore more Coding & Development skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

What does kill-or-build do?

The last step. One document a founder can act on, built only from what the pack found, and honest about which parts are real.

Read ${CLAUDE_SKILL_DIR}/../receipts/rules.md first.

Tool in this folder:

python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder

Step 1: see what is there

python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder --check

prints the verdict and each check. The checks, all computed:

  1. Each unit earns money before fixed costs (founder/numbers.json).
  2. Year 1 makes an operating profit.
  3. The break-even fits inside capacity, if a capacity was given.
  4. Enough simulated buyers buy (founder/panel/results.json; default bar 25%, change it with --min-buy-rate and say why). A low panel fails the plan; a high panel proves nothing.
  5. Real demand: at least one MEASURED demand claim in founder/evidence/claims.csv (a payment, a deposit, a signed pilot, a booking).

The verdicts:

verdictmeans
Incompleteno numbers yet: offer /burn-test
Not yeta check fails; each failure is listed with its number
Unproventhe math works on paper, but no real buyer has committed
Profitablethe math works and at least one real buyer committed

Run ledger.py summary first so the evidence section is current:

python3 "${CLAUDE_SKILL_DIR}/../receipts/ledger.py" summary

If there are no numbers, the verdict is Incomplete: offer to run /burn-test. List the other missing sections with the skill that fills each. Do not fill a missing section yourself from guesses.

Step 2: the summary

Write founder/summary.md, half a page, plain words, opening with The hard truth: the single most likely reason this fails.

  • What the business is and who it is for, in two sentences.
  • The verdict and the three numbers behind it (margin, break-even, year 1).
  • What is real: the count of MEASURED and THEY SAID IT claims, and what they are. Then what is still a guess.
  • What the simulated panel and board agreed on, and where they disagreed, labelled as simulated.
  • The biggest risk and what will be done about it.
  • What the founder needs to start (cash from the CFO, the first test from launch).
  • The one thing to do this week.

If the verdict is Not yet, the summary leads with what has to change and which skill changes it. If it is Unproven, it leads with the one real-world test that would prove or kill it this month. Never soften a failing check, and never write an Unproven plan as if it were a validated one.

Step 3: compile

python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder

writes founder/business-plan.md: title, the verdict and its checks, the key numbers table, the idea, then every section the pack produced (summary, board, competition, panel, pricing, offer, numbers, marketing, brand, operations, launch), and what is not done yet.

Step 4: the one-pager

Write founder/one-pager.md for the founder and close partners: the problem, the customer, the offer and price, the numbers table, the real evidence (and the panel, labelled simulated), what the money is for, and the ask. Same numbers as the plan, word for word.

For anyone outside (a customer, a funder, a lender), do not send the plan or this page: run /handshake, which builds only from claims that audience may see and checks the result.

Rules

  • The verdict comes from compile.py. Never write Profitable by hand, never round a failing number into a passing one, and never call Unproven "almost there".
  • Say once, clearly: the panel and board are simulated and the numbers are projections; only real customers and real quotes confirm them. Not financial, legal or tax advice.
  • If the user wants a PDF or a deck, offer to export the plan, but keep the markdown as the source of truth.

Output

founder/summary.md, founder/business-plan.md, founder/one-pager.md. Then give the user the verdict in one line, the hard truth, and the one real-world thing to do this week. Next: /handshake for the receiver who has to say yes.

Individual skills in this repo

This repo contains 5 individual skills — each has its own dedicated page.

burn-test

Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".

dealbreaker

Builds an offer too good to refuse. Lists every problem the buyer hits on the way to the result they want, turns each into a solution, trims to what is cheap to deliver and valuable to the buyer, and stacks it with honest bonuses, a guarantee the CFO can afford, real urgency and a clear name. Scores it on the value equation (outcome, likelihood, time, effort) and re-tests it on a quick buyer panel. Use when the user says "make my offer better", "why won't people buy", "what should I include", "guarantee", "bonuses", "grand slam offer", or after the panel shows people passing.

handshake

Turns the founder folder into the thing that gets one real person to say yes to the next step: a one-page pilot offer for a customer, an NSF Project Pitch or grant answer for a funder, an investor or lender one-pager, a business case for a boss, or an invite for the people who will use it. Always writes the one-sentence, three-sentence and three-minute versions first. Builds only from claims in the evidence ledger that the audience may see, never from simulated buyers, and checks the finished pitch with the ledger before it goes out. Use when the user says "pitch this", "write a pilot offer", "one-pager", "grant pitch", "NSF pitch", "deck for", "email this customer", "business case", or "what do I send them".

shark-board

Your board of directors, built to disagree with you. Puts a business idea in front of a four-member board, each a sub-agent reading the idea through one published framework: the Offers lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's Zero to One), the Product lens (from Walter Isaacson's biography of Steve Jobs) and the Evidence lens (from Rob Fitzpatrick's The Mom Test), which scores only what real people have done. Each member scores the idea, names what would kill it and the cheapest test that would prove it, and votes fund, fund with conditions, or pass. Use when the user says "test my business idea", "would this work", "pressure-test this", "what would a board say", "is this a good business", or starts the Shark Tank Proof pack on a new idea.

truth-serum

The consumer panel. Spins up a swarm of buyer sub-agents (default 100, --quick for 20) trained on the user's target customer, each with a different income, age, buying behaviour and objection, shows every one the same pitch, and runs the business through 100 buyer scenarios to see who buys, who doesn't, and why. Tallies the answers into buy rates by segment, the reasons people pass in their own words, what would flip a no, and price answers for litmus. Every result is labelled SIMULATED: it finds objections and the questions to ask real buyers, and never counts as demand. Use when the user says "would people buy this", "test it on customers", "run the consumer panel", "simulate buyers", "who is my customer", or "validate demand".

Related Skills