Skill detail
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills across JTBD, mom-test, lean startup, strategy, offers, and pricing.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- name: 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 1. **Resume first.** Before anything else, read `docs/CREATE-BUSINESS-PLAN.md` and 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. 2. **Intake on first run only.** No tracker: run the Intake below, then create `docs/CREATE-BUSINESS-PLAN.md` with every phase statused `pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason`. Done when the tracker exists and the user has confirmed the phase plan. 3. **Phase entry.** Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defeRead the full source on GitHub (opens external page)