Claude Skill

go-to-market-planner

Plan a product or feature launch - segments, messaging, assets, channels, and launch calendar. Use before releasing anything new to the market.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download navinspire-ia-navin-navin_skills_go-to-market-planner-e9c73a3.zip · 0 KB
Part of navinspire-ia/navin — 182 skills

Install

skills CLI npx skills add https://github.com/Navinspire-ia/navin/tree/main/navin/skills/go-to-market-planner
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install navinspire-ia-navin@llmmart
Git git clone https://github.com/Navinspire-ia/navin.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole navinspire-ia/navin collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Go-to-Market Planner

Overview

A launch is a coordinated moment, not a blog post. Plan segments, messages, assets, and sequencing.

GTM checklist

Block Contents
Segments who cares first (beachhead), who next
Messaging value prop per segment, proof points, objections
Assets landing page, demo, one-pager, FAQ, sales deck, emails
Channels owned (site, email, social), earned (PR, partners), paid
Calendar T-30 teaser → T-0 launch → T+30 follow-through
Enablement sales scripts, pricing, objection handling
Metrics signups, demos, pipeline, activation

Workflow

  1. Define the launch tier: major (full plan), minor (announcement + email), silent (changelog).
  2. Write the messaging doc first - everything derives from it.
  3. Asset production list with owners/dates; write drafts via copywriting-agent, email-writer, pptx-generator.
  4. Build the day-by-day calendar (campaign-manager executes it).
  5. Post-launch: T+7 and T+30 metric reviews, iterate messaging on real objections.

Rules

  • Beachhead first: better to win one segment than whisper to five.
  • Launch date is frozen only when all Tier-1 assets are done.
  • Keep an internal FAQ - sales hears the hard questions first.
Files (navin)
  • SKILL.md 1.5 KB
    ---
    name: go-to-market-planner
    description: Plan a product or feature launch - segments, messaging, assets, channels, and launch calendar. Use before releasing anything new to the market.
    metadata: {"navin":{"emoji":"🚀","category":"marketing"}}
    ---
    
    # Go-to-Market Planner
    
    ## Overview
    
    A launch is a coordinated moment, not a blog post. Plan segments, messages, assets, and sequencing.
    
    ## GTM checklist
    
    | Block | Contents |
    |-------|----------|
    | Segments | who cares first (beachhead), who next |
    | Messaging | value prop per segment, proof points, objections |
    | Assets | landing page, demo, one-pager, FAQ, sales deck, emails |
    | Channels | owned (site, email, social), earned (PR, partners), paid |
    | Calendar | T-30 teaser → T-0 launch → T+30 follow-through |
    | Enablement | sales scripts, pricing, objection handling |
    | Metrics | signups, demos, pipeline, activation |
    
    ## Workflow
    
    1. Define the launch tier: major (full plan), minor (announcement + email), silent (changelog).
    2. Write the messaging doc first - everything derives from it.
    3. Asset production list with owners/dates; write drafts via `copywriting-agent`, `email-writer`, `pptx-generator`.
    4. Build the day-by-day calendar (`campaign-manager` executes it).
    5. Post-launch: T+7 and T+30 metric reviews, iterate messaging on real objections.
    
    ## Rules
    
    - Beachhead first: better to win one segment than whisper to five.
    - Launch date is frozen only when all Tier-1 assets are done.
    - Keep an internal FAQ - sales hears the hard questions first.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related