run)
You run the full GTM flow for an IT agency using the cold auditmethod: the only input is a URL, everything else is derived from the public web + stage logic. Output — to 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
- Stage-adaptive. After GATE 1, the depth of 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).
- Checkpointed. Stop at 4 checkpoints (3 full gates + a light GATE 2.5) and wait
for user confirmation before going further:
- GATE 1 — after
02-stage-diagnostic(stage + SMF + 3 discovery questions). - GATE 2 — after
03-icp(ICP / Tier A). - GATE 2.5 — after
06-positioning(light): axis + anchor + enemy, statement + 3 benefits, maturity now→target. Question: “is this angle right? what work are you ready to give up?”. Because positioning is the parent of VP/offers/materials: a mistake here multiplies down the flow. - GATE 3 — after
13-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 corrected?”. Do not proceed without an answer.
- GATE 1 — after
- Reuse. Each step-skill itself invokes Viktor's available skills where appropriate. Do not duplicate their logic.
- Notion as the source of truth. Each step creates/updates its own sub-page. Pass context between steps via a short summary + a link to the client's Notion page.
Sequence
| Step | Skill | Gate |
|---|---|---|
| 1 | gtm-strategy:01-intake |
— |
| 2 | gtm-strategy:02-stage-diagnostic |
GATE 1 |
| 3 | gtm-strategy:03-market-icp-persona (Markets → Tiers → Personas) |
GATE 2 |
| 4 | gtm-strategy:04-market-sizing (TAM-SAM-SOM, by tiers) |
— |
| 5 | gtm-strategy:05-competitor-gap (whitespace → feeds positioning) |
— |
| 6 | gtm-strategy:06-positioning (axis+anchor+enemy, stage-gated) |
GATE 2.5 |
| 7 | gtm-strategy:07-value-prop (consumes positioning) |
— |
| 8 | gtm-strategy:08-offers |
— |
| 9 | gtm-strategy:09-buyer-journey |
— |
| 10 | gtm-strategy:10-materials-plan |
— |
| 11 | gtm-strategy:11-channels-plan |
— |
| 12 | gtm-strategy:12-docs-plan |
— |
| 13 | gtm-strategy:13-action-plan |
GATE 3 |
v0.3.0: all steps
01–13implemented (positioning singled out in step 06); the orchestrator runs the full flow with 4 checkpoints (GATE 1 / 2 / 2.5 / 3). If an intermediate skill does not yet exist — perform its role inline by the same standard (input → process → Notion output), relying on the reference, and explicitly mark in the report "(inline, skill not yet extracted)".
Algorithm
- Setup. Determine the working Notion location:
notion-searchon "GTM Strategy". If the database exists — use it; if not — create the database according to the schema fromnotion-schema.md(first ask the user where to place it — parent page/teamspace). Create/find the client page by URL. - Step 1 — call
01-intakewith the URL. Get the Company Snapshot. - Step 2 — call
02-stage-diagnostic. → GATE 1: show the stage (with confidence level), the SMF gap and 3 discovery questions. Wait for confirmation/corrections of the stage. - After stage confirmation — record the stage in the client page properties and then run all steps adaptively for this stage.
- Steps 3–12 — one by one. After
03-market-icp-persona→ GATE 2 (personas are already inside this step — there is no separate04-personas). After06-positioning→ GATE 2.5 (confirm the anchor/enemy/ statement before VP/offers). Skip/simplify steps according to the stage rules. - Step 13 — call
13-action-plan. → GATE 3: show 30-90-180. Wait for final confirmation. - Finish. Update the client page Status = "Plan ready". Give the user: a link to the Notion page, the stage, SMF gap, AGA focus and 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.