How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-planBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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 founderStep 1: see what is there
python3 "${CLAUDE_SKILL_DIR}/compile.py" --dir founder --checkprints the verdict and each check. The checks, all computed:
- Each unit earns money before fixed costs (
founder/numbers.json). - Year 1 makes an operating profit.
- The break-even fits inside capacity, if a capacity was given.
- 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 founderwrites 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.


