go-to-market-planner
# Go-to-Market Planner The go-to-market planner skill creates comprehensive launch strategies by classifying launches into three tiers (major, feature, incremental) and generating cross-functional plans including target audience analysis, messaging frameworks, activity trackers with assigned owners and deadlines, success metrics, and launch day checklists. Use it when planning product launches, defining GTM strategies, coordinating feature releases, or aligning multiple teams around a release timeline.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/go-to-market-planner && cp -r /tmp/go-to-market-planner/plugins/pm-delivery/skills/go-to-market-planner ~/.claude/skills/go-to-market-plannerSKILL.md
# Go-to-Market Planner Skill Produce a complete, cross-functional GTM plan that aligns product, marketing, sales, and support around a single launch — with clear owners, timelines, and success metrics. ## Launch Tier Framework Before planning, classify the launch: | Tier | Scope | Typical Effort | Examples | |---|---|---|---| | **Tier 1 — Major Launch** | New product / significant platform change | 8–12 weeks | New pricing model, platform rebrand, new product line | | **Tier 2 — Feature Launch** | Significant new capability | 4–6 weeks | Major feature, API release, new integration | | **Tier 3 — Incremental Release** | Improvement, bug fix, minor feature | 1–2 weeks | UI tweak, performance improvement, small enhancement | Always confirm tier with the user before proceeding. --- ## GTM Plan Output Format ### GTM Plan — [Product/Feature Name] — [Launch Date] **Launch Tier:** [1 / 2 / 3] **Launch Owner (PM):** [Name] **Target Launch Date:** [Date] **Soft Launch Date (Beta/Limited):** [Date, if applicable] --- ### 1. What We're Launching **One-line description:** [What it is, for whom, and why now] **Key customer problem solved:** [Specific pain point] **Key differentiator:** [Why ours, why now] --- ### 2. Target Audience **Primary segment:** [Who benefits most — be specific] **Secondary segment:** [Who else benefits] **Not for:** [Who this is NOT for — helps sales and support] --- ### 3. Messaging **Headline:** [Customer-facing headline — lead with outcome, not feature] **Sub-headline:** [Supporting context — how it works or why it matters] **3 key messages:** 1. [Problem solved] 2. [How it works / what's new] 3. [Proof / social proof / data] **Elevator pitch (30 seconds):** > [For [target user] who [has this problem], [product/feature] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].] --- ### 4. Launch Activities by Function | Function | Activity | Owner | Due Date | Status | |---|---|---|---|---| | Product | Feature flagging / rollout plan | PM | [date] | | | Marketing | Blog post / landing page | Marketing | [date] | | | Marketing | Email campaign to existing users | Marketing | [date] | | | Marketing | Social media content | Marketing | [date] | | | Sales | Sales enablement deck | PM + Sales | [date] | | | Sales | FAQ for sales team | PM | [date] | | | Support | Help centre articles | Support | [date] | | | Support | Support team training | Support | [date] | | | Engineering | Monitoring/alerting in place | Eng | [date] | | --- ### 5. Success Metrics | Metric | Baseline | Target | Measurement Window | |---|---|---|---| | [Adoption metric] | [X] | [Y] | 30 days post-launch | | [Engagement metric] | [X] | [Y] | 60 days post-launch | | [Business metric] | [X] | [Y] | 90 days post-launch | --- ### 6. Risks & Contingencies | Risk | Likelihood | Impact | Mitigation | |---|---|---|---| | [Risk] | H/M/L | H/M/L | [Action if it happens] | --- ### 7. Launch Day Checklist - [ ] Feature live for [X%] of users - [ ] Monitoring dashboard active - [ ] Support team briefed - [ ] Blog post published - [ ] Email sent / scheduled - [ ] Sales team notified - [ ] Executive announcement sent (if Tier 1) - [ ] Rollback procedure confirmed --- ## Required Inputs Ask the user for these if not provided: - **Product or feature name** - **Target launch date** - **Launch tier** (Tier 1 / 2 / 3 — or describe scope and the skill will classify) - **Target audience** (who benefits and who it's NOT for) - **Key message** (what's the headline outcome for the customer) - **PM and launch owner** ## Guidelines - Never plan a Tier 1 launch without at least 8 weeks of lead time - Always include a "Not for" section — it prevents misdirected sales and support tickets - Recommend a soft launch to 5–10% of users before full rollout for any Tier 1 or 2 launch - Post-launch retrospective should be scheduled at launch planning time — don't leave it to chance ## Quality Checks - [ ] Launch tier is confirmed and appropriate for scope - [ ] "Not for" section is included to prevent misdirected sales and support - [ ] Every function has at least one activity with a named owner and due date - [ ] Success metrics include a measurement window (30/60/90 days) - [ ] Rollback procedure is confirmed for Tier 1 and 2 launches - [ ] Post-launch retrospective is scheduled ## Anti-Patterns - [ ] Do not build a Tier 1 GTM plan for an incremental feature update — tier the launch appropriately before planning - [ ] Do not create activity lists without named owners and due dates — unowned tasks do not get done - [ ] Do not skip the rollback procedure for Tier 1 and 2 launches — every significant launch must have an abort plan - [ ] Do not treat marketing and engineering as separate tracks — cross-functional coordination is the whole point of a GTM plan - [ ] Do not set success metrics without a defined measurement window — "increase signups" is not a measurable target
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.