Create · Business

How to Create a New Business with AI Skills

A step-by-step playbook for going from idea to validated, positioned, monetizable business — using AI agent skills drawn from Lean Startup, The Mom Test, JTBD, and more.

18 min read 10 skills Free & open-source
  1. 01 Lean Startup lean-startup Build-Measure-Learn methodology
  2. 02 The Mom Test mom-test Customer conversations that reveal the truth
  3. 03 Jobs to Be Done jobs-to-be-done JTBD framework for product innovation
  4. 04 Design Sprint design-sprint 5-day process for validating ideas through prototyping
  5. 05 Good Strategy Bad Strategy good-strategy-bad-strategy Strategy kernel: diagnosis, guiding policy, coherent action
  6. 06 Blue Ocean Strategy blue-ocean-strategy Create uncontested market space with value innovation
  7. 07 Obviously Awesome obviously-awesome Product positioning: unique value, target customers
  8. 08 $100M Offers hundred-million-offers Grand Slam Offer creation: Value Equation, pricing, guarantees
  9. 09 Monetizing Innovation monetizing-innovation Design the product around validated willingness to pay
  10. 10 Crossing the Chasm crossing-the-chasm Technology adoption lifecycle and go-to-market

Most new businesses do not fail because the founder could not build the thing. They fail because the founder built the wrong thing, for nobody in particular, priced on a guess, and explained in a way prospects never understood. The code worked. The business did not. The expensive mistakes were all made before the first line of code — in the months when nobody was watching and everything felt like progress.

This guide is for the founder standing at exactly that moment: a raw idea, some conviction, and a finite amount of runway and energy. The temptation is to start building immediately, because building feels productive and talking to strangers feels slow. Resist it. The single highest-leverage thing you can do right now is to compress the cycle between I think this is true and I have evidence it is true — and to do that compression across demand, strategy, positioning, and price, not just product.

That is what this stack of ten AI agent skills does. Each one packages a battle-tested business book into something your coding agent can actually run. Used together, they form one continuous workflow: discover the real job customers are trying to get done, talk to them without poisoning the data, prototype and test the riskiest assumption in a week, then — only once demand is real — sharpen your strategy, find uncontested space, nail your positioning, build an offer people feel stupid refusing, price it against validated willingness to pay, and pick the beachhead you will dominate first. The order matters. Demand before building, strategy before scale, price before product.

You will not use all ten in a single afternoon. You will move through them roughly in sequence, looping back as evidence accumulates. By the end you should have something most first-time founders never get: 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. Let’s build it.

You can be wrong about your product in a week, or wrong about your business in a year. Pick the week.

Phase 1 — Find the real job before you fall for your solution

The first mistake is starting with the solution. You have an idea — “an app that does X” — and every subsequent decision quietly bends toward justifying it. The fix is to start one level deeper, with the Jobs to Be Done skill, which is built on a single uncomfortable truth from Competing Against Luck: customers do not buy products, they hire them to make progress in a specific circumstance. Your job is to find that progress before you fall in love with your way of delivering it.

A “job” is not a goal (“be healthy”) and not a task (“click the button”). It is progress in context: When I’m commuting alone, I want something to occupy me and blunt my hunger, so I’m not starving by lunch. Notice that statement never mentions a milkshake — or your product. That is the point. A well-formed job statement (When [circumstances], I want to [progress], so I can [outcome]) is solution-agnostic, which means it survives even when your first idea dies. And every job has three inseparable dimensions: functional (what they need to do), emotional (how they want to feel), and social (how they want to be seen). Miss the emotional and social ones and you will build something that works on a spec sheet and dies in the market.

The other thing JTBD forces you to confront early is your real competition. It is almost never the other apps in your category. It is the spreadsheet, the sticky note, the intern doing it by hand, and — most often — non-consumption, the customer simply doing nothing. If you cannot beat “doing nothing,” no feature will save you. Have your agent map the full competitive set around the job, including the workarounds people have hacked together, because those workarounds are a map of unmet needs.

Prompt

Use the jobs-to-be-done skill to analyze my idea for a tool that helps independent bookkeepers catch billing errors before invoices go out; reconstruct the likely Job to Be Done, write it as a When/I-want-to/so-I-can statement, and lay out all three dimensions — functional, emotional, and social

Jobs to Be Done
Prompt

Use the jobs-to-be-done skill to map every alternative a small bookkeeping firm could hire for this job — spreadsheets, manual double-checking, hiring a junior, and doing nothing — and tell me which competing hire I actually have to beat to win the Big Hire

Jobs to Be Done

Do not skip the emotional and social dimensions thinking they are soft. A founder building invoice software discovers the functional job is “get paid faster” — but the emotional job is “stop feeling like a nag,” and the social job is “look professional to clients.” Those last two are where the differentiated product lives.

Phase 2 — Talk to customers without poisoning the well

Now you need evidence the job is real and painful. This is where almost everyone fails, because almost everyone runs customer conversations that generate cheerful, useless lies. The The Mom Test skill — from Rob Fitzpatrick’s book of the same name — exists to fix this. Its core premise: everyone is lying to you, not maliciously, but because you are asking questions so bad that the only polite answer is a compliment.

The three rules are deceptively simple. Talk about their life, not your idea — never mention your solution until the very end, if at all. Ask about specifics in the past, not hypotheticals about the future (“Tell me about the last time this happened” beats “Would you use a tool that…”). And talk less; aim for them speaking eighty percent of the time. The deepest insight: a question passes the Mom Test only if the answer could destroy your imagined business. “Do you think this is a good idea?” always gets a yes and teaches you nothing. “How are you handling this today, and what does it cost you?” reveals actual behavior and budget.

The currency of these conversations is not enthusiasm — it is commitment. “I’d definitely buy that” costs nothing. An intro, a deposit, a scheduled pilot, a letter of intent: those cost something real, and only those tell you the truth. The worst outcome is not a “no.” It is the polite zombie lead who loves your idea and will never, ever buy. Have your agent build you an interview guide that obeys the rules, then — crucially — review your actual transcripts for where you led the witness.

Prompt

Use the mom-test skill to write me a 12-question customer discovery interview guide for solo bookkeepers that obeys the three Mom Test rules — every question must be about their past behavior and current workarounds, never about my idea, and none can be answerable with a meaningless yes

The Mom Test
Prompt

Use the mom-test skill to score each of my last three customer calls (notes pasted below) against the Mom Test principles, flag every leading question and every compliment I accepted as data, and tell me which 'commitments' were real versus zombie-lead politeness

The Mom Test

If you walk out of a meeting feeling great but holding no concrete facts and no commitment, you ran a pitch, not a discovery conversation. Run it again, and this time do not mention what you are building.

Phase 3 — Test the riskiest assumption in five days

You now have a hypothesis grounded in real conversations. Before you commit months to building, prove the riskiest part of it in a single week. The Design Sprint skill packages the Google Ventures five-day process — Map, Sketch, Decide, Prototype, Test — and it does one thing supremely well: it replaces months of debate with a real decision backed by five real customer reactions.

The structure is fixed for a reason. Monday you map the problem and pick one target moment in the customer journey — the riskiest, highest-stakes step. Tuesday everyone sketches solutions alone (no group brainstorms; they produce mush). Wednesday you decide, with a single Decider breaking ties so you do not design by committee. Thursday you build a facade — not working code, just something that looks real enough to provoke an honest reaction. Friday you put it in front of five target customers and watch them struggle. Five is the magic number: patterns emerge by the third or fourth interview, and returns flatten after five.

The hardest discipline on Friday is to shut up and let them struggle. The moment you explain the prototype, you have invalidated the test — because customers will not have you sitting beside them when they use the real thing. Watch where they get confused. That confusion is your roadmap.

Prompt

Use the design-sprint skill to plan a five-day design sprint to test whether bookkeepers will trust an automated error-catching pass over invoices they prepared by hand; give me the Monday map with sprint questions, a target moment on the customer journey, and a Friday five-act interview script that does not explain the prototype to the user

Design Sprint

A design sprint will not tell you the whole business works. It will tell you, cheaply and fast, whether the core concept survives contact with five real humans — and whether you should build it, fix it, or walk away. Walking away after one week is a win; you just saved yourself a year.

Phase 4 — Run the loop and pick the smallest possible MVP

Discovery and a sprint give you a strong start. Building a real business means turning that into a repeatable engine of validated learning — and that is the Lean Startup skill, drawn from Eric Ries’s book. Its central machine is the Build-Measure-Learn loop, and its central instruction is to plan that loop backward: first decide what you need to learn, then what metric proves it, then build the absolute minimum that produces that metric.

That minimum is the MVP, and it is almost always smaller and more embarrassing than you think. The skill catalogs the types: a smoke test (a landing page and a signup button, no product — how Dropbox validated demand with a video); a concierge MVP (you deliver the service manually, pretending it is automated); a Wizard of Oz (a polished front end with a human frantically working the back end). Each tests a different leap-of-faith assumption — the assumptions that, if wrong, kill the business. You test the riskiest one first, never the easiest.

And you measure with actionable metrics, not vanity ones. Total signups always goes up and tells you nothing; the signup-to-active conversion rate tells you whether anyone cares. Cohort retention tells you whether the product is actually improving. Set your pivot-or-persevere criteria before you run the experiment, so that week-one panic does not get to rewrite your strategy.

Prompt

Use the lean-startup skill to read my full feature wish list for the invoice error-checker (pasted below), identify my single riskiest leap-of-faith assumption, then design the smallest MVP that tests it — pick a type (smoke test, concierge, or Wizard of Oz) and write a Build-Measure-Learn experiment card with the hypothesis, the one actionable metric, and the success threshold

Lean Startup
Prompt

Use the lean-startup skill to define the pivot-or-persevere criteria for this experiment before we run it — what cohort retention and activation numbers at day 30 would mean persevere, what would mean pivot, and which type of pivot would be on the table if the value hypothesis fails

Lean Startup

Pick one engine of growth — sticky, viral, or paid — and optimize that one. Running all three at once dilutes your focus and muddies your learning. Most businesses at this stage should obsess over the sticky engine: get retention above churn before you spend a dollar acquiring anyone.

Phase 5 — Turn ambition into an actual strategy

By now you have evidence demand is real. The danger shifts: you have a working idea but no real strategy, just a list of goals dressed up as one. The Good Strategy Bad Strategy skill, from Richard Rumelt’s book, is the antidote. Its core claim is sharp: “grow 40 percent, expand to Europe, become the category leader” is not a strategy. It is a wish list. A goal names an ambition; a strategy explains how you will achieve it given the actual obstacles in your way.

Real strategy has a kernel of three parts. A diagnosis that names the single critical challenge and simplifies a messy reality into one thing that matters. A guiding policy — the overall approach you have chosen — that is a genuine choice with losers; if your nearest competitor could paste it into their deck unchanged, it is a platitude, not a policy. And coherent actions: coordinated, resourced steps that each reinforce the others, every one with an owner and a date. Most failed strategies skip the diagnosis entirely and leap from ambition straight to a laundry list of disconnected initiatives.

The skill is just as good at detecting bad strategy as writing it. Run your plan through the four hallmarks — fluff (buzzwords that collapse to nothing when restated plainly), failure to face the real challenge, goals masquerading as strategy, and dog’s-dinner objective lists — and you will see exactly where it is hollow. The source of power that matters most for a new business is concentration: pick one pivot point and pour everything past the threshold where results become visible, instead of spreading thin effort across five fronts and winning none.

Prompt

Use the good-strategy-bad-strategy skill to audit my one-page plan for the invoice error-checker (pasted below) against the four hallmarks of bad strategy, then rewrite it as a proper kernel — a one-paragraph diagnosis of my single critical challenge, a guiding policy that rules whole classes of action out, and three coherent actions with owners — plus an explicit list of what I am choosing NOT to do

Good Strategy Bad Strategy

The hardest part is choosing, because every real choice creates losers. But that is the work. A strategy that pleases every stakeholder concentrates nothing and wins nowhere.

Phase 6 — Find the uncontested space instead of fighting for scraps

Strategy tells you how to win. The next question is where to win — and the most common error is to compete head-on in a bloody, crowded market on the same factors as everyone else. The Blue Ocean Strategy skill, from Kim and Mauborgne’s book, offers the alternative: stop fighting for share of an existing market (a “red ocean”) and create uncontested space (a “blue ocean”) where competition is, for a while, irrelevant.

The engine is value innovation — the pursuit of differentiation and low cost simultaneously, which competitors assume is impossible. You achieve it with the Four Actions Framework, the ERRC grid: which factors the industry takes for granted can you Eliminate? What can you Reduce well below the standard? What should you Raise well above it? And what can you Create that the industry has never offered? Eliminating and reducing over-served factors cuts your costs at the same time raising and creating lifts buyer value — so value rises more than cost, breaking the trade-off. Plot it on a strategy canvas and a genuinely different offering shows up as a curve that diverges from everyone else’s instead of tracing the same shape.

Crucially, blue oceans are built by converting non-customers, not by stealing rivals’ customers. Map the three tiers — the soon-to-be (on the edge of your market, ready to jump), the refusing (who looked and consciously said no), and the unexplored (who never considered your category at all) — and find the common barrier whose removal would unlock a wave of new demand.

Prompt

Use the blue-ocean-strategy skill to build a strategy canvas from the six tools bookkeepers currently use for invoice review and the factors they all compete on (pasted below), then apply the ERRC grid to design a value-innovation move I can make with limited resources — what to eliminate and reduce to cut cost while I raise and create on the factors that actually matter to my buyer

Blue Ocean Strategy

Do not eliminate factors customers genuinely value — especially anything touching trust, security, or accuracy in a finance product. Test your assumptions about what is over-served before you cut it.

Phase 7 — Position so prospects instantly get it

You can have a great product in great market space and still lose, because prospects do not understand what you are in thirty seconds. The Obviously Awesome skill, from April Dunford’s book, fixes that — and its central reframe is the one most founders miss: positioning is not messaging, positioning is context. It is the frame of reference you put customers in so your strengths look obvious. Customers always evaluate you relative to alternatives; there is no absolute perception of “expensive” or “powerful,” only relative to what they are comparing you against. Choose that comparison deliberately.

The process is five steps, and it is the same one whether you have a research budget or not. First, identify your true competitive alternatives — what customers would actually use if you vanished (usually a spreadsheet or “doing nothing,” not a named competitor). Second, list your unique attributes — what you have that those alternatives do not, things that survive the “only we” test. Third, map each attribute to the value it delivers by asking “so what?” until you reach something the customer genuinely cares about. Fourth, define your best-fit customers — the tightest possible description of who cares most, identifiable by job title and company traits, never “everyone.” Fifth, choose the market category that makes your value obvious: compete in an existing one, carve a subcategory, or — rarely, only with traction to spare — create a new one and pay the education tax of teaching the market what it is.

Prompt

Use the obviously-awesome skill to walk me through the full Obviously Awesome positioning exercise for my invoice error-checker — list the real competitive alternatives (including spreadsheets and doing nothing), identify my unique attributes, run the so-what test to map them to value themes, define my best-fit customer down to firm size and role, and recommend whether to position in an existing category or a subcategory

Obviously Awesome
Prompt

Use the obviously-awesome skill to fill out the positioning canvas for me and write a one-line internal positioning statement in the form 'For [best-fit customer], we are the [category] that [key value]' that my whole team can repeat identically

Obviously Awesome

Test the result the cheap way: say your category and one-liner to someone outside the business and watch their face. If they get it in the first thirty seconds, the category is right. If they squint, no amount of clever copy will rescue you — fix the positioning, not the words.

Phase 8 — Build an offer people feel stupid refusing

Positioning makes prospects understand you. An offer makes them buy. The $100M Offers skill, from Alex Hormozi’s book, is built on a claim worth internalizing: the offer is the number one lever in the business. A great offer sells despite mediocre marketing; the best marketing in the world cannot save a weak one. So before you optimize a funnel or run an ad, fix the offer.

The heart of it is the Value Equation: value equals dream outcome times perceived likelihood of achievement, divided by time delay times effort and sacrifice. Maximize the top, minimize the bottom. People buy outcomes, weighed against how confident they are of getting them and how long and hard the path looks. A guarantee raises perceived likelihood and lowers risk at the same time. Faster results and less effort command premium prices. From there you assemble a Grand Slam Offer — a complete package of core offer, named bonuses (each killing a specific objection, each with a defensible dollar value), a risk-reversing guarantee, and ethical scarcity — so that no competitor offers the same combination and price comparison becomes impossible. And you name it with the MAGIC formula: a magnetic reason, the avatar, the goal, a time frame, and a container word.

Fix the offer before you fix the funnel. A category-of-one offer with crude marketing beats a commodity with a beautiful one.

Prompt

Use the hundred-million-offers skill to turn my invoice error-checker into a Grand Slam Offer for solo bookkeeping firms using the Value Equation — maximize the dream outcome and slash time-delay and effort, then stack three named bonuses that each kill a specific objection, design a risk-reversing guarantee, add ethical scarcity, and name the whole offer with the MAGIC formula

$100M Offers

Keep every dollar value honest and every guarantee genuinely honorable — a bonus priced at what nobody would actually pay, or a guarantee buried in fine print, destroys trust the moment it is discovered. The goal is to be a category of one, not to inflate a fake value-price gap.

Phase 9 — Price against validated willingness to pay

Here is where most founders quietly torch their economics: they build the whole product, then pick a price at launch by copying a competitor or marking up their costs. The Monetizing Innovation skill, from Ramanujam and Tacke of Simon-Kucher, inverts that. Its core instruction — design the product around the price — means you have the willingness-to-pay conversation while the product is still a concept, because the price customers will accept is the earliest, clearest signal of whether the thing is worth building at all. Seventy-two percent of new products miss their revenue targets, and treating price as an afterthought is the common root cause.

You cannot ask customers to name a perfect price, but they reliably reveal a range. Ask what feels acceptable, what feels expensive, and what is prohibitively expensive. Ask purchase probability on a one-to-five scale and trust only the top box. Then watch for the four monetization failures: feature shock (cramming so much in that value drowns in complexity), minivation (a 10x product priced ten percent above what it replaces — a win rate near 100 percent with no price pushback is its telltale sign), the hidden gem (a valuable byproduct nobody monetizes), and the undead (a product nobody wants, kept alive on sunk cost). Segment customers by what they value and will pay — never by demographics — and package with the leader / filler / killer model: classify every feature, build good-better-best tiers around the leaders that drive purchase, design the middle tier first because most buyers land there, and pull “killer” features (the ones that reduce willingness to pay for a segment forced to fund them) out into add-ons.

Prompt

Use the monetizing-innovation skill to design our monetization before we finish building — write a willingness-to-pay interview script for my next ten bookkeeper calls using the acceptable / expensive / prohibitive price questions, then classify my planned features into leaders, fillers, and killers and draft a good-better-best tier structure with the middle tier designed to be the one most buyers choose

Monetizing Innovation
Prompt

Use the monetizing-innovation skill to tell me which of the four monetization failures my current pricing is drifting toward given that my win rate is near 100 percent and no prospect ever pushes back on price, and recommend the specific countermeasure

Monetizing Innovation

Pick your price metric — per seat, per invoice checked, per error caught — before you pick the price level, because the metric decides whether revenue grows automatically as customers get more value. A metric that tracks delivered value is the difference between a business that compounds and one that caps out at renewal.

Phase 10 — Pick the beachhead you will dominate first

You have a validated, positioned, priced offer. The final question is go-to-market, and the Crossing the Chasm skill, from Geoffrey Moore’s book, names the trap that kills technology businesses with early traction: the chasm between the visionary early adopters who love new things and the pragmatist early majority who just want something that works. The two groups want opposite things — what wins the visionary actively repels the pragmatist — so the strategy and the whole product both have to change to cross.

The way across is not to be everything to everyone; that is how you stall in the chasm. It is to pick a single, narrow beachhead segment — “solo bookkeeping firms that bill more than fifty invoices a month,” not “finance teams” — and utterly dominate it. A good beachhead has an urgent, expensive pain, is reachable through known channels, has customers who talk to each other (so references spread), and is small enough to own yet big enough to matter. Then you assemble the whole product for that one segment: not just your core technology, but the integrations, onboarding, support, and partner pieces a pragmatist needs before they will buy. References are the currency here — pragmatists will not move without proof from peers — and your positioning shifts from “revolutionary” (which terrifies them) to “proven solution for your specific problem.” Win the beachhead, then knock down adjacent segments one at a time, bowling-pin style.

Prompt

Use the crossing-the-chasm skill to help me choose a single beachhead segment for the invoice error-checker — score three candidate niches of bookkeeping firms against pain, reachability, word-of-mouth, and whether I can dominate it, then map the whole-product requirements (integrations, onboarding, references) a pragmatist in that segment needs before they will buy

Crossing the Chasm

Resist the urge to keep your options open by chasing several segments at once. Concentration is the whole game: own one segment completely, get your lighthouse references, and let that dominance pull you into the next.

Your checklist

  • Write the Job to Be Done as a When [circumstances], I want to [progress], so I can [outcome] statement — with no mention of your product
  • Map the full competitive set around the job, including workarounds and non-consumption, and name the hire you must beat
  • Run at least ten Mom Test conversations about past behavior, and review your transcripts for leading questions
  • Collect a real commitment (time, reputation, or money) from each promising conversation — no zombie leads
  • Run a five-day design sprint on the riskiest part of the concept; test with five target customers
  • Identify your single riskiest leap-of-faith assumption and pick the smallest MVP that tests it
  • Define actionable metrics and pivot-or-persevere criteria before running the experiment
  • Write a strategy kernel: diagnosis, guiding policy, coherent actions — plus an explicit no-list
  • Build a strategy canvas and an ERRC grid to find an uncontested value-innovation move
  • Complete the five-step positioning exercise and test your one-liner on an outsider in 30 seconds
  • Assemble a Grand Slam Offer: core, named bonuses, risk-reversing guarantee, ethical scarcity, MAGIC name
  • Run willingness-to-pay interviews; classify features as leader / filler / killer; design good-better-best tiers
  • Choose your price metric before your price level
  • Select one beachhead segment and define its whole product

Common mistakes

Building before validating. The fatal one. You will be tempted to skip Phases 1 through 4 because building feels like progress and talking to strangers feels slow. But every hour of building before you have evidence is an hour bet on an unvalidated guess. Use the smallest possible MVP — a smoke test or a concierge service — to buy that evidence before you write real code.

Pitching during discovery. If you mention your idea in a customer interview, you have ended the discovery and started a sales pitch — and the data goes from honest to flattering and worthless. Keep the conversation entirely about their life and past behavior. Save your idea for the very end, if you mention it at all.

Mistaking compliments and signups for validation. “That’s a great idea!” and a free email signup both feel like progress and both contain almost zero information about whether anyone will pay. Chase commitment instead: a deposit, a pre-order, a scheduled pilot, an active paying user. Watch what people do, not what they say.

Confusing goals for strategy. “Grow 40 percent and become the leader” is a wish, not a plan. If your document never names the one critical challenge you face, you have no strategy to evaluate or improve. Write the diagnosis first, always.

Positioning for everyone. A product “for everyone” is compelling to no one. The broadest possible target dilutes your differentiation until prospects feel it was built for someone else. Tighten your best-fit definition until it is almost uncomfortably narrow, then go narrower.

Pricing on cost or competitors. Both anchor on the wrong thing — your costs measure your business, a competitor’s price measures their strategy; neither measures what your customer values. Price from validated willingness-to-pay ranges, and decide your price metric before your price level.

Trying to cross the chasm on multiple fronts. Early traction tempts you to chase every interested segment. Spreading thin means you dominate nothing and accumulate no references — and pragmatists buy on references. Pick one beachhead and own it completely before expanding.

Frequently asked questions

In what order should I actually use these skills?

Roughly the order above, but it is a loop, not a straight line. Start with Jobs to Be Done and The Mom Test to find and validate the real problem. Use Design Sprint and Lean Startup to test the riskiest assumption cheaply. Once demand is real, sharpen the business with Good Strategy Bad Strategy and Blue Ocean Strategy, then make the market understand and want you with Obviously Awesome, $100M Offers, and Monetizing Innovation. Finish with Crossing the Chasm to plan go-to-market. Expect to loop back — a Mom Test conversation in Phase 2 may send you back to rewrite the job statement from Phase 1, and that is the process working.

Do I really need all ten, or can I just pick a few?

You can start a business with two or three, but the failures cluster predictably around the ones founders skip. Skip discovery and you build the wrong thing. Skip pricing work and you torch your margins. Skip positioning and prospects never grasp what you are. The minimum honest stack is discovery (jobs-to-be-done plus mom-test), one validation skill (lean-startup or design-sprint), one positioning skill (obviously-awesome), and one pricing skill (monetizing-innovation or hundred-million-offers). The rest sharpen the edges and become essential the moment you start to scale.

How do I install and invoke a skill?

Install any skill from your terminal with npx skills add wondelai/skills/<slug> --global — for example, npx skills add wondelai/skills/mom-test --global. Then you invoke it by writing a prompt that tells your agent to use it, exactly like the prompt blocks throughout this guide: paste in your real artifacts (your interview notes, your feature list, your pricing page) and ask the skill to do its work on them. The more concrete your inputs, the better the output.

Can my AI agent talk to customers for me?

No, and you should not want it to. The skills design your interview guides, score your transcripts for bias, structure your experiments, and analyze the results — but the actual conversations and the real commitments have to come from you. The Mom Test only works on genuine human behavior; an agent role-playing a customer will cheerfully confirm whatever you hope is true. Use the agent to prepare and to process, then go talk to real people.

What if my design sprint or MVP says the idea does not work?

Then it just did its job, cheaply. A failed five-day sprint or a smoke test that nobody signs up for has saved you months and a great deal of money. Feed the result back into Lean Startup and decide between pivot and persevere against the criteria you set in advance. Successful startups commonly pivot one to five times before they find product-market fit — the skill catalogs the types (zoom-in, customer segment, business architecture, and more) so you change direction deliberately instead of flailing.

Start with one conversation

The whole stack reduces to one principle: earn your evidence before you spend your runway. You do not need to run all ten skills this week. You need to run the first one today.

Install the discovery skills and write your first Mom Test interview guide:

npx skills add wondelai/skills/mom-test --global
npx skills add wondelai/skills/jobs-to-be-done --global

Then ask your agent to build you an interview guide, go have five honest conversations this week, and let what you hear — not what you hoped — decide what you build next. Add the strategy, positioning, offer, and pricing skills as you move from “is this real?” to “how do I win?”

Once you have customers and the question shifts from creating a business to expanding one, continue with Grow an Existing Business with AI Skills. And if your validated idea needs software built around it, the companion playbook is Create a New App with AI Skills. Browse the full library and install what you need with npx skills add wondelai/skills --all --global.

Get all 50 skills, free

Open-source, MIT-licensed, and ready in 30 seconds.

npx skills add wondelai/skills --all --global