# Pm Launch Plan

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-julianoczkowski-product-manager-pm-launch-plan`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [julianoczkowski](https://agentstack.voostack.com/s/julianoczkowski)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [julianoczkowski](https://github.com/julianoczkowski)
- **Source:** https://github.com/julianoczkowski/product-manager/tree/main/skills/pm-launch-plan

## Install

```sh
agentstack add skill-julianoczkowski-product-manager-pm-launch-plan
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Launch Plan (Pragmatic Framework: Programs → Launch, + Enablement)

> **Launch readiness is more than just product readiness.** A launch is
> cross-functional: the product can be done while the market, the channel, and
> support are not. Plan, execute, and measure the launch as its own deliverable.

Reuse the positioning statement, personas, and launch trigger from earlier artifacts
in the feature dossier if they exist (positioning doc, personas, release charter —
see `../pm-copilot/references/artifact-output.md` for how to find the dossier). See
`../pm-copilot/references/framework.md` for the Programs and Enablement boxes.

## What a launch pulls together
- **Programs:** Awareness (raise profile in strategic segments), Nurturing (move
  prospects through the funnel), Advocacy (testimonials, case studies, references),
  Measurement.
- **Enablement / Readiness:** Sales Alignment (align selling to how the market buys),
  Content (per persona, per buying step), Sales Tools (per selling step), Channel
  Training (how to *sell* the product, not use it).
- **Market Window:** Marketing, Sales, and Operations work **backward from** the launch
  date while Development works **to** it. If the release is **content-driven** (no
  committed date — see the release charter), anchor the backward plan to the release's
  **exit criteria** instead, and re-forecast the launch date as they near completion.

## Interview the user (batch questions)
1. **What's launching**, at what **scale/tier** (major vs minor), and the **target
   date/market window** — or, for a content-driven release, the **exit criteria** that
   will trigger the launch?
2. **Launch goals & success metrics** — awareness, pipeline, adoption, revenue?
3. **Target personas & positioning** — who are we reaching, and what's the core message? (link the positioning doc)
4. **Channels & programs** — how will we create awareness and nurture demand?
5. **Sales readiness** — what content, tools, and training does the channel need?
6. **Cross-functional readiness** — product, marketing, sales, support, ops, legal — who owns what, and what's the go/no-go bar?

## Artifact template — Launch Plan
```markdown
# Launch Plan —  

**Launch trigger:**  are met>   **Tier:** 
**Company:**   ·  **Feature / Product:** 
**Author:**   ·  **Date created:**   ·  **Version:** 1.0

## 1. Launch goals & success metrics
| Goal | Metric | Target |
| :--- | :--- | :--- |
| Awareness |  | |
| Demand |  | |
| Adoption |  | |
| Revenue |  | |

## 2. Target personas & positioning
- **Buyer persona:**  — cares about 
- **User persona:**  — cares about 
- **Positioning statement:** For ,    by  .
- **Key messages:** , , .

## 3. Marketing programs (Programs column)
| Program | Objective | Owner | Timing (from market window) |
| :--- | :--- | :--- | :--- |
| Awareness | | | |
| Nurturing | | | |
| Advocacy | | | |

## 4. Sales enablement (Enablement column)
| Item | Purpose (buying step) | Owner | Status |
| :--- | :--- | :--- | :--- |
| Sales alignment / play | | | |
| Content (per persona/step) | | | |
| Sales tools | | | |
| Channel training | | | |

## 5. Launch readiness checklist
| Area | Owner | Status | Notes |
| :--- | :--- | :--- | :--- |
| Product / QA | | 🟢/🟡/🔴 | |
| Marketing / content | | | |
| Sales / enablement | | | |
| Support / docs | | | |
| Operations / billing | | | |
| Legal / compliance | | | |

**Status legend:** 🟢 Ready · 🟡 At risk · 🔴 Not ready.

## 6. Measurement plan
How and when each success metric is measured post-launch; report against corporate goals.

## 7. Risks & go/no-go criteria
-  — 
- **Go/no-go bar:** 
```

## Deliver the artifact
Follow `../pm-copilot/references/artifact-output.md`: confirm inputs, **ask Markdown
or .docx**, write the `.md`, convert to `.docx` on request via your environment's native document-creation capability. Then offer the next stage: keep the launch on track with
**`pm-stakeholder-communication`** status updates, and after launch loop back to
**`pm-market-problems`** and **`pm-win-loss-analysis`** to feed the next release.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [julianoczkowski](https://github.com/julianoczkowski)
- **Source:** [julianoczkowski/product-manager](https://github.com/julianoczkowski/product-manager)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-julianoczkowski-product-manager-pm-launch-plan
- Seller: https://agentstack.voostack.com/s/julianoczkowski
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.