gtm-alignment

GTM Alignment Skill

Ensure implementation phasing aligns with go-to-market strategy by validating against persona tiers and estimating business value from KPI database.

CRITICAL: This skill MUST fetch real data from Notion. Do NOT make up personas or GTM tiers.

When to Use

• During Ask mode Phase 2 (CONVERGE), after dependency-mapping
• When prioritizing between equally-risky slices
• Before finalizing phase order

Notion Database IDs

Database	ID	Purpose
Persona DB	2b1c4d5e-7bea-80ee-85c2-fb96dfdcf98b	Persona tiers, RICE scores, characteristics
GTM Strategy	2b2c4d5e-7bea-809d-8c49-cc6b443738df	Positioning, messaging, segments

Note: If API-query-data-source fails, use API-post-search with query "Persona" as fallback.

Instructions

Phase 1: Fetch Persona Tiers (REQUIRED)

Primary method - Query database:

CallMcpTool:
  server: user-notion
  toolName: API-query-data-source
  arguments: {"data_source_id": "2b1c4d5e-7bea-80ee-85c2-fb96dfdcf98b"}

Fallback method - Search (if query fails):

CallMcpTool:
  server: user-notion
  toolName: API-post-search
  arguments: {"query": "Persona"}

STOP if BOTH methods fail. Report error and do not proceed with made-up data.

Extract from Persona DB:

• Persona name (title)
• RICE score (for prioritization)
• Goals, Pain points, Background
• Market segments

Build Tier Priority Table (sorted by RICE score):

Tier	Persona	RICE Score	Key Traits
T1	[Highest RICE from Notion]	[Score]	[Goals/Pain points]
T2	[Second RICE from Notion]	[Score]	[Goals/Pain points]
T3	[Third RICE from Notion]	[Score]	[Goals/Pain points]

Evidence required: Show persona names and RICE scores from Notion

Phase 2: Fetch GTM Strategy (REQUIRED)

Primary method - Query database:

CallMcpTool:
  server: user-notion
  toolName: API-query-data-source
  arguments: {"data_source_id": "2b2c4d5e-7bea-809d-8c49-cc6b443738df"}