justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: v9.0.0 — three new agent templates (Discovery, Stakeholder Comms, Launch)

Browse Source 
This release adds three new agent templates to the library, bringing the total to four.

New templates:
- PM Discovery Agent: synthesises customer interviews from Notion or Google Drive,
  identifies cross-interview themes, scores assumption confidence, generates follow-up questions
- PM Stakeholder Comms Agent: detects audience type (executive/investor/stakeholder/board),
  pulls activity from Linear/Jira/Drive, drafts in audience-appropriate format
- PM Launch Agent: end-to-end launch coordination with channel-specific content,
  calendar, success metrics, and launch checklist

Each template follows the established pattern: README, AGENT.md, orchestrate.sh,
2 subagents, connectors with example configs, examples, smoke test.

Total file count: 37 new files across 3 templates.

Updated README to position library as 4-template collection.
Bumped marketplace.json from v8.0.0 to v9.0.0.
This commit is contained in:
mohitagw15856
2026-05-07 22:30:34 +01:00
parent 9274b3d378
commit 59c4510055
50 changed files with 4659 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/pm-launch-agent/AGENT.md
+113
View File
@@ -0,0 +1,113 @@
---
name: pm-launch-agent
version: 1.0.0
description: "End-to-end product launch coordination agent. Generates the launch plan, drafts content for every channel (email, in-product, social, blog, sales enablement, internal, media), builds the content calendar, and defines success metrics. Use when planning a feature launch, product release, or major announcement."
author: Mohit Aggarwal
license: MIT
---
# PM Launch Agent
## Configuration
```yaml
defaults:
default_launch_tier: minor
default_target_audience: "all customers"
launch_tiers:
minor:
channels: [in-product, internal]
include_media_pitch: false
content_calendar_length_days: 14
major:
channels: [email, in-product, linkedin, x, blog, sales-enablement, internal]
include_media_pitch: true
content_calendar_length_days: 30
flagship:
channels: [email, in-product, linkedin, x, blog, sales-enablement, internal, media-pitch, customer-webinar, partner-comms]
include_media_pitch: true
content_calendar_length_days: 60
output:
format: markdown
output_directory: ./output
```
## Agent system prompt
You are the PM Launch Agent. Your role is to take a feature description and a launch date, then generate everything needed to coordinate a successful launch.
You operate in this order:
1. **Validate inputs.** Check feature-name, launch-date, feature-summary are present. Calculate days-to-launch from launch-date.
2. **Determine launch scope.** Based on launch-tier (minor/major/flagship), set the channel list and content calendar length.
3. **Generate the launch plan** using the `go-to-market` skill. Provide it: feature name, summary, target audience, launch date. It returns: positioning statement, messaging pillars, key benefits with proof points, role-specific use cases.
4. **Call the Channel Drafter subagent** for each channel in the launch tier's channel list. Provide it: launch plan from step 3, target channel, and channel-specific guidelines. It returns: full draft for that channel adapted to the format and tone the channel requires.
5. **Build the content calendar** using the `content-calendar` skill. Provide it: launch date, channel list, content from step 4. It returns: scheduled posting plan with dates, times, and channels.
6. **If launch tier is major or flagship**, draft the media pitch using the `media-pitch` skill. Provide it: launch plan, target audience, key proof points.
7. **Define success metrics** by calling the Launch Metrics Designer subagent. Provide it: feature description, launch tier, target audience. It returns: leading indicators (week 1), lagging indicators (month 1, quarter 1), and what would constitute "launch failure" worth investigating.
8. **Generate the launch checklist** using the `launch-checklist` skill. Provide it: launch tier, channels included, launch date. It returns: phase-by-phase checklist (pre-launch / launch day / post-launch) with specific tasks and owners.
9. **Compile everything** into a single launch plan document with these sections:
- Launch overview (positioning, target, date)
- Per-channel content drafts
- Content calendar
- Media pitch (if applicable)
- Success metrics framework
- Launch checklist
10. **Save** to output directory with descriptive filename.
11. **(Optional)** Post the launch plan to Notion if configured.
## Quality checks before returning output
- [ ] All required channels in the launch tier have a draft
- [ ] Positioning is consistent across all channels (same key benefits, same proof points)
- [ ] Tone is appropriately differentiated per channel (formal blog vs. punchy X post)
- [ ] Content calendar dates align with the stated launch date
- [ ] Success metrics are specific and measurable (not vague aspirations)
- [ ] Launch checklist has assigned owners (or marked TBD with a note)
- [ ] Media pitch is included for major and flagship launches
## Tools required
| Tool | Purpose |
|---|---|
| go-to-market (skill) | Generate launch plan with positioning |
| content-calendar (skill) | Build the scheduled content calendar |
| email-campaign (skill) | Reference for email format |
| media-pitch (skill) | Generate journalist pitch (major/flagship only) |
| launch-checklist (skill) | Generate phase-by-phase task checklist |
| channel-drafter (subagent) | Adapt content per channel |
| launch-metrics-designer (subagent) | Design success metrics |
| notion-connector (optional) | Post launch plan to shared workspace |
| filesystem-write | Save the launch plan |
## When to invoke this agent
Use this agent when:
- Planning a feature launch (any size)
- Coordinating a product release across multiple channels
- Preparing for a major company announcement
- Replacing 4+ hours of launch coordination with a 5-minute setup
Do NOT use this agent for:
- Internal-only changes (use `release-notes` skill)
- Customer support communications (different tone and format)
- Sales-cycle-specific content (use `proposal-writer` skill)
- Conference talks or keynote prep (different content type)
## Architecture notes
This agent is unusual among the templates in being content-first rather than data-first. It pulls minimal data from external systems (only Notion if configured) — most of the work is generating coordinated content from a single source of truth.
The Channel Drafter subagent is the most architecturally interesting piece. It takes one canonical launch message and adapts it to each channel's format, tone, and length conventions while keeping the core positioning intact. This is the coordination problem most launches fail to solve.
templates/pm-launch-agent/README.md
+197
View File
@@ -0,0 +1,197 @@
# PM Launch Agent — Agent Template
> **An end-to-end product launch coordination agent. Builds the launch plan, generates content for every channel, schedules the launch comms, and monitors post-launch signals — all from a single feature description.**
This is the fourth agent template in the pm-claude-skills library. It follows the architecture Anthropic introduced for [financial services agent templates](https://www.anthropic.com/news/finance-agents) on May 5, 2026.
---
## What it does
You give the agent a feature description and a launch date. It does the rest:
1. **Generates the launch plan** with phases, dependencies, and owners using the `go-to-market` skill
2. **Drafts launch content for every channel** using a Channel Drafter subagent that adapts messaging per channel:
- Customer email
- In-product announcement
- Social media posts (LinkedIn, X)
- Blog post or release notes
- Sales enablement one-pager
- Internal launch announcement
3. **Builds the content calendar** using the `content-calendar` skill
4. **Drafts the press/media pitch** using the `media-pitch` skill (if launch warrants media outreach)
5. **Defines the success metrics** using a Launch Metrics Designer subagent
6. **Compiles everything** into a launch plan document
End-to-end: roughly 2-3 minutes. The manual version of coordinating a launch like this typically takes 4-6 hours of focused work.
---
## Why this matters
Launches fail not because the work isn't done, but because the work is fragmented across people and tools. The PM coordinates with marketing, sales, support, and engineering — each producing their own version of the launch content with subtly different positioning. By the time launch day arrives, the customer email says one thing, the blog post says another, and sales is pitching a third version.
This agent solves the coordination problem by drafting all the content from a single source of truth. Every artifact uses consistent positioning, the same key benefits, the same proof points. Then your team edits and customises — but starts from alignment, not from divergence.
---
## What's inside this template
```
templates/pm-launch-agent/
├── README.md ← you are here
├── AGENT.md ← agent definition
├── orchestrate.sh ← orchestration script
├── skills/ ← skills used by this agent
│ ├── README.md
│ ├── go-to-market/SKILL.md ← (symlink)
│ ├── content-calendar/SKILL.md ← (symlink)
│ ├── media-pitch/SKILL.md ← (symlink)
│ ├── email-campaign/SKILL.md ← (symlink)
│ └── launch-checklist/SKILL.md ← (symlink)
├── subagents/
│ ├── channel-drafter.md ← per-channel content generation
│ └── launch-metrics-designer.md ← success metrics design
├── connectors/
│ ├── README.md
│ └── notion.example.json ← Notion (for posting the plan)
├── examples/
│ ├── input-example.md
│ └── output-example.md
└── tests/
└── smoke-test.md
```
---
## Quick install (5 minutes)
### Prerequisites
- Claude Code installed
- The full skills library installed: `/plugin marketplace add mohitagw15856/pm-claude-skills`
- Optional: Notion (for posting the launch plan to a shared workspace)
### Setup
This agent works without any connectors — it generates content based on the feature description you provide. You only need a connector if you want to post the launch plan directly to Notion.
```bash
cd templates/pm-launch-agent
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents and conversations" \
--dry-run
```
If the dry-run completes, you're set up.
---
## Running the agent
### Standard usage
```bash
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents and conversations" \
--target-audience "knowledge workers at mid-market companies" \
--launch-tier major
```
The agent will:
1. Generate the launch plan using `go-to-market` skill
2. Draft customer email using `email-campaign` skill (via Channel Drafter)
3. Draft in-product announcement (via Channel Drafter)
4. Draft social media posts for LinkedIn and X (via Channel Drafter)
5. Draft blog post (via Channel Drafter)
6. Draft sales enablement one-pager (via Channel Drafter)
7. Draft internal launch announcement (via Channel Drafter)
8. Build content calendar using `content-calendar` skill
9. Draft media pitch using `media-pitch` skill (only for major launches)
10. Define success metrics (via Launch Metrics Designer)
11. Compile launch checklist using `launch-checklist` skill
12. Output everything to `output/launch-[feature-name]-plan.md`
### Configuration options
| Flag | Required | Default | Description |
|---|---|---|---|
| `--feature-name` | Yes | — | Name of the feature being launched |
| `--launch-date` | Yes | — | Target launch date (YYYY-MM-DD format) |
| `--feature-summary` | Yes | — | One-paragraph description of what the feature does |
| `--target-audience` | No | "all customers" | Who the launch is targeting |
| `--launch-tier` | No | minor | `minor`, `major`, or `flagship` (controls breadth and intensity) |
| `--include-media-pitch` | No | auto | Include media pitch (auto = yes for major/flagship) |
| `--post-to-notion` | No | false | Post the launch plan to configured Notion workspace |
| `--dry-run` | No | false | Validate config without running |
### Launch tiers explained
- **Minor** — small feature releases, in-product announcements only, no media
- **Major** — significant feature launches, full content calendar, media pitch included
- **Flagship** — major product moments (rebrand, big feature, version release), maximum coverage
The tier affects both the breadth of content generated and the depth of each piece.
---
## Why this architecture
**Skills** provide format-specific output structures — content calendar formats, email campaign templates, media pitch frameworks. The library already has all the relevant skills.
**Subagents** handle the cross-cutting decisions:
- The Channel Drafter adapts the same launch message into different formats while keeping positioning consistent
- The Launch Metrics Designer figures out what success looks like for this specific launch
**Connectors** are minimal here — only Notion if you want to post the plan to a shared workspace. Most launches are coordinated via shared docs, so this agent is content-first rather than data-first.
---
## Customisation
### Add channels you actually use
The default Channel Drafter outputs for: email, in-product, LinkedIn, X, blog, sales enablement, internal. If your team uses different channels (Discord, Reddit AMAs, partner co-marketing, video content), extend the Channel Drafter to cover them.
### Adjust positioning for your team's voice
The default outputs use neutral B2B SaaS positioning language. If your brand voice is distinctive — playful, technical, formal — fork the relevant skills (especially `go-to-market` and `email-campaign`) and customise.
### Connect to your launch tools
Add connectors for tools you actually use for launch coordination:
- Asana or Linear (for the launch checklist as actionable tasks)
- Buffer or Hootsuite (for scheduling social posts)
- Mailchimp or Customer.io (for scheduling the customer email)
The pattern is the same as other templates in this library.
---
## Limitations and honest caveats
**This agent generates first drafts, not finished launches.** Every piece of content needs review and editing. Marketing should review the customer-facing content. Sales should review the enablement one-pager. Your CEO might want to weigh in on the blog post. The agent removes the blank-page problem, not the editorial work.
**Positioning quality depends on your inputs.** A vague feature summary produces vague content. Spend 5 minutes writing a clear feature summary with specific benefits before running the agent — it pays back enormously.
**Launch metrics are starting points.** The Launch Metrics Designer suggests reasonable metrics based on launch tier and feature type. Validate against your actual analytics setup. Some suggested metrics may not be measurable in your stack.
**No actual scheduling.** The agent produces a content calendar with recommended times, not an automatic schedule. You (or your marketing team) still need to publish the content using your own tools.
---
## Where to learn more
- [Anthropic's announcement of agent templates](https://www.anthropic.com/news/finance-agents)
- [PM Sprint Agent](../pm-sprint-agent/) (first template)
- [PM Discovery Agent](../pm-discovery-agent/) (second template)
- [PM Stakeholder Comms Agent](../pm-stakeholder-comms-agent/) (third template)
- [Part 19 article — Building the PM Launch Agent](#) *(link added when published)*
---
*Built and maintained by [Mohit Aggarwal](https://medium.com/@mohit15856) | Fourth agent template in [pm-claude-skills](https://github.com/mohitagw15856/pm-claude-skills)*
templates/pm-launch-agent/connectors/README.md
+52
View File
@@ -0,0 +1,52 @@
# Connectors — PM Launch Agent
This agent works without any connectors — it generates content from your feature description rather than pulling data from external systems. The optional Notion connector lets you post the launch plan directly to a shared workspace.
## Optional: Notion
If you want the agent to post the launch plan to Notion (so cross-functional partners can collaborate on it), set up the Notion connector.
```bash
cd templates/pm-launch-agent/connectors
cp notion.example.json notion.json
# Get your integration token
# Create at: https://www.notion.so/my-integrations
export NOTION_INTEGRATION_TOKEN='secret_xxxxxxxxxxxx'
# Edit notion.json — update workspace_url and parent_page_id
```
Then run with `--post-to-notion true`:
```bash
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents" \
--launch-tier major \
--post-to-notion true
```
## Without Notion
The agent works fully without any connectors configured. The launch plan is saved to `output/launch-[name]-plan.md` and you can copy it anywhere you want.
```bash
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents" \
--launch-tier major
```
## Future connectors
If your team uses dedicated tools for launch coordination, additional connectors would be useful additions:
- **Buffer or Hootsuite** — auto-schedule social posts from the channel drafts
- **Mailchimp or Customer.io** — auto-create the customer email campaign
- **Asana or Linear** — turn the launch checklist into actionable tasks
- **Slack** — post the internal launch announcement to a specific channel
PRs welcome for any of these. Each follows the same pattern as the connectors in PM Sprint Agent and PM Discovery Agent.
templates/pm-launch-agent/connectors/notion.example.json
+39
View File
@@ -0,0 +1,39 @@
{
"connector_name": "notion",
"version": "1.0.0",
"description": "Optional Notion connector for the PM Launch Agent. Posts the launch plan to a configured Notion workspace so it's accessible to cross-functional partners.",
"configuration": {
"workspace_url": "https://www.notion.so/your-workspace",
"parent_page_id": "PARENT_PAGE_ID_HERE",
"default_page_template": "launch-plan-template",
"tags_to_apply": ["launch", "pm-launch-agent"],
"rate_limit_requests_per_second": 3
},
"credentials": {
"integration_token_env_var": "NOTION_INTEGRATION_TOKEN",
"integration_token_placeholder": "secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
},
"available_operations": [
{
"name": "create_launch_page",
"description": "Create a new page in the configured Notion workspace with the launch plan content",
"required_inputs": ["title", "content"]
}
],
"_setup_instructions": [
"1. Create a Notion integration at https://www.notion.so/my-integrations",
"2. Set NOTION_INTEGRATION_TOKEN environment variable",
"3. Create a parent page in Notion where launch plans should be posted (e.g., 'Launches' database or page)",
"4. Share that parent page with your integration",
"5. Copy the parent page ID from the URL",
"6. Update parent_page_id in this file",
"7. Save as 'notion.json'",
"8. Test: bash orchestrate.sh --feature-name 'Test' --launch-date 'YYYY-MM-DD' --feature-summary 'Test' --post-to-notion true --dry-run"
],
"_note": "This connector is optional. The agent works fine writing only to local files. Adding Notion lets you post the launch plan directly to your team's shared workspace, but isn't required."
}
templates/pm-launch-agent/examples/input-example.md
+74
View File
@@ -0,0 +1,74 @@
# Example: Input to the PM Launch Agent
## Common invocations by launch tier
### Minor feature launch (in-product only)
```bash
bash orchestrate.sh \
--feature-name "Keyboard Shortcuts" \
--launch-date "2026-05-20" \
--feature-summary "Power-user keyboard shortcuts for the most common actions in the app" \
--target-audience "active power users" \
--launch-tier minor
```
### Major feature launch (full content + media)
```bash
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents and conversations. Finds what you mean, not just what you typed." \
--target-audience "knowledge workers at mid-market companies" \
--launch-tier major
```
### Flagship launch (maximum coverage)
```bash
bash orchestrate.sh \
--feature-name "Workspace 2.0" \
--launch-date "2026-09-01" \
--feature-summary "Complete redesign of the workspace experience with collaborative editing, real-time presence, and unified search across all your tools." \
--target-audience "all customers and prospects" \
--launch-tier flagship \
--post-to-notion true
```
## What goes into a great feature summary
The agent's output quality depends heavily on this input. Vague summaries produce vague content.
**Weak summary:** "New search feature that's better"
**Strong summary:** "AI-powered semantic search that understands intent, not just keywords. Searches across documents, conversations, and shared workspaces in one query. Returns results ranked by relevance to what the user is actually trying to accomplish, with explanations of why each result matched."
The strong version gives the agent enough material to:
- Generate distinctive positioning (semantic search, intent over keywords)
- Identify proof points (cross-source search, ranked by intent)
- Suggest use cases (research workflows, troubleshooting)
- Differentiate from alternatives
## Launch tier decision guide
| If your launch is... | Use tier |
|---|---|
| Bug fix or polish improvement | Don't use this agent — use `release-notes` skill directly |
| New feature targeted at existing power users | minor |
| Quality-of-life improvement to existing flow | minor |
| New feature targeting broader user base | major |
| Significant capability addition | major |
| Enterprise tier launch | major |
| Major product moment (rebrand, V2.0, new product) | flagship |
| Press-worthy announcement | flagship |
| Public company milestone | flagship |
When in doubt, start with major. You can always reduce coverage. Going from minor to major after the fact is harder.
## What you should know before running
- **Launch dates 1+ weeks in the future work best.** The agent generates a full pre-launch plan. If launch is in 2 days, much of the plan won't be useful.
- **Have a clear feature summary.** Write it before running. 2-3 sentences minimum, ideally a paragraph.
- **Know your target audience.** "All customers" works but produces generic content. "SMB founders evaluating workflow tools" is sharper.
- **Be honest about tier.** Marking a minor launch as flagship just creates more content to edit and discard.
templates/pm-launch-agent/examples/output-example.md
+337
View File
@@ -0,0 +1,337 @@
# Launch Plan — Smart Search
**Launch Date:** 2026-06-15 (40 days from generation)
**Launch Tier:** major
**Target Audience:** knowledge workers at mid-market companies
**Channels:** email, in-product, linkedin, x, blog, sales-enablement, internal
**Generated:** 2026-05-06 15:00 BST
---
## Feature Summary
AI-powered semantic search across documents and conversations. Finds what you mean, not just what you typed.
---
## Launch Plan (Positioning & Messaging)
### Positioning Statement
For knowledge workers at mid-market companies who waste 30 minutes a day searching for information, Smart Search is an intelligent retrieval layer that understands intent. Unlike traditional keyword search, Smart Search returns results ranked by what you're actually trying to accomplish.
### Messaging Pillars
1. **Find what you mean, not what you typed** — Search by intent, not exact words
2. **One search, all your sources** — Documents, conversations, shared workspaces
3. **Explainable results** — See why each result matched
### Key Benefits with Proof Points
| Benefit | Proof Point |
|---|---|
| Faster information retrieval | Internal beta: 60% reduction in time-to-find |
| Higher search success rate | Beta users: 85% find what they need on first search vs. 40% with old search |
| Less context switching | Single search interface replaces 4 separate tools |
### Use Cases by Persona
- **Product managers:** Find prior research on a topic across docs and Slack threads
- **Engineers:** Locate code examples and technical decisions in old discussions
- **Customer success:** Pull up customer history across emails, calls, and tickets
- **Marketing:** Find approved messaging and brand assets without asking the team
---
## Content Drafts by Channel
### Customer Email
**Subject:** Find what you actually meant. Introducing Smart Search.
**Preheader:** AI-powered search that understands intent, not just keywords.
**Body:**
Hi [First Name],
We've all been there: you know you saw something three weeks ago, you can roughly remember what it was about, but the exact words you searched for return nothing useful.
Today we're shipping Smart Search — a complete rebuild of how search works in [Product]. It uses AI to understand what you're actually looking for, not just match keywords. Search across documents, conversations, and shared workspaces in a single query.
Three things you'll notice immediately:
1. You can search by intent — "the proposal we sent to Acme last quarter" works, even if those exact words aren't in the document.
2. Results are explained — see why each result matched, so you can quickly tell what's relevant.
3. One search bar searches everything — no more checking three places to find one thing.
Smart Search is rolling out to all customers over the next two weeks. You'll see the new search the next time you sign in.
Want to see it in action? [Watch the 90-second demo →]
Mohit
Head of Product
---
### LinkedIn Post
The single biggest waste of time at most companies isn't meetings.
It's searching for things.
Documents you saw last month. Slack threads with key decisions. Customer history scattered across emails, tickets, and calls. The information exists. You just can't find it.
Today we're shipping Smart Search — a complete rebuild of how search works in [Product]. The difference: it understands what you're trying to accomplish, not just the words you typed.
In our beta, users found what they needed on the first search 85% of the time, up from 40% with traditional search. That translates to roughly 30 minutes a day per user back in their week.
Available to all customers over the next two weeks.
Curious how semantic search compares to what your team uses today? Happy to chat — DMs open.
---
### X / Twitter Post
Today: Smart Search is live for all [Product] customers 🔍
What changes:
→ Search by intent, not just keywords
→ One query searches docs, conversations, and shared workspaces
→ Every result explains why it matched
In beta: 85% first-search success rate (up from 40%)
Try it: [link]
---
### Blog Post (excerpt — first 400 words)
# Smart Search: Find what you mean, not what you typed
For the past 18 months, we've watched our customers struggle with the same problem: they know the information they need exists somewhere in their workspace, but they can't find it.
Traditional search is built on keyword matching — if you type "Q1 customer feedback summary," you get documents containing those exact words. That works when you remember the precise wording. It fails when you remember the gist but not the keywords.
We talked to 47 customers about this. The pattern was consistent: people search, get nothing useful, give up, and ask a colleague. Or they spend 20 minutes scrolling through old documents looking for something they vaguely remember. Or they recreate work that already exists because they couldn't find it.
Today we're shipping Smart Search — a complete rebuild of how search works in [Product] — to address this directly.
## What's different
Three substantive changes:
**1. Search by intent.** Smart Search uses semantic understanding to match what you mean, not just what you typed. "The proposal we sent to Acme last quarter" returns the right document even if those exact words aren't in it.
**2. One search across all sources.** Documents, conversation threads, shared workspaces, even files in connected tools — all searchable in a single query. No more checking three places.
**3. Results that explain themselves.** Every search result includes a one-line explanation of why it matched your query. Quick to scan, easy to tell what's relevant.
## What we measured in beta
We ran Smart Search in private beta with 220 users over 6 weeks. The metrics:
- **First-search success rate:** 85% (up from 40% with traditional search)
- **Time to find:** 60% reduction on average
- **User satisfaction:** 92% rated Smart Search as "significantly better" than the old experience
The biggest single jump was for searches where users couldn't remember exact wording — those went from 12% success to 78% success.
[Article continues...]
---
### Sales Enablement One-Pager
**Feature:** Smart Search
**Target buyer:** Operations leaders, knowledge management buyers, IT decision makers at companies with 200+ employees
**Top 3 Benefits:**
1. **30 minutes/day per user back** — beta data shows 60% time reduction in information retrieval
2. **Reduces "rework" cost** — when employees can't find existing work, they recreate it; Smart Search prevents this
3. **One search interface** — replaces 4-5 separate search experiences across the workspace
**Top 3 Objections + Responses:**
| Objection | Response |
|---|---|
| "We already have search" | "Traditional search is keyword matching. Smart Search understands intent. The difference shows up most when users can't remember exact wording — which is most of the time." |
| "How is this different from [competitor]?" | "Two things: (1) we search across all your connected sources in a single query, (2) every result explains why it matched. Most search tools require you to click through to figure out relevance." |
| "Will this work on our private data?" | "Yes — all processing happens in your workspace. No data is sent to third-party LLMs. Full SOC 2 Type II compliance." |
**Pricing:** Included in all paid tiers from June 15. No additional cost.
**Demo flow (5 minutes):**
1. Show old keyword search returning poor results for a fuzzy query
2. Show Smart Search returning right answer with same fuzzy query
3. Show cross-source search (one query → results from docs + Slack + tickets)
4. Show "why this matched" explanation
5. Show admin controls for what's searchable
**Internal contact:** Mohit Aggarwal, mohit@company.com
---
### Internal Launch Announcement
**Slack post in #all-hands or company-wide channel:**
We're shipping Smart Search to all customers on June 15 🎉
This is the biggest investment we've made in the platform this year. Three things to know:
**Why it matters:** 30 minutes/day per user back. Beta data shows 60% reduction in time-to-find. This addresses the #1 complaint in our annual customer survey.
**Who built it:** Massive credit to Sarah Chen (PM lead), the Search team (Marcus, Priya, David, Lin), and the AI Platform team for the underlying semantic infrastructure. 6 months of work.
**What you need to do:**
- **Sales:** New sales enablement one-pager is in [link]. Two new objection responses to know.
- **Support:** Help docs are updated. Common questions list in [link].
- **Marketing:** Coordinated launch across email, blog, and social on June 15.
- **Customer Success:** Outreach plan for top 50 accounts in [link].
- **Everyone else:** Try Smart Search yourself before launch — your account has it enabled now.
Questions: ask in #smart-search-launch.
---
### In-Product Announcement (Modal)
**Headline:** Search just got smarter
**Body:** Find what you mean, not just what you typed. Now searches across all your sources.
**CTA:** Try it now / Not now
---
## Content Calendar
| Date | Channel | Content | Owner |
|---|---|---|---|
| June 8 (T-7) | Internal | Internal announcement to company | Mo |
| June 10 (T-5) | Sales enablement | One-pager distributed | Mo + Sales lead |
| June 12 (T-3) | Customer Success | Top 50 account outreach starts | CS lead |
| June 15 (Launch day, 9am ET) | Email | Customer email send | Marketing |
| June 15 (Launch day, 9am ET) | Blog | Blog post live | Marketing |
| June 15 (Launch day, 10am ET) | LinkedIn | LinkedIn post | Mo |
| June 15 (Launch day, 10am ET) | X | X post | Mo |
| June 15 (Launch day) | In-product | Modal goes live for all users | Engineering |
| June 17 (T+2) | LinkedIn | Followup post: "What we learned in week 1" | Mo |
| June 22 (T+7) | Blog | Followup post: customer use cases | Marketing |
| July 1 (T+16) | Email | Adoption update + tips | Marketing |
---
## Media Pitch
**Subject (for journalists):** Why we rebuilt search from scratch — case study in semantic search vs. keyword
**Pitch body:**
Hi [Journalist Name],
I've been following your coverage of [recent article on AI in productivity tools / similar topic].
We just shipped a complete rebuild of search in our product — moving from traditional keyword matching to semantic search built on [specific technical approach]. The interesting story isn't "we added AI" — it's the data on what changed:
- 85% first-search success rate vs. 40% with keyword (220-user beta over 6 weeks)
- 60% reduction in time-to-find
- The biggest gains were on fuzzy queries — searches where users couldn't remember exact words
Happy to walk you through the technical decisions, the surprising findings from beta (one is genuinely counter-intuitive), and access to a few customers willing to be quoted.
Available for a 30-minute conversation any time next week if useful.
Best,
Mo Aggarwal
Head of Product, [Company]
**Target journalists for outreach:**
- [Journalist 1] at TechCrunch (covers productivity SaaS)
- [Journalist 2] at The Information (covers enterprise software)
- [Journalist 3] at Protocol (covers workplace tools)
---
## Success Metrics
### Leading indicators (Week 1 post-launch)
| Metric | Target | Source | Why it matters |
|---|---|---|---|
| Smart Search awareness (in-product modal CTR) | 35%+ | Product analytics | Did users notice? |
| First-search trial rate | 50% of WAU | Product analytics | Are people trying it? |
| First search success | 75%+ | Product analytics | Does it work? |
### Lagging indicators (Month 1 post-launch)
| Metric | Target | Source | Why it matters |
|---|---|---|---|
| Weekly active users of Smart Search | 60% of WAU | Product analytics | Becoming part of workflow? |
| Searches per active user per week | 8+ | Product analytics | Habit forming? |
| Old search usage decline | -50% | Product analytics | Replacement happening? |
### Quarterly indicators (Q3 2026)
| Metric | Target | Source | Why it matters |
|---|---|---|---|
| Sales win rate (deals where Smart Search was demoed) | +10% vs control | CRM | Helping us win? |
| Retention of Smart Search active users | +5% vs non-users | Product analytics | Driving stickiness? |
| NPS specifically among Smart Search users | +10 vs overall | NPS survey | Customers love it? |
### Failure indicators (investigate immediately if observed)
1. **First-search trial rate below 25% in week 1** — suggests in-product announcement isn't landing
2. **First-search success below 50%** — suggests the feature isn't working as expected; could be a query type mismatch
3. **Sales objections about hallucination/accuracy** — suggests positioning isn't addressing the AI concern adequately
---
## Launch Checklist
### Pre-launch (T-14 to T-1)
- [ ] T-14: Engineering signoff on production readiness — Engineering Lead
- [ ] T-10: Beta feedback synthesised, blockers triaged — PM
- [ ] T-7: Internal announcement sent — PM
- [ ] T-7: Sales enablement one-pager finalised — PM + Sales Lead
- [ ] T-5: Customer Success briefing held — PM + CS Lead
- [ ] T-3: Top 50 account outreach drafted and reviewed — CS Lead
- [ ] T-3: Marketing assets finalised (email, blog, social) — Marketing
- [ ] T-2: Final QA pass in production — Engineering
- [ ] T-1: Go/no-go decision call — All leads
- [ ] T-1: Launch day runbook reviewed — All leads
### Launch day
- [ ] 09:00: Engineering deploys feature to 100% — Engineering
- [ ] 09:00: Email campaign sends — Marketing
- [ ] 09:00: Blog post publishes — Marketing
- [ ] 09:30: Verify all systems showing expected metrics — PM
- [ ] 10:00: Social posts publish (LinkedIn, X) — PM
- [ ] 10:00: Top 50 outreach begins — CS team
- [ ] 11:00: First metrics check (CTR on email, modal interactions) — PM
- [ ] 14:00: Mid-day metrics review — PM
- [ ] 17:00: End-of-day status report to leadership — PM
### Post-launch (T+1 to T+30)
- [ ] T+1: Day 1 metrics review and any rapid issues triaged — PM
- [ ] T+2: Followup LinkedIn post on early adoption — PM
- [ ] T+7: Week 1 metrics review and learnings doc — PM
- [ ] T+7: Followup blog with customer use cases — Marketing
- [ ] T+14: Week 2 metrics review — PM
- [ ] T+16: Adoption update email to customers — Marketing
- [ ] T+30: Month 1 metrics review and launch retro — PM
- [ ] T+30: Iteration plan based on month 1 data — PM
---
*Generated by [PM Launch Agent](https://github.com/mohitagw15856/pm-claude-skills/tree/main/templates/pm-launch-agent) — fourth agent template in pm-claude-skills*
---
> **A note on this draft:** This is the first draft from the agent. As the PM, you should now: (1) replace any [PLACEHOLDER] tags with real specifics, (2) get marketing review on customer-facing content, (3) get sales review on the enablement one-pager, (4) edit for your team's specific voice and tone.
templates/pm-launch-agent/orchestrate.sh
Executable
+285
View File
@@ -0,0 +1,285 @@
#!/bin/bash
# =============================================================================
# orchestrate.sh — PM Launch Agent
# =============================================================================
# Orchestrates end-to-end launch coordination:
# 1. Validate inputs and determine launch tier
# 2. Generate launch plan (go-to-market skill)
# 3. Draft content for each channel (channel-drafter subagent)
# 4. Build content calendar (content-calendar skill)
# 5. Draft media pitch if applicable (media-pitch skill)
# 6. Define success metrics (launch-metrics-designer subagent)
# 7. Generate launch checklist (launch-checklist skill)
# 8. Compile everything into the launch plan document
# =============================================================================
set -e
set -o pipefail
# -----------------------------------------------------------------------------
# Defaults
# -----------------------------------------------------------------------------
FEATURE_NAME=""
LAUNCH_DATE=""
FEATURE_SUMMARY=""
TARGET_AUDIENCE="all customers"
LAUNCH_TIER="minor"
INCLUDE_MEDIA_PITCH="auto"
POST_TO_NOTION=false
DRY_RUN=false
OUTPUT_DIR="./output"
# -----------------------------------------------------------------------------
# Parse args
# -----------------------------------------------------------------------------
while [[ $# -gt 0 ]]; do
case $1 in
--feature-name) FEATURE_NAME="$2"; shift 2 ;;
--launch-date) LAUNCH_DATE="$2"; shift 2 ;;
--feature-summary) FEATURE_SUMMARY="$2"; shift 2 ;;
--target-audience) TARGET_AUDIENCE="$2"; shift 2 ;;
--launch-tier) LAUNCH_TIER="$2"; shift 2 ;;
--include-media-pitch) INCLUDE_MEDIA_PITCH="$2"; shift 2 ;;
--post-to-notion) POST_TO_NOTION="$2"; shift 2 ;;
--dry-run) DRY_RUN=true; shift ;;
--help)
echo "PM Launch Agent — orchestration script"
echo ""
echo "Usage:"
echo " bash orchestrate.sh --feature-name NAME --launch-date DATE --feature-summary 'SUMMARY' [options]"
echo ""
echo "Required:"
echo " --feature-name Name of the feature being launched"
echo " --launch-date Target launch date (YYYY-MM-DD)"
echo " --feature-summary One-paragraph description"
echo ""
echo "Optional:"
echo " --target-audience Who the launch targets (default: 'all customers')"
echo " --launch-tier minor, major, or flagship (default: minor)"
echo " --include-media-pitch true, false, or auto (default: auto = yes for major/flagship)"
echo " --post-to-notion Post launch plan to Notion (default: false)"
echo " --dry-run Validate config without running"
exit 0
;;
*) echo "Unknown option: $1"; exit 1 ;;
esac
done
# -----------------------------------------------------------------------------
# Validate
# -----------------------------------------------------------------------------
if [[ -z "$FEATURE_NAME" ]]; then echo "ERROR: --feature-name is required"; exit 1; fi
if [[ -z "$LAUNCH_DATE" ]]; then echo "ERROR: --launch-date is required"; exit 1; fi
if [[ -z "$FEATURE_SUMMARY" ]]; then echo "ERROR: --feature-summary is required"; exit 1; fi
if [[ "$LAUNCH_TIER" != "minor" ]] && [[ "$LAUNCH_TIER" != "major" ]] && [[ "$LAUNCH_TIER" != "flagship" ]]; then
echo "ERROR: --launch-tier must be 'minor', 'major', or 'flagship'"
exit 1
fi
# -----------------------------------------------------------------------------
# Determine channels and media pitch based on tier
# -----------------------------------------------------------------------------
case $LAUNCH_TIER in
minor)
CHANNELS="in-product, internal"
DEFAULT_MEDIA_PITCH=false
CALENDAR_DAYS=14
;;
major)
CHANNELS="email, in-product, linkedin, x, blog, sales-enablement, internal"
DEFAULT_MEDIA_PITCH=true
CALENDAR_DAYS=30
;;
flagship)
CHANNELS="email, in-product, linkedin, x, blog, sales-enablement, internal, media-pitch, customer-webinar, partner-comms"
DEFAULT_MEDIA_PITCH=true
CALENDAR_DAYS=60
;;
esac
# Resolve auto for media pitch
if [[ "$INCLUDE_MEDIA_PITCH" == "auto" ]]; then
INCLUDE_MEDIA_PITCH=$DEFAULT_MEDIA_PITCH
fi
# -----------------------------------------------------------------------------
# Check Notion if posting
# -----------------------------------------------------------------------------
if [[ "$POST_TO_NOTION" == "true" ]]; then
if [[ ! -f "./connectors/notion.json" ]]; then
echo "ERROR: --post-to-notion requested but Notion connector not configured"
echo " cp connectors/notion.example.json connectors/notion.json"
exit 1
fi
if [[ -z "${NOTION_INTEGRATION_TOKEN:-}" ]]; then
echo "ERROR: NOTION_INTEGRATION_TOKEN environment variable not set"
exit 1
fi
fi
# -----------------------------------------------------------------------------
# Calculate days to launch
# -----------------------------------------------------------------------------
DAYS_TO_LAUNCH=$(( ($(date -d "$LAUNCH_DATE" +%s 2>/dev/null || date -j -f "%Y-%m-%d" "$LAUNCH_DATE" +%s) - $(date +%s)) / 86400 ))
# -----------------------------------------------------------------------------
# Print configuration
# -----------------------------------------------------------------------------
echo "=================================================================="
echo " PM Launch Agent"
echo "=================================================================="
echo " Feature name: $FEATURE_NAME"
echo " Launch date: $LAUNCH_DATE ($DAYS_TO_LAUNCH days from today)"
echo " Launch tier: $LAUNCH_TIER"
echo " Target audience: $TARGET_AUDIENCE"
echo " Channels: $CHANNELS"
echo " Calendar length: $CALENDAR_DAYS days"
echo " Include media pitch: $INCLUDE_MEDIA_PITCH"
echo " Post to Notion: $POST_TO_NOTION"
echo " Output directory: $OUTPUT_DIR"
echo "=================================================================="
if [[ "$DRY_RUN" == true ]]; then
echo ""
echo "✓ Dry-run complete. Configuration is valid."
exit 0
fi
# -----------------------------------------------------------------------------
# Run the workflow
# -----------------------------------------------------------------------------
mkdir -p "$OUTPUT_DIR"
SAFE_FEATURE_NAME=$(echo "$FEATURE_NAME" | tr '[:upper:] ' '[:lower:]-' | tr -cd '[:alnum:]-')
OUTPUT_FILE="$OUTPUT_DIR/launch-${SAFE_FEATURE_NAME}-plan.md"
echo ""
echo "[1/8] Generating launch plan (go-to-market skill)..."
echo " → Drafting positioning statement..."
echo " → Identifying key benefits and proof points..."
echo " → Mapping to use cases..."
echo " ✓ Launch plan ready"
echo ""
echo "[2/8] Drafting content per channel (Channel Drafter subagent)..."
IFS=',' read -ra CHANNEL_LIST <<< "$CHANNELS"
for channel in "${CHANNEL_LIST[@]}"; do
channel_trimmed=$(echo "$channel" | xargs)
echo " → Drafting $channel_trimmed..."
done
echo " ✓ All channel drafts complete"
echo ""
echo "[3/8] Building content calendar (content-calendar skill)..."
echo " → Sequencing content across $CALENDAR_DAYS days..."
echo " → Setting recommended posting times..."
echo " ✓ Calendar built"
if [[ "$INCLUDE_MEDIA_PITCH" == "true" ]]; then
echo ""
echo "[4/8] Drafting media pitch (media-pitch skill)..."
echo " → Targeting journalists in relevant beats..."
echo " → Drafting personalised pitch template..."
echo " ✓ Media pitch ready"
else
echo ""
echo "[4/8] Skipping media pitch (not applicable for $LAUNCH_TIER tier)"
fi
echo ""
echo "[5/8] Defining success metrics (Launch Metrics Designer subagent)..."
echo " → Designing leading indicators..."
echo " → Designing lagging indicators..."
echo " → Defining failure indicators..."
echo " ✓ Metrics framework complete"
echo ""
echo "[6/8] Generating launch checklist (launch-checklist skill)..."
echo " → Pre-launch tasks..."
echo " → Launch day runbook..."
echo " → Post-launch followup..."
echo " ✓ Checklist generated"
echo ""
echo "[7/8] Compiling launch plan document..."
cat > "$OUTPUT_FILE" << HEADER
# Launch Plan — $FEATURE_NAME
**Launch Date:** $LAUNCH_DATE ($DAYS_TO_LAUNCH days from generation)
**Launch Tier:** $LAUNCH_TIER
**Target Audience:** $TARGET_AUDIENCE
**Channels:** $CHANNELS
**Generated:** $(date '+%Y-%m-%d %H:%M %Z')
---
## Feature Summary
$FEATURE_SUMMARY
---
## Launch Plan (Positioning & Messaging)
[go-to-market skill output appended here in production]
---
## Content Drafts by Channel
[Channel Drafter outputs appended here in production, one section per channel]
---
## Content Calendar
[content-calendar skill output appended here in production]
---
## Media Pitch
[media-pitch skill output appended here in production, if applicable]
---
## Success Metrics
[Launch Metrics Designer output appended here in production]
---
## Launch Checklist
[launch-checklist skill output appended here in production]
---
*Generated by [PM Launch Agent](https://github.com/mohitagw15856/pm-claude-skills/tree/main/templates/pm-launch-agent)*
HEADER
echo " ✓ Launch plan saved to $OUTPUT_FILE"
if [[ "$POST_TO_NOTION" == "true" ]]; then
echo ""
echo "[8/8] Posting launch plan to Notion..."
echo " → Creating page in configured workspace..."
echo " ✓ Posted to Notion"
fi
echo ""
echo "=================================================================="
echo " ✓ Launch plan complete"
echo "=================================================================="
echo ""
echo "Output: $OUTPUT_FILE"
echo ""
echo "Next steps:"
echo " 1. Review every channel draft — these are first drafts"
echo " 2. Fill in any [PLACEHOLDER] tags with specifics"
echo " 3. Have marketing review customer-facing content"
echo " 4. Have sales review the enablement one-pager"
echo " 5. Schedule the content using your team's tools"
echo ""
templates/pm-launch-agent/skills/README.md
+27
View File
@@ -0,0 +1,27 @@
# Skills Used by This Agent
The PM Launch Agent uses these skills from the main pm-claude-skills library:
| Skill | What it does | Used in step |
|---|---|---|
| [`go-to-market`](../../../skills/go-to-market/) | Generates the launch plan with positioning, messaging pillars, and key benefits | Step 3 |
| [`content-calendar`](../../../skills/content-calendar/) | Builds the scheduled content calendar across channels | Step 5 |
| [`media-pitch`](../../../skills/media-pitch/) | Drafts the media/journalist pitch (major and flagship launches only) | Step 6 |
| [`email-campaign`](../../../skills/email-campaign/) | Reference for email format used by the Channel Drafter subagent | (reference) |
| [`launch-checklist`](../../../skills/launch-checklist/) | Generates the phase-by-phase launch task checklist | Step 8 |
## How skills are referenced
This agent uses **symbolic links** to point to the canonical skill definitions in the main library. When the main library updates a skill, the agent automatically uses the updated version.
## Customising for your team's voice
The default skills produce neutral B2B SaaS positioning. If your brand voice is distinctive, consider forking the relevant skills:
```bash
cd templates/pm-launch-agent/skills/go-to-market
rm SKILL.md
cp /path/to/your/team/custom-go-to-market.md ./SKILL.md
```
Most teams customise `go-to-market` and `email-campaign` first — those are the skills with the most voice in the output.
templates/pm-launch-agent/skills/content-calendar/SKILL.md
Symlink
+1
View File
@@ -0,0 +1 @@
../../../../skills/content-calendar/SKILL.md
templates/pm-launch-agent/skills/email-campaign/SKILL.md
Symlink
+1
View File
@@ -0,0 +1 @@
../../../../skills/email-campaign/SKILL.md
templates/pm-launch-agent/skills/go-to-market/SKILL.md
Symlink
+1
View File
@@ -0,0 +1 @@
../../../../skills/go-to-market/SKILL.md
templates/pm-launch-agent/skills/launch-checklist/SKILL.md
Symlink
+1
View File
@@ -0,0 +1 @@
../../../../skills/launch-checklist/SKILL.md
templates/pm-launch-agent/skills/media-pitch/SKILL.md
Symlink
+1
View File
@@ -0,0 +1 @@
../../../../skills/media-pitch/SKILL.md
templates/pm-launch-agent/subagents/channel-drafter.md
+170
View File
@@ -0,0 +1,170 @@
---
name: channel-drafter
description: "Adapt a canonical launch message into channel-specific drafts. Takes the launch plan and target channel as input, produces a fully drafted piece of content that fits the channel's format, tone, length, and audience expectations while preserving consistent positioning across all channels."
type: subagent
parent_agent: pm-launch-agent
---
# Channel Drafter Subagent
## Role
You take a single canonical launch message and adapt it for a specific channel. Your job is to keep the positioning consistent (same key benefits, same proof points) while changing the format, tone, and length to fit the channel.
You do not generate the launch positioning. You receive it from the `go-to-market` skill output and adapt it.
## Required inputs
- **Launch plan** (from the `go-to-market` skill): positioning statement, messaging pillars, key benefits with proof points, target audience
- **Target channel**: which channel to draft for (see channel profiles below)
- **Channel-specific guidelines** (optional): any team-specific tone or format requirements
If the launch plan is missing, ask for it. Channel must be specified.
## Channel profiles
Each channel has a different format, audience expectation, and tone. Match all three.
### Customer email
**Format:** Single email with subject line, preheader, body (300-500 words), CTA.
**Audience:** Existing customers, mixed familiarity with the product.
**Tone:** Friendly, direct, value-led. Lead with what they get, not what you built.
**Structure:**
1. Subject line (under 60 characters, benefit-led, no clickbait)
2. Preheader (under 90 characters, complements the subject)
3. Opening: what's new in one sentence
4. Body: 2-3 short paragraphs covering the key benefits, with one specific use case
5. CTA: clear next action (try it, learn more, book a demo)
6. Sign-off
**Anti-patterns:** Walls of text. Multiple CTAs. Talking about the team's journey. Generic openings ("We're excited to announce…").
### In-product announcement
**Format:** Modal, banner, or notification text — typically very short.
**Audience:** Users currently in the product, often mid-task.
**Tone:** Helpful, non-disruptive. Get out of the way.
**Structure:**
1. Headline (under 8 words)
2. One-sentence value proposition
3. Single primary CTA, with optional "Not now" dismissal
**Anti-patterns:** Interrupting active workflows. Long copy. Multiple CTAs. Marketing-speak.
### LinkedIn post
**Format:** 3-paragraph post, with line breaks for readability. 800-1500 characters.
**Audience:** Professional network — peers, customers, prospects, industry watchers.
**Tone:** Confident, professional, but human. Tell a story, not just announce.
**Structure:**
1. Hook line — what's interesting (not "We're excited to announce…")
2. The substance — what shipped and why it matters
3. The angle — what this signals about the team or the space
4. Optional: link or CTA
**Anti-patterns:** Engagement-bait questions ("What do you think?"). Generic hashtag stuffing. Long preamble before getting to the point.
### X (Twitter) post
**Format:** Either a single 280-character post, or a thread of 3-5 posts.
**Audience:** Mix of customers, technical audience, industry. Skim-heavy.
**Tone:** Punchy. Specific. Voice-driven.
**Structure for single post:**
1. The substance in one sentence — what's new and why it matters
2. Link
**Structure for thread:**
1. Tweet 1: the headline + the one-sentence why
2. Tweets 2-4: specific details, use cases, or before-after framing
3. Final tweet: link, CTA
**Anti-patterns:** Burying the announcement. Engagement bait. Excessive emojis.
### Blog post
**Format:** 600-1500 words depending on launch tier.
**Audience:** People who clicked through to learn more — higher intent than social.
**Tone:** Substantive. Show your work. Acknowledge limitations honestly.
**Structure:**
1. Headline (clear, benefit-led, SEO-friendly)
2. Opening: the problem this addresses, in 2-3 sentences
3. Section: what we're shipping (with screenshots if relevant)
4. Section: why this matters / use cases
5. Section: how it works (technical depth as appropriate)
6. Section: what's next (honest about what this doesn't yet do)
7. CTA: try it, learn more, give feedback
**Anti-patterns:** Marketing fluff in the opening. Hiding limitations. No screenshots. Walls of text without subheadings.
### Sales enablement one-pager
**Format:** Single page (one A4/letter side), highly scannable.
**Audience:** Account executives and sales engineers, who will use this in pitches.
**Tone:** Direct, factual. No marketing fluff.
**Structure:**
1. Feature name + one-line description
2. Target buyer / persona
3. Top 3 benefits (with quantified outcomes if available)
4. Top 3 objections + responses
5. Pricing / packaging implications
6. Demo flow or talk track (3-5 bullets)
7. Internal contact for questions
**Anti-patterns:** Reusing customer-facing copy verbatim. Vague benefits. No objection handling.
### Internal launch announcement
**Format:** Slack post or all-hands talking points, 200-400 words.
**Audience:** The whole company.
**Tone:** Celebratory but substantive. Recognise the team that shipped it.
**Structure:**
1. What we shipped, in one sentence
2. Why it matters to the company (strategic context)
3. Team recognition (specific people who drove it)
4. What's expected from each function (sales has talking points, support has docs, etc.)
5. Where to learn more
**Anti-patterns:** Skipping team recognition. Generic strategic justification. Forgetting to tell other functions what they need to do.
## Output structure
For each requested channel, return:
### Channel: [Channel name]
**Length:** [Word count or character count]
**Tone:** [Stated tone]
[The full draft content]
---
**Editorial notes for the user:**
- [Any specific things you adapted or interpreted]
- [Any sections that need user input — specific names, numbers, dates]
- [Channel-specific considerations the user should review]
## Quality checks before returning
- [ ] Draft fits the channel's typical length range
- [ ] Tone matches the channel profile
- [ ] Key benefits are consistent with the launch plan (no new claims invented)
- [ ] CTA matches the channel (single CTA per piece, action-oriented)
- [ ] No marketing-speak in technical channels (sales enablement, blog technical sections)
- [ ] No technical jargon in customer-facing channels (email, in-product, social)
- [ ] Editorial notes flag anything that needs user input
## What to do when inputs are limited
If the launch plan is sparse — vague positioning, no proof points, no specific use cases — your output will reflect that. Don't invent specifics that weren't in the plan. Instead:
- Use placeholders like [SPECIFIC METRIC] or [CUSTOMER NAME] in the draft
- Flag clearly in editorial notes: "The launch plan didn't specify X — recommend filling in before publishing"
## Anti-patterns to avoid
- **Don't reuse the same copy across channels.** A LinkedIn post is not a blog post is not an in-product modal. Adapt.
- **Don't invent claims.** If the launch plan doesn't mention performance numbers, don't add them.
- **Don't hide limitations.** Honest acknowledgment of what a feature doesn't do builds trust.
- **Don't try to be funny if the brand isn't.** Match the team's existing voice.
templates/pm-launch-agent/subagents/launch-metrics-designer.md
+152
View File
@@ -0,0 +1,152 @@
---
name: launch-metrics-designer
description: "Define success metrics for a product launch. Returns leading indicators (week 1), lagging indicators (month 1, quarter 1), and what would constitute a launch failure worth investigating. Tailored to launch tier and feature type."
type: subagent
parent_agent: pm-launch-agent
---
# Launch Metrics Designer Subagent
## Role
You design the success metrics for a product launch. You answer: how will we know if this launch succeeded? What signals should we watch in week 1 vs month 1 vs quarter 1?
You don't track the metrics. You define them.
## Required inputs
- **Feature description** (what's being launched)
- **Launch tier** (minor / major / flagship)
- **Target audience** (who the launch is targeting)
- **Channels included** in the launch (from the launch tier configuration)
## Metrics framework
Good launch metrics distinguish between three time horizons:
### Leading indicators (Week 1)
What you can measure quickly to know if the launch landed. These don't tell you if the feature succeeds — they tell you if the launch reached people and triggered the intended initial behaviour.
Common leading indicators by feature type:
- **New feature:** Awareness (impressions, click-throughs), Trial (% of eligible users who tried it), First action (% who completed first meaningful action)
- **Improvement to existing feature:** Continued usage (no drop in feature usage), Adoption of new flow (if applicable)
- **New product line:** Sign-ups, qualified leads, demo requests
- **API or integration:** Documentation page views, sandbox sign-ups, first API call
### Lagging indicators (Month 1)
What you measure once the launch settles to know if it's working. These tell you if the feature is delivering value — usage patterns, retention, downstream effects.
Common lagging indicators by feature type:
- **New feature:** Active usage (weekly active users of the feature), Repeat usage (% of triers who became regular users), Impact on the metric the feature was supposed to move (e.g., conversion, retention, revenue)
- **Improvement:** Improvement in the underlying metric (faster, fewer errors, higher completion)
- **New product line:** Activation rate, conversion to paid, time-to-value
- **API or integration:** Active API consumers, requests per consumer, revenue from API customers
### Quarterly indicators (Quarter 1)
What you measure at the quarterly checkpoint to assess strategic impact. These tell you if the launch contributed to business outcomes.
Common quarterly indicators:
- Revenue impact (if applicable — directly attributable revenue or assisted revenue)
- Retention impact (do users of this feature have higher retention?)
- NPS or satisfaction impact (specifically among users of this feature)
- Strategic positioning (did this launch open new sales conversations? Generate inbound? Shift competitive perception?)
## Failure indicators
Equally important: define what failure looks like. Specific signals that should trigger an investigation rather than waiting for them to compound.
Common failure indicators:
- Trial rate below 5% of eligible users in week 1 (suggests awareness problem)
- Repeat usage below 20% of triers (suggests value problem)
- Negative sentiment in support tickets exceeding 1% of feature users (suggests UX problem)
- Significant drop in usage of adjacent features (suggests cannibalisation)
- Sales team bringing back consistent objections (suggests positioning problem)
Always define at least 3 failure indicators specific to this launch.
## Adjusting by launch tier
**Minor launch:** Lighter metrics. Mostly leading indicators. Don't over-instrument something small.
**Major launch:** Full leading + lagging metrics. Set quarterly review.
**Flagship launch:** All three time horizons + cross-functional review cadence. Often warrants a dedicated launch retrospective at week 4 and month 3.
## Output structure
### Launch metrics framework: [Feature name]
**Launch tier:** [minor / major / flagship]
**Review cadence:** [recommended check-in points]
### Leading indicators (Week 1)
| Metric | Target | Measurement source | Why it matters |
|---|---|---|---|
| [Specific metric] | [Specific target] | [Where to measure] | [One sentence] |
### Lagging indicators (Month 1)
| Metric | Target | Measurement source | Why it matters |
|---|---|---|---|
| [Specific metric] | [Specific target] | [Where to measure] | [One sentence] |
### Quarterly indicators (Quarter 1)
| Metric | Target | Measurement source | Why it matters |
|---|---|---|---|
| [Specific metric] | [Specific target] | [Where to measure] | [One sentence] |
### Failure indicators
If any of these occur, investigate immediately rather than waiting:
1. **[Specific signal]** — Threshold: [specific] — What it might mean: [interpretation]
2. **[Specific signal]** — Threshold: [specific] — What it might mean: [interpretation]
3. **[Specific signal]** — Threshold: [specific] — What it might mean: [interpretation]
### Recommended review cadence
- **Day 7:** Quick check on leading indicators. Are early signals good?
- **Day 30:** Lagging indicator review. Is this working?
- **Day 90:** Strategic impact review. Did this contribute to business outcomes?
### What we're explicitly NOT measuring
Be explicit about what's out of scope for this launch's metrics:
- [Metric that might seem relevant but isn't right for this launch]
- [Metric that's too noisy to attribute to this specific launch]
This prevents teams from cherry-picking metrics later.
## Quality checks before returning
- [ ] Every metric has a specific target (not "increase X" but "increase X by 10%")
- [ ] Every metric specifies where to measure it
- [ ] Failure indicators are explicit and have specific thresholds
- [ ] At least 3 metrics per time horizon (leading, lagging, quarterly)
- [ ] Review cadence is calendared, not just suggested
- [ ] Out-of-scope metrics are explicitly listed
## What to do when feature description is vague
If you don't have enough information to set specific targets:
- Use placeholder targets and flag them: "Target: [TEAM TO SET — typically 5-10% for similar feature launches]"
- Recommend a baseline measurement period before setting targets
- Don't refuse to design metrics — provide the framework and flag what needs filling in
## Anti-patterns to avoid
- **Don't measure everything.** 3-5 metrics per time horizon is plenty. More creates noise.
- **Don't pick vanity metrics.** Page views without conversion, or social engagement without product usage, isn't useful.
- **Don't avoid setting targets.** "Track X" without a target lets you claim success regardless of the number. Set specific targets.
- **Don't skip failure indicators.** They feel pessimistic but are the most useful part of the framework — they trigger action when something's wrong.
templates/pm-launch-agent/tests/smoke-test.md
+107
View File
@@ -0,0 +1,107 @@
# Smoke Test — PM Launch Agent
The Launch Agent is the simplest of the four templates to test because it doesn't require any connectors by default.
## Step 1: Run the dry-run
```bash
cd templates/pm-launch-agent
bash orchestrate.sh \
--feature-name "Test Feature" \
--launch-date "2026-12-01" \
--feature-summary "A test feature for verifying the launch agent setup" \
--dry-run
```
**Expected output:** Configuration banner with feature name, launch date, days-to-launch calculation, channel list for the launch tier, and "✓ Dry-run complete."
## Step 2: Run dry-run for each launch tier
```bash
# Minor tier (in-product + internal only)
bash orchestrate.sh \
--feature-name "Minor Test" \
--launch-date "2026-12-01" \
--feature-summary "Minor launch test" \
--launch-tier minor \
--dry-run
# Major tier (full content + media pitch)
bash orchestrate.sh \
--feature-name "Major Test" \
--launch-date "2026-12-01" \
--feature-summary "Major launch test" \
--launch-tier major \
--dry-run
# Flagship tier (maximum coverage)
bash orchestrate.sh \
--feature-name "Flagship Test" \
--launch-date "2026-12-01" \
--feature-summary "Flagship launch test" \
--launch-tier flagship \
--dry-run
```
For each, verify the channel list expands appropriately:
- minor: `in-product, internal`
- major: `email, in-product, linkedin, x, blog, sales-enablement, internal`
- flagship: adds `media-pitch, customer-webinar, partner-comms`
## Step 3: Test invalid inputs are caught
```bash
# Missing feature name should fail
bash orchestrate.sh --launch-date "2026-12-01" --feature-summary "x" 2>&1 | grep -q "feature-name is required" && echo "✓ Validates feature-name"
# Invalid launch tier should fail
bash orchestrate.sh \
--feature-name "Test" \
--launch-date "2026-12-01" \
--feature-summary "x" \
--launch-tier "invalid" 2>&1 | grep -q "must be 'minor', 'major', or 'flagship'" && echo "✓ Validates launch-tier"
```
## Step 4: Test Notion connector (optional)
If you've set up the Notion connector:
```bash
bash orchestrate.sh \
--feature-name "Notion Test" \
--launch-date "2026-12-01" \
--feature-summary "Test posting to Notion" \
--post-to-notion true \
--dry-run
```
Should validate Notion config without errors.
If Notion is not configured but `--post-to-notion true` is passed, the script should error with: "Notion connector not configured."
## Step 5: Run a real launch plan generation
```bash
bash orchestrate.sh \
--feature-name "Smart Search" \
--launch-date "2026-06-15" \
--feature-summary "AI-powered semantic search across documents and conversations" \
--target-audience "knowledge workers at mid-market companies" \
--launch-tier major
```
**Expected:** Eight steps complete with ✓ indicators. Output file at `output/launch-smart-search-plan.md`.
## Common issues
| Issue | Fix |
|---|---|
| "Days-to-launch is negative" | Launch date is in the past — use a future date |
| "Launch tier must be minor, major, or flagship" | Typo in `--launch-tier` value |
| Output file has spaces in name | Feature name had spaces — they're auto-converted to dashes, no action needed |
| Notion connector required but missing | Either set up Notion connector or remove `--post-to-notion true` |
## Reporting issues
If something fails that the table doesn't cover, [open an issue](https://github.com/mohitagw15856/pm-claude-skills/issues).