Launch Plan

Community

assimovt

launch-plan

Plan product launches with the right tier and coordinated checklists. Use when asked to plan a launch, coordinate a release, prepare for go-to-market, or figure out how to announce a new feature or product. Covers silent, soft, and big-bang launch tiers.

Overview

Publisher	assimovt
Repository	`productskills`
Skill name	`launch-plan`
Stars	71
Forks	6
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

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 assimovt on GitHub. Read the source before you install it.

Installation

Install the Launch Plan 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/assimovt/productskills/tree/main/skills/launch-plan
Enable the skill in any chat where you want it available.

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/assimovt/productskills.git /tmp/productskills
mkdir -p .claude/skills
cp -r /tmp/productskills/skills/launch-plan .claude/skills/launch-plan

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

Use it in TypingMind

Enable Launch Plan 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 Plan 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 Plan 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 based on the size of the bet, not the size of your ambition. Most features deserve a silent or soft launch. Save the big-bang for genuinely new products or major pivots. Linear's principle: launch early, launch often, launch multiple times.

Launch Tiers

Tier 1: Silent Launch

Ship it, turn it on, see what happens. No announcement.

Use for: Bug fixes, minor improvements, internal tools, infrastructure changes, experiments.

Checklist:

Feature is behind a flag or gradually rolled out
Monitoring/alerting is in place
Rollback plan exists
One person is on point to watch metrics for 24 hours

Tier 2: Soft Launch

Ship it, tell existing users, collect feedback before going wide.

Use for: New features for existing users, significant UX changes, pricing changes, beta programs.

Checklist:

Changelog entry or in-app notification written
Help docs updated (or created)
Support team briefed with FAQ
Feedback collection mechanism in place (survey, feedback button, Slack channel)
Known limitations documented
Rollback plan exists
1-2 week feedback period before going wide

Example: Launching real-time collaboration — Changelog: "Edit together, see cursors live." Support FAQ covers latency expectations and max concurrent editors. Roll out to 20% of teams for 3 days via feature flag, then 100%. Rollback: disable WebSocket sync, fall back to polling. Feedback widget live for 2 weeks. Success metric: % of teams with 2+ simultaneous editors.

Tier 3: Big-Bang Launch

Coordinated, public, designed for maximum reach. Expensive in time and attention.

Use for: New product launch, major pivot, rebrand, entering a new market. Maximum 2-3 per year.

Checklist:

Product

Feature complete and tested at scale
Onboarding flow tested with 5+ new users
Performance benchmarked under expected load

Content

Landing page or product page live
Blog post / announcement written
Demo video or screenshots prepared
Social posts drafted for launch day and day +1, +3, +7

Distribution

Email to existing users scheduled
Social media posts queued
Community posts drafted (relevant subreddits, Slack groups, Discord)
Product Hunt launch prepared (if applicable)
Influencer/partner outreach done 1 week before

Support

Support team briefed and staffed for launch day
FAQ and known issues documented
Escalation path defined

Measurement

Success metrics defined before launch (not after)
Analytics tracking verified
Daily review scheduled for first week

Post-Launch

Regardless of tier:

Day 1: Watch metrics. Fix anything broken. Respond to all feedback.
Day 3: First retro — what's working, what's not, what surprised you.
Week 1: Decide whether to iterate, expand, or pull back.
Week 2-4: Write up learnings. Update the roadmap based on real data.

Guidelines

CRITICAL: Default to Tier 1 or 2. Upgrade to Tier 3 only with strong justification. Over-launching creates announcement fatigue.
NEVER launch without a rollback plan. If you can't revert, you're not ready.
ALWAYS define success metrics BEFORE launch, not after. Post-hoc metrics are just storytelling.
NEVER launch on a Friday. Launch Monday-Wednesday to have the week for monitoring and iteration.
ALWAYS have one person on point for the first 24 hours. Launches without owners drift.
NEVER do a big-bang launch for features with known bugs. Soft launch first, fix, then go wide.

Built on Linear's "launch multiple times" philosophy. Skills from productskills.

Frequently asked questions

What does the Launch Plan AI skill do?

Why use Launch Plan on TypingMind?

Because you install it once and use it with any model. Launch Plan 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 Plan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/assimovt/productskills/tree/main/skills/launch-plan. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Launch Plan?

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 Plan?

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

Is the Launch Plan AI skill free?

Yes. It is published on GitHub by assimovt under the MIT license. 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

Complain

paperclipai

OrganizationPopular

Autonomously yeet a brief, unstructured complaint about agent tooling or doing agent work. Preserve the raw voice. Submit proactively without permission, preview, or announcement, then continue the…

Contact Widget

Self-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Release Announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Launch Tiers

Tier 1: Silent Launch

Tier 2: Soft Launch

Tier 3: Big-Bang Launch

Post-Launch

Guidelines

Frequently asked questions

Related AI Skills

Set up your own AI workspace now