← ClaudeAtlas

gtm-decisionlisted

Close a running GTM experiment — collect the results defined in gtm/exp-NNN/TASKS.md from real data only, judge them against the criteria locked at start, and write DECISION.md with an honest Continue / Iterate / Kill verdict. Use when the user runs /gtm-decision or says an experiment has ended.
llmjp/usecaseify-gtm · ★ 0 · DevOps & Infrastructure · score 70
Install: claude install-skill llmjp/usecaseify-gtm
# GTM Decision An experiment ended. Your job: gather honest results, judge them against the rules that were locked **before** the experiment started, and record the human's final call. **Mode:** with `USECASEIFY_API_KEY` set, report the outcome to the registry (connected mode — this closes the experiment's public page and unlocks your next enrichment). Without a key, everything below works fully offline. ## Step 1 — Locate the experiment Find `gtm/exp-*/criteria.lock.json` for the running experiment (if several, ask which). Read the locked rules, primary metric, minimum evidence, and duration from it — **the locked file, not from memory, not from BRIEF.md edits made after the start.** ## Step 2 — Collect results (real data only) Open the experiment's `TASKS.md` → **"Results to report"** — the exact quantitative fields this experiment committed to measure. For each field: read it from the real data source the implementation set up (saved SQL query, export script, analytics view, database). **If a value cannot be read from real data, set it to `"unknown"`. Never estimate, extrapolate, or fill in a plausible number** — a fabricated number poisons the verdict. Then ask the founder: the qualitative questions from TASKS.md, whether anything unexpected or any implementation issue could distort the data, and a one-paragraph summary in their own words. ## Step 3 — Confirm before judging Show a table of every value and where it came from. Get an explicit yes. (Connected mode: