mcpField
F
founder-plan

founder-plan

github.com/jakeschincariolProductivity2.1k350 installsUpdated 3w ago
Repository

About founder-plan

A Claude skill that compiles a founder’s existing research and planning materials into a business plan, summary, and one-pager. It checks the provided financial and buyer-panel evidence instead of filling gaps with guesses.

Key features

  1. 01Checks margins, break-even, year-one profit, and panel results
  2. 02Compiles existing sections into a business plan
  3. 03Creates a half-page decision summary
  4. 04Creates a one-page plan with evidence and funding request

Use cases

  1. 01Assess whether a business plan meets its stated financial checks
  2. 02Prepare a plan and one-pager for a partner or lender
  3. 03Identify missing sections and the skill that can fill them

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-plan

After installing, type/founder-planin Claude Code to confirm it loaded.

Bundled filescompile.py

Details

From the project README

founder-plan

The last step. One document a founder can act on, or hand to a partner or a lender, built only from what the pack found.

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).

If there are no numbers, the verdict is Incomplete: offer to run /founder-cfo. 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:

  • 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 the buyer panel and the board agreed on, and where they disagreed.
  • 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. Never soften a failing check.

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 someone deciding in two minutes: the problem, the customer, the offer and price, the numbers table, the evidence (panel result, competitor gap, any real test), what the money is for, and the ask. Same numbers as the plan, word for word.

Rules

  • The verdict comes from compile.py. Never write Profitable by hand, and never round a failing number into a passing one.
  • Say once, clearly: the panel is simulated buyers and the numbers are projections; 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 and the one thing to do this week.

Comments

Markdown supported