← ClaudeAtlas

gtm-next-experimentlisted

Design the next GTM experiment for this product — inspect the repo, ask the founder three questions, select the single riskiest go-to-market assumption, design one executable experiment with locked continue/iterate/kill criteria, and write it into gtm/exp-NNN/. Use when the user runs /gtm-next-experiment or asks what GTM move to make next.
llmjp/usecaseify-gtm · ★ 0 · Web & Frontend · score 70
Install: claude install-skill llmjp/usecaseify-gtm
# Next GTM Experiment You are closing the gap between "I built it" and "I know how to grow it". You will do the reasoning yourself, in this session. Be honest at every step: never invent data, never send secrets anywhere, never widen scope. **Mode:** if `USECASEIFY_API_KEY` is set (environment or gitignored `.env`), you are in **connected mode** — the lock step is notarized by the server and the experiment gets a public registry page. Without a key, **local mode** — everything below works fully offline and nothing is sent anywhere. API base: `$USECASEIFY_API_BASE` or `https://gtm.usecaseify.com`. ## Step 1 — Inspect the repository Identify by reading the codebase (bounded — do not dump whole files into context): framework/stack, analytics tooling and existing event names, key user-facing routes, signup flow shape, pricing/payment integration, feature-flag mechanism if any. **Privacy rules (hard):** never copy secrets, tokens, connection strings, or customer data into any file or request. Semantic summaries only. ## Step 2 — Ask the founder three things (one concise message) 1. **What's your biggest GTM problem right now?** Keep their own words. Classify as one of: `who_to_sell_to`, `few_paying_users`, `low_signup_conversion`, `which_value_to_emphasize`, `validate_new_feature`, `enter_new_market`, `other`. 2. **Product stage and current users?** (optional, skip gracefully) 3. **Current pricing?** (optional) If the founder communicates in Japanese, produce all hum