create-business

What it does

Guides a user from a raw idea to a defendable, positioned, priced business through ten sequential phases, each handled by a specific skill (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). It prompts the user at every decision point, records results in docs/ (CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md), and supports resuming across sessions by storing state in docs/. It instructs to read and update project artifacts before moving to the next phase, and to invoke the phase-specific skill by its slug. If a phase skill is unavailable, it offers a fallback to install it via a CLI command and, if declined, to proceed with a minimum viable method described in the phase brief. It emphasizes demand before build, strategy before scale, and price before product, and it requires the human to conduct customer interviews rather than simulating customers.

How it works

• Phase 1 (Find the real job): invoke jobs-to-be-done with the raw idea and customer guess from Intake; determine the real job statement and competing alternatives; create docs/CUSTOMER.md with sections for Job Statement, Job Dimensions, and Competing Alternatives.
• Phase 2 (Validate with real conversations): invoke mom-test with the Phase 1 job and competing alternatives; create an Interview Guide and record interview evidence in docs/CUSTOMER.md under an Interview Evidence section; decide to proceed, revise, or stop.
• Phase 3 (Test the riskiest assumption): invoke design-sprint with the validated job and riskiest open question; create docs/EXPERIMENTS.md with an Experiment Card and an Experiment Backlog; record a verdict and unlock further phases if proceeding.
• Phase 4 (Lean startup MVP): invoke lean-startup with the feature wish list; define the MVP, Build-Measure-Learn, and pivot/persevere thresholds; update docs/PRODUCT.md and docs/EXPERIMENTS.md accordingly.
• Phase 5 (Strategy kernel): invoke good-strategy-bad-strategy to produce a diagnosis, guiding policy, and coherent actions; create docs/STRATEGY.md with sections for Diagnosis, Guiding Policy, Coherent Actions, and No-List.
• Phase 6 (Blue ocean): invoke blue-ocean-strategy using competing alternatives and the kernel; extend docs/STRATEGY.md with Strategy Canvas & ERRC Grid.
• Phase 7 (Obviously-awesome): invoke obviously-awesome to position the offering in 30 seconds; update docs/POSITIONING.md accordingly.
• Each phase uses a documented artifact workflow, requiring the user’s decision, and updates to the project docs accordingly.

When to use it

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 or improve-business for later stages. For building the product itself, use create-app or create-website. For a single framework in isolation, invoke that phase directly.

What it can touch

The skill invokes specific phase skills by slug (e.g., 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). It writes to docs/ artifacts, including CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md, EXPERIMENTS.md, PRODUCT.md, STRATEGY.md, and others as the journey evolves.

Caveats

• Requires the toolkit of ten phase skills; if a phase skill is unavailable, the system prompts installation via the CLI: npx skills add wondelai/skills/<slug> --global.
• All state and artifacts live in docs/ to allow resumable sessions across restarts.
• Guidance is decision-oriented and does not simulate real customers; interviewing guides and transcripts are prepared for human-led validation.