founder-launch
Skill131 starsChanged 37 days agoMITView on GitHub
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
In this repository10 other files it gives its agents.
- founder-boardSkill
- founder-brandSkill
- founder-cfoSkill
- founder-competitorsSkill
- founder-consumerSkill
- founder-marketingSkill
- founder-offerSkill
- founder-opsSkill
- founder-planSkill
- founder-pricingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 31
Write the success line before running it (for example: 50 pre-orders in two weeks at $6.50), and compare the result with the panel's buy …
≈ “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.
Files
founder-launch
Launching is a project with a date. This skill turns everything else in the pack into a dated plan, and starts with the cheapest way to find out if real people will pay before the big money goes out.
Step 1: test before you spend
Pick the cheapest real test that fits the business, and run it before signing the
big costs in founder/numbers.json:
| business | the test |
| physical shop or café | a pop-up, a market stall or a pre-order list with a price and a date |
| online product | a landing page with the price and a "pre-order" or "join the waitlist" button |
| service or agency | three paid pilot clients at the planned price |
| subscription | a founding-member offer, paid up front |
Write the success line before running it (for example: 50 pre-orders in two weeks
at $6.50), and compare the result with the panel's buy rate. If real buyers fall
well short of the panel, trust the real buyers and go back to /founder-offer or
/founder-pricing.
Step 2: the countdown
From today to launch day, with real dates (ask for the target date; default to the
earliest realistic one given lead times in founder/ops.md). Weekly blocks, each
task with an owner and a deadline:
- Legal and money: registration, bank account, permits from
founder/ops.md. - Build: fit-out or website, suppliers ordered by their lead times.
- Brand: sign, packaging, profiles from
founder/brand.md. - Marketing: the calendar in
founder/marketing.mdfrom launch minus 14 days. - Team: hiring and training on the SOPs.
- A soft open or friends-and-family day before the public launch.
Mark the critical path: the tasks that move the launch date if they slip.
Step 3: launch day
An hour-by-hour run sheet: who is where, what goes out on which channel, the opening offer, what to do if something breaks (from the risk register).
Step 4: the first 30 days
The weekly numbers to track (from the CFO: units a day against break-even; from marketing: the channel numbers), the level that triggers a change, and a review on days 7, 14 and 30 with the questions to answer.
Output
founder/launch.md with the test, the countdown, the run sheet and the 30-day
review. Next: /founder-plan compiles everything into the business plan.
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
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.