Find and qualify evidence-backed potential first customers, early adopters, design partners, or beta users for a startup using recent public pain and buying signals. Use when Codex needs to analyze a product URL or idea, define an ideal customer profile, research public discussions and business pages, identify…
Use for decision-grade startup hypothesis validation: kill/refine ideas, identify ICP, jobs, demand, money signals, wedges, and GTM paths via the bundled Russian research prompt.
Find and qualify evidence-backed potential first customers, early adopters, design partners, or beta users for a startup from recent public signals. Trigger on "find my first customers", "who would buy this", "find early adopters", "find design partners", "find beta users", "find leads for my startup", or when given a…
Extracts what a customer conversation revealed — current behavior, workarounds, quoted proof — then triangulates against tickets, CRM, issues, or the repo. Use when the user wants insights from a call, what it means, whether signal is a pattern, or what ticket to file. "Extract some insights." / "What did we learn?" /…
Turns a customer conversation into one anchor sentence and 4-5 spoken questions — and finds two or three people likely to react strongly when nobody's named. Use when the user has a call scheduled, wants prep for a support call or screen-share, or needs someone to react to a prototype. "Prep me for the Acme call." /…
Pressure-tests product bets, feature requests, and roadmap items against current customer behavior — workarounds, not hypotheticals. Use when the user wants to challenge an idea, decode a feature request, pick a priority, or build conviction on what to ship. "Pressure-test this." / "We need a dashboard." / "Should we…
Surfaces the assumptions a product or strategy depends on, classifies them by criticality and evidence quality, and produces a prioritized test plan. Use when: assumption mapping, identify assumptions, what could go wrong, leap-of-faith assumptions, riskiest assumption test, RAT, assumption inventory, validate before…
Triages a backlog of raw customer feedback into a ranked list of opportunities scored on reach, severity, strategic fit, and confidence. Outputs a prioritized list with explicit "do not act" callouts for vocal-minority signals. Use when: triage feedback, prioritize feature requests, customer feedback backlog, what…
Turn raw research into Jobs-to-be-Done statements showing what users are really trying to accomplish. Use when: extract jobs, jtbd analysis, jobs to be done, what job is the user hiring, underlying user needs.
Synthesize startup customer interview notes, outreach replies, validation calls, and test results into evidence, contradictions, signal strength, and a proceed/park/kill recommendation before v1 scoping, with optional formatted single-file HTML artifact output.
Stress-test a captured startup problem with sharp questions before validation or product scoping, with optional formatted single-file HTML artifact output.
This skill should be used when a founder wants to validate, pressure-test, or kill a startup/product idea before building it — sharpening a hunch into a testable hypothesis, red-teaming it, sizing the market, mapping competitors, designing and synthesizing customer-discovery interviews, and deciding whether the…
This skill should be used when a founder wants to know which startup stage they're actually in, what the goal and exit criteria of that stage are, what failure modes to watch for, or which tool/module to use next — e.g. "what stage am I at", "what should I focus on now", "am I ready for an MVP", "do I have…