From pm-delivery
Generates cross-functional GTM plans for product launches, feature releases, and market entries, including tiers, audience, messaging, activities, owners, timelines, and metrics.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-deliveryThis skill uses the workspace's default tool permissions.
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.
Provides product launch frameworks with tier scoring (major/standard/minor), timelines (12-week plans), checklists, cross-functional coordination, and execution best practices.
Plans product launches and go-to-market strategies covering positioning, messaging, channels, and timelines. Useful for new releases or market entries.
Generates go-to-market strategies for product launches covering marketing channels, messaging, success metrics, and phased timelines. Use for new product planning or market entry.
Share bugs, ideas, or general feedback.
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.
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.
Launch Tier: [1 / 2 / 3] Launch Owner (PM): [Name] Target Launch Date: [Date] Soft Launch Date (Beta/Limited): [Date, if applicable]
One-line description: [What it is, for whom, and why now] Key customer problem solved: [Specific pain point] Key differentiator: [Why ours, why now]
Primary segment: [Who benefits most — be specific] Secondary segment: [Who else benefits] Not for: [Who this is NOT for — helps sales and support]
Headline: [Customer-facing headline — lead with outcome, not feature] Sub-headline: [Supporting context — how it works or why it matters] 3 key messages:
Elevator pitch (30 seconds):
[For [target user] who [has this problem], [product/feature] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].]
| 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] |
| 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 |
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk] | H/M/L | H/M/L | [Action if it happens] |