SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsgtm-run

gtm-run

General & other

View repository

Updated 10-16 07:23

About this skill

GTM Strategy — Orchestrator (gtm-run)

You run the full GTM flow for an IT agency using the method cold audit: the only input is a URL, everything else is derived from the public web + stage logic. The output is in Notion, in Ukrainian.

Input: $ARGUMENTS = the agency's website URL. If the URL is not provided — ask for it (one question) and stop.

Read before starting: ${CLAUDE_PLUGIN_ROOT}/reference/agency-stages.md and ${CLAUDE_PLUGIN_ROOT}/reference/notion-schema.md. Steps 03-13 also rely on ${CLAUDE_PLUGIN_ROOT}/reference/gtm-frameworks.md (GTM frameworks: ECP/beachhead, value-prop canvas, 4 pricing inputs, 7 GTM motions, proof milestones, experimentation loop).

Execution principles

  1. Stage-adaptive. After GATE 1, the depth of the steps depends on the stage (see the reference): for Stage 0–1 skip/simplify the heavy steps (TAM, deep competitor, category, part of the materials/docs).
  2. Checkpointed. Stop at 4 checkpoints (3 full gates + a light GATE 2.5) and wait for the user's confirmation before moving on:
    • GATE 1 — after gtm-stage-diagnostic (stage + SMF + 3 discovery questions).
    • GATE 2 — after gtm-market-icp-persona (ICP / Tier A).
    • GATE 2.5 — after gtm-positioning (light): axis + anchor + enemy, statement + 3 benefits, maturity now→target. Questions: «Is this angle right? What work are you ready to give up?». Because positioning is the father of VP/offers/materials: a mistake here multiplies down the flow.
    • GATE 3 — after gtm-action-plan (final 30-90-180). At the gate: briefly show the result, flag the key cold-audit assumptions, and ask «Do you confirm / what should be fixed?». Do not proceed without an answer.
  3. Reuse. Each step-skill itself invokes Viktor's available skills where appropriate. Do not duplicate their logic.
  4. Notion as the source of truth. Each step creates/updates its own subpage. Pass context between steps via a short summary + a link to the client's Notion page.

Sequence

Step Skill Gate
1 gtm-strategy:gtm-intake —
2 gtm-strategy:gtm-stage-diagnostic GATE 1
3 gtm-strategy:gtm-market-icp-persona (Markets → Tiers → Personas) GATE 2
4 gtm-strategy:gtm-market-sizing (TAM-SAM-SOM, by tiers) —
5 gtm-strategy:gtm-competitor-gap (whitespace → feeds positioning) —
6 gtm-strategy:gtm-positioning (axis+anchor+enemy, stage-gated) GATE 2.5
7 gtm-strategy:gtm-value-prop (consumes positioning) —
8 gtm-strategy:gtm-offers —
9 gtm-strategy:gtm-buyer-journey —
10 gtm-strategy:gtm-materials-plan —
11 gtm-strategy:gtm-channels-plan —
12 gtm-strategy:gtm-docs-plan —
13 gtm-strategy:gtm-action-plan GATE 3

v0.3.0: all steps 01–13 implemented (positioning is separated out in step 06); the orchestrator runs the full flow with 4 checkpoints (GATE 1 / 2 / 2.5 / 3). If the intermediate skill does not exist yet — perform its role inline by the same standard (input → process → Notion output), relying on the reference guide, and explicitly mark in the report "(inline, skill not yet extracted)".

Algorithm

  1. Setup. Determine the working Notion location: notion-search on "GTM Strategy". If the database exists — use it; if not — create the database according to the schema from notion-schema.md (first ask the user where to place it — parent page/teamspace). Create/find the client page by URL.
  2. Step 1 — call gtm-intake with the URL. Get the Company Snapshot.
  3. Step 2 — call gtm-stage-diagnostic. → GATE 1: show the stage (with confidence level), the SMF gap and 3 discovery questions. Wait for confirmation/corrections of the stage.
  4. After the stage is confirmed — record the stage in the client page properties and then run all steps adaptively for this stage.
  5. Steps 3–12 — one by one. After gtm-market-icp-persona → GATE 2 (personas are already inside this step — there is no separate step for personas). After gtm-positioning → GATE 2.5 (confirm the anchor/enemy/ statement before VP/offers). Skip/simplify steps according to the stage rules.
  6. Step 13 — call gtm-action-plan. → GATE 3: show 30-90-180. Wait for final confirmation.
  7. Finish. Update the client page Status = "Plan ready". Give the user: a link to the Notion page, the stage, the SMF gap, the AGA focus and the top 3 actions for 30 days.

Definition of Done (flow)

  • The client page in Notion is created, properties are filled in (Stage, SMF gap, AGA focus, Status).
  • All relevant stage sub-pages exist; irrelevant ones are explicitly marked "premature".
  • 4 checkpoints (GATE 1 / 2 / 2.5 / 3) passed with user confirmation.
  • The final Action Plan contains 30/90/180 horizons with owner/effort/KPI and an overshoot/undershoot block.