Final step and final checkpoint (GATE 3). Consolidate everything into a prioritized 30 / 90 / 180-day action plan. Basis of the plan: Stage + cheapest SMF gap + AGA mapping (the decision is fixed in the flow architecture).
Read ${CLAUDE_PLUGIN_ROOT}/reference/agency-stages.md (sections 2, 4, 5, 8). GTM enrichment (${CLAUDE_PLUGIN_ROOT}/reference/gtm-frameworks.md §0,§7,§8):
proof milestones (Problem-Solution → PMF → GTM-fit → Scaling; Sean Ellis ≥40%) · NSM + OKR (monthly review) ·
Experimentation Loop + Impact × Ease prioritization · 90-day plan. Pull from the client's Notion
page: Stage, SMF gap, AGA focus + all artifacts of steps 03-12 (03 market/ICP/tiers/persona ·
04 market-sizing · 05 competitor+whitespace · 06 positioning · 07 VP · 08 offers · 09 customer journey ·
10 materials · 11 channels · 12 docs). Whatever is still missing — treat it as a 'dependency'. Take leading KPIs; where appropriate — Z1 benchmarks
(Appendix A).
Prioritization logic
- Stage sets the ceiling of ambitions (what is appropriate now, what is premature).
- SMF gap determines WHAT we fix first (close the cheapest gap: L → Cr → $ → #).
- AGA focus determines WHICH block of work we activate (M1 / M2–M3 / M4 / M5).
- Overshoot/undershoot (from steps 10–12) → specific 'kill' and 'build' items.
Plan structure
Horizons:
- 0–30 days — Quick Wins: 5–7 actions that produce visible movement and close the cheapest gap. For Stage 0–1 — focus, not scale (1 ICP, 1 offer, 1 channel).
- 31–90 days — Foundation: build the foundational artifacts/processes for the stage (ICP refresh, offer A/B, basic docs per the matrix).
- 91–180 days — Traction/Scale: scale what worked; add the next AGA module.
Format of each action (task card):
- Name · Why (which gap/goal it closes) · Owner (role by stage) · Effort (S/M/L) · KPI (leading metric) · Dependencies.
Separate blocks:
- Kill / freeze (overshoot) — 1–3 items.
- Build (undershoot, critical gaps) — 1–3 items.
- What we do NOT do now (premature for the stage) — to avoid paralysis and overshoot.
Reuse
Before finalizing, run the plan through gtm-action-thinker (this pack; stress test: blind spots, risks,
whether the scope is realistic for the stage team). Take the comments into account.
GATE 3 — checkpoint
Show the user a concise 30-90-180 + kill/build blocks. Wait for confirmation/edits. After that — update
Status = Plan ready.
Output (Notion)
Sub-page «13 · Action Plan 30-90-180»: 3 horizons with task cards (table or toggles), overshoot/undershoot/"not doing" blocks, and a summary at the top (Stage · SMF gap · AGA focus · top-3 actions). In Ukrainian. A "Sources/assumptions" block.
Definition of Done
- 3 horizons filled in; each action has owner + effort + KPI.
- The plan is explicitly tied to the Stage + SMF gap + AGA focus.
- There are "kill", "build", "not doing now" blocks.
- Passed
gtm-action-thinkerstress test. - Notion updated;
Status = Plan ready.