Launch Planning

Community

Productfculty-aipm

launch-planning

Use this skill when the user asks to "plan a launch", "create a launch plan", "how do I launch this feature", "launch checklist", "go-to-market plan for this feature", "launch timeline", "prepare for launch", or needs a structured plan for taking a feature or product from "ready to ship" to "in users' hands with people knowing about it".

Overview

Publisher	Productfculty-aipm
Repository	`PM-Copilot-by-Product-Faculty`
Skill name	`launch-planning`
Stars	80
Forks	34
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the Launch Planning AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/launch-planning
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/launch-planning

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/launch-planning .claude/skills/launch-planning

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Launch Planning in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Launch Planning on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Launch Planning is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Launch Planning

You are creating a launch plan — a structured timeline and checklist that ensures a feature or product is shipped, communicated, and measured effectively. Launches fail most often not because of product quality, but because of poor coordination, missing communications, or unmeasured impact.

Framework: April Dunford (positioning-first launch), Lenny Rachitsky (GTM frameworks), Teresa Torres (outcome measurement).

Step 1 — Load Context

Read memory/user-profile.md for product context, stakeholders, and stack (issue tracker, comms tools). Read context/product/roadmap.md for launch timeline and OKR context.

Step 2 — Launch Scope Classification

Not all launches are created equal. Classify the launch to right-size the plan:

Tier 1 — Full launch (maximum coordination): Major feature or product release. Affects most users. Requires: press/blog, email, in-app, coordinated sales/CS briefing, social media. Examples: New product, major redesign, pricing change, new tier launch.

Tier 2 — Feature launch (moderate coordination): Significant new capability. Affects a meaningful segment. Requires: in-app announcement, email to affected segment, CS briefing. Examples: New integration, major workflow improvement, key requested feature.

Tier 3 — Incremental update (light coordination): Quality improvements, minor features, bug fixes. Requires: changelog entry, brief CS note if it affects common workflows. Examples: Performance improvements, small UX fixes, minor capability additions.

Ask the user which tier applies, or help them classify it.

Step 3 — Pre-Launch Checklist

For Tier 1 or 2 launches, verify before launch day:

Product readiness:

Feature is complete and tested in staging
All acceptance criteria from the PRD are met
Edge cases and failure modes are handled
Analytics instrumentation is in place (can you measure success?)
Feature flag configured (if applicable — allows instant rollback)

Content readiness:

Launch announcement written (for each channel)
Help documentation updated
Support team briefed on what's changing and common questions
Customer success team briefed (for any enterprise customers who need heads-up)

Coordination readiness:

All stakeholders know the launch date
Sales team briefed (if applicable)
Leadership is aware
External partners notified (if this affects an integration)

Measurement readiness:

Success metrics are defined and instrumented
Baseline measurements taken before launch
First review date scheduled (T+7 days)

Step 4 — Launch Timeline

Build a launch timeline working backward from the launch date:

T-	Action	Owner
T-14	Feature complete in staging; acceptance criteria review	Engineering
T-10	Write all launch communications; send to stakeholders for review	PM
T-7	Finalize help docs; brief support team	PM + Support
T-5	Brief CS/Sales; confirm partner notifications sent	PM + CS
T-3	Final testing in staging; confirm feature flag is ready	Engineering
T-1	All communications pre-scheduled; team on standby	PM
T-0	Deploy to production; activate feature flag; publish communications	Engineering + PM
T+1	Monitor metrics; address early support volume	PM
T+7	First metrics review; quick wins documented	PM
T+14	Full impact assessment; lessons captured	PM

Step 5 — Rollback Plan

Define the rollback plan before launch day:

Trigger: At what metric threshold would we roll back? (e.g., error rate > 5%, core metric drops > 10%)
How to roll back: Feature flag? Code revert? Who executes it?
Who decides to roll back? One named decision-maker — not a committee
Communication plan: What do we tell users if we roll back?

Step 6 — Post-Launch Review

Schedule:

T+7 day review: Is the feature being used? Are there unexpected issues? Is the metric moving?
T+30 day review: Full impact assessment against success metrics from the PRD. Document lessons learned.
Memory update: Offer to save launch lessons to memory/user-profile.md

Step 7 — Output

Produce:

Launch tier classification with rationale
Pre-launch checklist (completed with owners and deadlines)
Launch timeline table
Rollback plan
Post-launch review schedule
Draft launch announcement (or reference the launch-announcement skill)

Frequently asked questions

What does the Launch Planning AI skill do?

Why use Launch Planning on TypingMind?

Because you install it once and use it with any model. Launch Planning is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Launch Planning in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/launch-planning. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Launch Planning?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Launch Planning?

As many as you like. As long as a model supports skills, you can use Launch Planning with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Launch Planning AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Content Engine

affaan-m

CommunityPopular

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content…

Crosspost

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user…

Deep Research

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any…

Documentation Lookup

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Launch Planning

Step 1 — Load Context

Step 2 — Launch Scope Classification

Step 3 — Pre-Launch Checklist

Step 4 — Launch Timeline

Step 5 — Rollback Plan

Step 6 — Post-Launch Review

Step 7 — Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now