Install
$ agentstack add skill-julianoczkowski-product-manager-pm-launch-plan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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)
- 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?
- Launch goals & success metrics — awareness, pipeline, adoption, revenue?
- Target personas & positioning — who are we reaching, and what's the core message? (link the positioning doc)
- Channels & programs — how will we create awareness and nurture demand?
- Sales readiness — what content, tools, and training does the channel need?
- Cross-functional readiness — product, marketing, sales, support, ops, legal — who owns what, and what's the go/no-go bar?
Artifact template — Launch Plan
# 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
- Source: julianoczkowski/product-manager
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.