Turn a feature drop's pitch summary into a presentation-deck PDF — a bold, type-driven slide deck rendered from `docs/#NNNN-<slug>-pitch.md`, structured Problem → Solution → Impact for a 3–5 minute pitch. Use whenever the user wants to "make a pitch deck", "turn the pitch into a PDF", "create a presentation / slides", "build the deck for
Draw an Ash-Maurya Lean Canvas (10 boxes) for an idea by reading its `#NNNN-<slug>.md` files from `workflow/ideas/`, `workflow/approach/`, and `workflow/marketing/`, synthesizing each cell, then rendering a PNG into `docs/` via the `tldraw` MCP server. Use whenever the user asks to "draw the canvas", "render a lean canvas", "make a business canvas", "visualize idea
Drive a real browser through an MVP's happy-path demo flow with the Playwright MCP, then verify the runtime checks that code can't prove on its own — the count-up that should land on the right number, the streak that should tick, the "money moment" that should complete. Reads plans/{id}-plan-root.md's "Demo flow" as the script, walks each step in Chromium, screenshots it, and writes a pass/fail report to reports/. Use right after `mvp-execute` finishes a build, or whenever the user says "walk the demo", "play through the happy flow", "verify the demo in the browser", "drive the demo with Playwright", "check the [?] runtime items", "/playwalkthrough {id}", or wants the founder's 5-minute pitch path clicked through end-to-end before they present. This is how the deferred `[?]` done-when boxes from a build get resolved into real pass/fail — don't leave them to the human's eyeballs when a browser can confirm them.
Drill a pre-launch / first-1000-users marketing plan by relentlessly pinning down a single best channel, paid ads vs influencer vs founder-led vs organic, a real budget and timeline, and a 30-day action list. Use when the user mentions a launch plan, go-to-market, GTM, marketing strategy, "how do I get my first users", "should I run Meta/TikTok/Google ads", "should I hire an influencer", "which platform should I use", "how do I grow this", or right after the `mvp/` is built and before they ship. Push back on hand-wavy answers — "we'll do all the platforms", "go viral", "millennials" — and refuse to leave the user with a five-channel scattergun plan.
Walk an MVP build plan to completion — read plans/{id}-plan-root.md, execute the phase files in plans/todo/{id}-*.md in dependency order, ship each phase to plans/done/ as it lands. Use whenever the user wants to "build the MVP", "execute the plan", "run the build", "ship phase NN", "make the demo work", or follow up an `mvp-plan` session with actual code. Spawns `phase-executor` sub-agents — fans out parallel-safe phases concurrently, pauses between groups so the user can verify the dev server. Pitch-demo scope only — happy-path React + RR + Zustand, no auth/deploy/tests.
Plan an MVP build phase-by-phase from an idea's workflow evidence. Use this skill whenever the user wants to turn a validated idea into a buildable MVP plan, asks to "plan the build", "break this into phases", "plan
Build a hunt plan for unsolicited demand evidence — where to find people already complaining about a problem in their own words (Reddit, Twitter/X, Hacker News, niche Discords, G2/Capterra reviews of adjacent products, YouTube comments, Indie Hackers, plus traditional/offline channels), what queries to run, and how to run client interviews or surveys without leading questions. Use when the user wants to validate demand, find proof people already have this problem, asks "where do real users complain", "how do I find evidence for X", or right after a `validate-idea` session before any building starts.
Stress-test a business idea by drilling into the underlying problem, target user, and willingness to pay before any code is written. Use when the user wants to validate an idea, says "validate this idea", "is this worth building", "should I build this", drops a new product/business concept, or mentions an `workflow/ideas/` entry.