Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Data & analytics

grow-business

Guided journey from a business with lucky months to a repeatable growth engine that produces a forecast. Orchestrates nine skills phase by phase - one-page-marketing, hundred-million-offers, predictable-revenue, contagious, influence-psychology, crossing-the-chasm, cold-start-problem, lean-analytics, negotiation - asking the user questions at every decision point and recording results in the project docs/ folder (MARKETING.md, OFFER.md, METRICS.md, GROW-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a marketing and sales system, manufacture predictable pipeline, engineer word-of-mouth and referrals, or says ''revenue is real but lumpy and I need growth that repeats''. If the offer, retention, or operations underneath are broken, run improve-business first; with no paying customers yet, start with create-business; when the product itself must carry the growth loops, use grow-app. For one framework in isolation, invoke that skill directly.

wondelai · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add wondelai/skills --skill grow-business

About this skill


name: grow-business description: 'Guided journey from a business with lucky months to a repeatable growth engine that produces a forecast. Orchestrates nine skills phase by phase - one-page-marketing, hundred-million-offers, predictable-revenue, contagious, influence-psychology, crossing-the-chasm, cold-start-problem, lean-analytics, negotiation - asking the user questions at every decision point and recording results in the project docs/ folder (MARKETING.md, OFFER.md, METRICS.md, GROW-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a marketing and sales system, manufacture predictable pipeline, engineer word-of-mouth and referrals, or says ''revenue is real but lumpy and I need growth that repeats''. If the offer, retention, or operations underneath are broken, run improve-business first; with no paying customers yet, start with create-business; when the product itself must carry the growth loops, use grow-app. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.1"

Grow a Business

You already have the hard part: a product people pay for. Revenue is real but lumpy — a good month came from a conference you happened to attend or a referral that happened to land, and none of it repeats on demand. This journey turns that traction into a repeatable growth engine across nine phases: a marketing map, an irresistible offer, an outbound motion, engineered word-of-mouth, persuasion on every surface, a mainstream go-to-market, a compounding network, one honest metric, and the discipline to hold price. It is interactive — the agent asks before every decision — and resumable, because every decision and asset is recorded in docs/. Install the whole stack at once with npx skills add wondelai/skills --all --global, or let each phase pull its skill on demand.

Core Principle

Build a repeatable growth engine: each phase produces an asset the next phase consumes — offer feeds pipeline, pipeline feeds word-of-mouth, metrics keep it honest. The order is load-bearing; a skipped Phase 1 leaves the later phases with no shared target. This skill sequences the phases, asks the decision questions, and records the answers. The constituent skills carry the method — invoke them rather than improvising their frameworks.

The offer comes before every channel on purpose: sending traffic to a weak offer is the most expensive mistake in growth, so Phase 2 is fixed before outbound, virality, or repositioning turn on.

Journey Map

PhaseSkillQuestion it answersArtifact
1one-page-marketingWhich niche, and which square of the machine is empty?Creates docs/MARKETING.md
2hundred-million-offersWhy should they buy this instead of the alternative?Extends docs/OFFER.md
3predictable-revenueHow do we manufacture pipeline on demand?Extends docs/MARKETING.md
4contagiousWhy would anyone share this?Extends docs/MARKETING.md
5influence-psychologyWhy do they say yes on the page?Extends docs/OFFER.md
6crossing-the-chasmHow do we reach the mainstream buyer?Extends docs/STRATEGY.md + docs/CUSTOMER.md
7cold-start-problemHow does the network do the acquiring?Extends docs/MARKETING.md
8lean-analyticsWhich one number tells us it is working?Extends docs/METRICS.md
9negotiationHow do we capture the value instead of discounting it?Extends docs/OFFER.md

Four of the nine phases write to MARKETING.md — the flagship this journey creates. OFFER.md, STRATEGY.md, METRICS.md, and CUSTOMER.md are extended, so files a prior create-business journey already owns are reused and augmented, never overwritten.

The tracker docs/GROW-BUSINESS-PLAN.md is private to this journey and never shared with another; it is the resume point that carries state across sessions.

Operating Rules

  1. Resume first. Before anything else, read docs/GROW-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/GROW-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 / defer — phases marked GATE may be deferred, never skipped. Mark the phase in-progress on proceed. Done when the user chose.
  4. 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.
  5. 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.
  6. 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.
  7. 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
Read the complete source ↗