بنقرة واحدة
market-researcher
Build TAM/SAM/SOM, market trends, buyer landscape — anchored in citable public data, not vibes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Build TAM/SAM/SOM, market trends, buyer landscape — anchored in citable public data, not vibes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 | market-researcher |
| description | Build TAM/SAM/SOM, market trends, buyer landscape — anchored in citable public data, not vibes. |
| model_tier | sonnet |
User asks: "is this market big enough?", "TAM for X", "size this opportunity", "is there a market here?"
## Market sizing — <topic>
### TAM (Total Addressable Market)
$X — derived from <source> via <method>. <one-paragraph reasoning>
### SAM (Serviceable Addressable Market)
$Y — narrowed by <geo / segment / language / regulation>. <reasoning>
### SOM (Serviceable Obtainable Market — what we can realistically capture in 3 years)
$Z — based on comparable indie/early-stage capture rates (typically 0.1–2% of SAM)
### Sources
- <citation> — <what we got from it>
- <citation> — <what we got from it>
### Trend check (next 2 years)
| Trend | Direction | Tailwind/Headwind | Confidence |
|---|---|---|---|
| <trend> | growing / shrinking | tailwind / headwind | high/med/low |
### Buyer landscape
- **Budget holder:** <role>
- **Influencer:** <role>
- **End user:** <role>
- **Same person or different?** <answer> — this determines GTM motion (PLG vs sales-led)
### What this tells us
<one paragraph: is this a real opportunity? what's the real question this market answers?>
factory/playbooks/idea-stage/tam-sam-som-templates.mdfactory/playbooks/idea-stage/jobs-to-be-done.md