Menu
Plan customer discovery — define target profile, build prospect list, draft interview script, set up outreach + scheduling logistics.
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 | customer-discovery |
| description | Plan customer discovery — define target profile, build prospect list, draft interview script, set up outreach + scheduling logistics. |
| model_tier | sonnet |
User has a sharpened problem hypothesis and is ready to talk to humans. They ask: "how do I find people to interview?", "help me plan customer discovery for X", "draft outreach for Y".
A discovery plan saved to products/<name>/interviews/discovery-plan.md:
## Discovery Plan — <product/idea>
### Target profile (be precise)
- Role / title: <specific>
- Company / context: <specific>
- Team size: <range>
- Seniority: <IC / manager / VP / C-suite>
- Acuteness signal: <how to tell they have this problem badly>
### Where they congregate (top 5 reachable channels)
1. <community / forum / LinkedIn group / Slack workspace> — URL
2. ...
### Prospect list strategy
- How to source: <Apollo / LinkedIn Sales Nav / scrape X / cold from Reddit threads>
- Initial batch size: 50–80
- Outreach format: <DM / email / cold call / community post>
### Interview script (15-min default)
1. **Warm-up** (2 min): "Tell me about your role and a typical week."
2. **Past-behavior probe** (5 min): "Tell me about the last time you dealt with <problem>. Walk me through it."
3. **Current solution** (3 min): "What did you try? What worked? What didn't?"
4. **Workaround cost** (2 min): "How much time/money does this currently cost you?"
5. **Magic wand** (2 min): "If you could wave a wand, how would this look?"
6. **Close** (1 min): "Who else has this problem? Mind connecting me?"
### Don't ask (Mom Test violations to strike out)
- ❌ "Would you use a product that does X?"
- ❌ "Would you pay $Y for this?"
- ❌ "Do you think this is a good idea?"
- All future-hypothetical questions.
### After every 5 interviews
Run `agents/idea/interview-synthesizer/` on the batch.
problem-sharpener output (or ask user for it).factory/playbooks/idea-stage/mom-test.md.products/<name>/interviews/outreach-templates.md.Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:
problem-sharpener — never build a discovery plan on a vague hypothesis; a precise plan for an imprecise problem just finds the wrong people faster.products/<name>/interviews/discovery-plan.md (+ optional outreach-templates.md); raw interview notes accumulate in products/<name>/interviews/raw/, one file per interviewee.factory/playbooks/idea-stage/mom-test.mdfactory/playbooks/launch-stage/cold-outreach-templates.md (just the structure)