gtm-alignment_skill

This skill aligns implementation phases with GTM strategy and KPI targets by validating persona tiers against real Notion data.

TypeScript

306

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill wellapp-ai/well --skill gtm-alignment

SKILL.md6.2 KB

Overview

This skill aligns implementation phases with the go-to-market strategy by validating slices against real persona tiers and estimating business value from KPI targets. It requires live reads from the team's Notion persona and GTM strategy databases and produces prioritized phase mappings with GTM scores and conflict resolutions. The output is actionable: tiered priorities, phase assignments, and remediation options when GTM and risk orders conflict.

How this skill works

The skill queries the designated Notion persona and GTM strategy databases, extracting persona names, RICE scores, goals, pain points, positioning statements and messaging themes. It builds a tier-priority table sorted by actual RICE scores, maps feature slices to the personas they serve, and computes a GTM Score that combines tier priority, value score, and announcement potential. Finally, it reconciles GTM ordering with dependency-based risk order and outputs phase assignments plus resolution options for detected conflicts.

When to use it

During Ask mode Phase 2 (CONVERGE) after dependency-mapping is complete
When prioritizing between slices with similar technical risk
Before locking the final phase order or release plan
When you need evidence-backed persona prioritization for stakeholder discussions
When assessing what to announce at each phase to maximize impact

Best practices

Always use the live Notion queries; stop and report if both query and search fail
Require evidence in output (record counts, RICE scores, positioning excerpts) before accepting recommendations
Ensure each phase fully serves at least one persona tier to preserve customer value
Resolve high GTM + high risk by splitting into MVP + full delivery where feasible
Document conflicts with clear resolution options and a recommended path

Example use cases

Choosing which feature slice to ship first when two slices have equal risk but different persona impact
Designing a three-phase launch plan that maximizes announcements for Tier 1 customers
Balancing dependency-driven engineering order with GTM priorities for early revenue impact
Preparing a stakeholder checkpoint that shows evidence from Notion and recommended phase sequencing

FAQ

The skill will attempt the configured search fallback; if both methods fail it stops and reports the error—no personas or GTM data are invented.

How is the GTM Score calculated?

GTM Score = (TierPriority x 3) + ValueScore + AnnouncementPotential, where TierPriority maps T1=3,T2=2,T3=1; ValueScore maps Critical=3...Low=0; AnnouncementPotential is 2/1/0.

What evidence is produced?

Outputs include Notion fetch status, record counts, persona names with RICE scores, a positioning statement excerpt, tier tables, phase mappings, GTM scores, and any conflict documentation.