Menu
Run a full validation pass on an idea — sharpening, devil's advocate, market sizing, competitor mapping, customer discovery plan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.
Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.
Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
| name | validate |
| description | Run a full validation pass on an idea — sharpening, devil's advocate, market sizing, competitor mapping, customer discovery plan. |
An opt-in rail, not a gate. Use /validate when a bet is expensive, slow, or hard to undo — paid acquisition, a big build, a pivot. For cheap, reversible ideas, just build; the ship is the validation.
Usage: /validate <idea or product name>
Runs the Idea-stage agents in sequence (or parallel where independent):
problem-sharpener — turn the idea into a testable hypothesisdevils-advocate — build the strongest case againstmarket-researcher — TAM/SAM/SOM + trendscompetitor-mapper — landscape by tiercustomer-discovery — interview plan + outreach templatesOutputs go to products/<slug>/ (creating the folder if new).
<idea> to a product slug (existing or new).products/<slug>/ with minimal structure, log in decisions/0001-validation-start.md.factory/playbooks/mvp-stage/fleet-patterns.md):
model_tier.products/<slug>/validation/snapshot.md — the summaryproducts/<slug>/validation/hypothesis.md — sharpened problemproducts/<slug>/validation/devils-advocate.md — kill caseproducts/<slug>/validation/market.md — sizing + trendsproducts/<slug>/validation/competitors.md — landscapeproducts/<slug>/interviews/discovery-plan.md — the planidea-generator or devils-advocate directly, not full validation.