create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-in…
Install / Use
npx skills add wondelai/skills --skill create-businessInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Project & Program ManagementSupported Platforms
Our assessment of create-business
create-business scores 87/100 on our quality scale, 34th of 83 Project & Program Management skills we index (top 41%).
Its SKILL.md is 24 KB long, well organised into 19 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so create-business is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
create-business compared with similar skills
All 4 of these similar skills score higher than create-business; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| create-business (this skill)by wondelai | 87 | 2.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install create-business?
- Run
npx skills add wondelai/skills --skill create-business. The install tabs above show the steps for each supported agent. - Which AI agents does create-business work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is create-business safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is create-business still maintained?
- The repository was last updated about 2 months ago, so create-business is actively maintained.
Skill content
View source on GitHubname: create-business description: 'Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation, crossing-the-chasm - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to start a new business, validate a startup idea, find product-market fit before building, or says ''I have an idea for a company''. Do not use once the business has paying customers: use grow-business to add revenue and customers, or improve-business to fix strategy and operations. For building the product itself use create-app or create-website. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.1"
Create a Business
Take a raw idea to a business you can defend on every axis: who it is for, what job it does, why it is different, why it wins, what it costs, and why anyone would pay. This journey runs ten phases in sequence, looping back as evidence accumulates. It is interactive — the agent asks before every decision — and resumable: all state lives in docs/ so you can stop and restart across sessions. The order is the point: demand before building, strategy before scale, price before product.
Core Principle
Earn your evidence before you spend your runway: demand before building, strategy before scale, price before product. You can be wrong about your product in a week, or wrong about your business in a year — pick the week. This skill sequences the phases, asks the questions at every decision point, and records what you decide in docs/. The constituent skills carry the method — invoke them rather than improvising their frameworks.
Journey Map
| Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | jobs-to-be-done | What progress is the customer really hiring us for? | Creates docs/CUSTOMER.md | | 2 | mom-test | Is the job real, painful, and worth paying to solve? | Extends docs/CUSTOMER.md — GATE | | 3 | design-sprint | Does the concept survive contact with five real customers? | Creates docs/EXPERIMENTS.md | | 4 | lean-startup | What is the smallest MVP that tests the riskiest assumption? | Creates docs/PRODUCT.md; extends docs/EXPERIMENTS.md | | 5 | good-strategy-bad-strategy | What is the one critical challenge, and how do we win? | Creates docs/STRATEGY.md | | 6 | blue-ocean-strategy | Where is the uncontested space we can own? | Extends docs/STRATEGY.md | | 7 | obviously-awesome | What are we, and why does that matter, in 30 seconds? | Creates docs/POSITIONING.md | | 8 | hundred-million-offers | What makes this offer impossible to refuse? | Creates docs/OFFER.md | | 9 | monetizing-innovation | What will people actually pay, and per what? | Extends docs/OFFER.md | | 10 | crossing-the-chasm | Which single segment do we dominate first? | Extends docs/STRATEGY.md |
Operating Rules
- Resume first. Before anything else, read
docs/CREATE-BUSINESS-PLAN.mdand every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted. - Intake on first run only. No tracker: run the Intake below, then create
docs/CREATE-BUSINESS-PLAN.mdwith every phase statusedpending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan. - Phase entry. Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defer — phases marked GATE may be deferred, never skipped. Mark the phase
in-progresson proceed. Done when the user chose. - Skill invocation and fallback. Load the phase's skill and use it: each phase's Invoke line names the skill by slug — use that skill to run the phase. If it is not available, offer:
npx skills add wondelai/skills/<slug> --global. If the user declines, run the phase from its Brief — the minimum viable method. State which mode you are in. - In-phase decisions. Ask every question under "Decide with the user" — with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.
- Phase exit. Present the draft artifact content for sign-off before writing. On approval: write or extend the docs/ files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows
done. - Artifact discipline. Read before writing; create a file only if missing, otherwise extend — add or update your sections, preserve everyone else's. Files are UPPERCASE in
docs/. Every recommendation lands as a checkbox or a table row with owner and priority. See references/artifact-templates.md when creating a docs/ file for the first time — create it from the full skeleton (all section headings), then fill the sections your phase names. - The agent prepares and processes; only the human talks to customers. Draft interview guides and score transcripts, then pause with status
awaiting-evidenceuntil the user returns with notes. Never simulate a customer — a role-played interview confirms whatever you hope is true.
Intake
Ask these before creating the tracker (skip any already answered):
- What is the raw idea, in one or two sentences? (seeds the job reconstruction in Phase 1)
- Who do you imagine the customer is, and how do they solve this today? (feeds Competing Alternatives; a tight segment speeds Phases 7 and 10)
- What customer access do you have — a list, a community, warm intros? (gates Phases 2-4; without access the human-only interview phases stall)
- What evidence already exists — past interviews, a waitlist, sales, a prototype? (lets us fast-track or skip discovery already done)
- Is this B2B or B2C — and if B2B, sales-led or self-serve? Is it a marketplace or network product? (routes optional predictable-revenue and cold-start-problem)
- What is your runway and deadline? (sets phase depth and whether to defer strategy phases)
- Is any product already built? (if so this may be the wrong journey — route to grow-business or improve-business)
Phase-skip heuristics: skip Phase 1 when a validated job statement with three dimensions already exists in CUSTOMER.md; skip Phase 3 when a working prototype has already been tested with 5+ target users; defer Phase 6 for a clearly-differentiated niche until the kernel is set; defer Phases 5-10 until Phase 2 returns real commitments — no strategy on unvalidated demand. Then create docs/CREATE-BUSINESS-PLAN.md from the template, status every phase, and confirm the plan. Done when docs/CREATE-BUSINESS-PLAN.md exists with every phase statused and the user has confirmed the plan.
Phases
Phase 1 — Find the real job (jobs-to-be-done)
Purpose: Reframe the raw idea as the progress a customer is trying to make, so the business survives even if the first solution dies.
Brief (fallback): A job is progress in context, not a goal or a task — write it as When [situation], I want to [motivation], so I can [outcome], solution-agnostic. Every job has functional, emotional, and social dimensions; the differentiated product usually lives in the last two. Real competition includes workarounds and non-consumption — name the hire you must beat.
Invoke: Use the jobs-to-be-done skill with the raw idea and customer guess from Intake. Ask for a When/I-want-to/so-I-can job statement, all three dimensions, and the full competing-alternatives set including non-consumption.
Decide with the user: Which job statement is the real one, and which competing hire you must beat first. Recommend the tightest statement that still names an emotional or social dimension.
Artifact: Create docs/CUSTOMER.md with ## Job Statement, ## Job Dimensions, and ## Competing Alternatives. Update the tracker.
Done when: CUSTOMER.md holds a solution-agnostic job statement, all three dimensions, and the competing set with the hire-to-beat named.
Phase 2 — Validate the job with real conversations (mom-test) — GATE
Purpose: Replace opinions with facts — evidence the Phase 1 job is real, painful, and worth paying to solve. Phases 5-10 stay locked until this returns a proceed verdict.
Brief (fallback): Three rules — talk about their life not your idea; ask about specifics in the past not hypotheticals; talk less (they speak 80%). Compliments are not data; only commitments (time, reputation, money) count. A good question could destroy the imagined business.
Invoke: Use the mom-test skill with the job statement and competing alternatives from docs/CUSTOMER.md. Ask for (a) a 10-12 question interview guide obeying the three rules, then later (b) transcript scoring that flags leading questions and zombie leads. Hand the guide to the user and pause with status awaiting-evidence; record the approved guide in docs/CUSTOMER.md under a ### Interview Guide subsection of ## Interview Evidence so it survives the pause.
Decide with the user (on return): Does the evidence confirm the job? Proceed (3+ concrete commitments), revise the job statement (loop to Phase 1), or stop (no pain found — a cheap win).
Artifact: Extend docs/CUSTOMER.md: add ## Interview Evidence (date | who | facts | commitment) and ## Validation Verdict with the decision and reasoning. Update the tracker.
Done when: CUSTOMER.md holds 5+ evidence rows, the verdict is recorded, the user chose proceed / revise / stop, and — on proceed — Phases 5-10 are unlocked.
Phase 3 — Test the riskiest assumption in five days (design-sprint)
Purpose: Before committing months, prove the riskiest part of the concept in one week with five real customer reactions.
Brief (fallback): Five days — Map, Sketch, Decide, Prototype, Test. Pick one target moment (the riskiest step); sketch alone (no group brainstorms); a single Decider breaks ties; build a facade, not working code; test with exactly five target customers. On Friday, shut up and let them struggle — explaining the prototype invalidates the test.
Invoke: Use the design-sprint skill with the validated job and riskiest open question. Ask for the Monday map with sprint questions and target moment, and a Friday five-act interview script that does not explain the prototype. Hand the recruiting brief to the user and pause awaiting-evidence for real sessions; record the approved script and brief under the sprint card in docs/EXPERIMENTS.md so they survive the pause.
Decide with the user: What single assumption to test this week and who is the Decider. On return: does the concept survive — build, fix, or walk away (a one-week win)?
Artifact: Create docs/EXPERIMENTS.md with ## Experiment Cards (EXP-001, type sprint, pre-committed metric, decision rule, result and verdict) and ## Experiment Backlog. Update the tracker.
Done when: EXPERIMENTS.md holds the sprint card with a recorded verdict from five sessions, and the user chose build / fix / walk away.
Phase 4 — Run the loop and pick the smallest MVP (lean-startup)
Purpose: Turn discovery into a repeatable engine of validated learning and ship the smallest MVP that tests the riskiest leap-of-faith assumption.
Brief (fallback): Plan Build-Measure-Learn backward: decide what to learn, then the metric that proves it, then the minimum build. MVP types — smoke test, concierge, Wizard of Oz — each test a dif
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
