assimovt/launch-plan
skills/launch-plan/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add assimovt/productskills launch-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 3, 2026, 11:52 AM4.5s1 file scanned
SKILL.md
- name:
- launch-plan
- description:
- >
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.
Related Skills
assimovt/user-interview
development
VerifiedTrustedCommunity
Prepare and conduct user interviews that extract truth, not validation. Use when asked to create an interview guide, prepare for user interviews, plan customer discovery, or talk to users. Built on The Mom Test and YC's Five Questions framework for startup customer development.
33SKILL.mdUpdated Apr 3, 2026
assimovt/strategy-doc
documentation
VerifiedTrustedCommunity
Write product strategy documents with real tradeoffs and clear choices. Use when asked to write a product strategy, define strategic direction, create a strategy doc, or articulate where to play and how to win. Built on Playing to Win and Rumelt's Strategy Kernel.
33SKILL.mdUpdated Apr 3, 2026
assimovt/scope-cutting
tools
VerifiedTrustedCommunity
Cut scope ruthlessly using Shape Up's appetite-first approach. Use when asked to reduce scope, find the MVP, trim features, ship faster, or figure out what to cut. Applies fixed time variable scope thinking and scope hammering techniques.
33SKILL.mdUpdated Apr 3, 2026
assimovt/roadmap-planning
development
VerifiedTrustedCommunity
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.
33SKILL.mdUpdated Apr 3, 2026