Launch Strategy
- 583 installs
- 23.5k repo stars
- Updated July 17, 2026
- alirezarezvani/claude-skills
launch-strategy is an agent skill that plans repeatable SaaS product and feature launches using Owned, Rented, and Borrowed channel frameworks, phased timelines, and a 0–100 readiness scorer for developers shipping relea
About
launch-strategy is a marketing agent skill (version 1.0.0) for planning SaaS product and feature launches with compounding momentum instead of one-off posts. It centers on the ORB model—Owned channels like email and blog, Rented channels like social platforms, and Borrowed channels like partners, newsletters, and Product Hunt—and a three-phase timeline: pre-launch (2–6 weeks), launch day, and post-launch (30 days). Output artifacts include a phase-by-phase launch plan, ORB channel map, launch-day checklist, Product Hunt brief, and post-launch momentum list. A bundled launch_readiness_scorer.py script scores checklist JSON categories from 0–100 and flags weakest areas before committing a launch date. The skill triggers on mentions of go-to-market, beta access, waitlists, feature releases, and pricing-change announcements, integrating with email-sequence and social-content sibling skills for execution copy while keeping channel strategy and timing in one repeatable playbook.
- ORB framework: owned (email, blog, community), rented (social, ads), and borrowed (partners, press) with traffic back to
- Treats every feature and update as a launch moment to compound momentum over time
- Emphasizes early user access and real feedback loops before big-bang announcements
- Includes concrete play patterns such as invite-only waitlists and high-touch onboarding demos
- Positions owned channels as long-term compounders versus algorithm-dependent rented reach
Launch Strategy by the numbers
- 583 all-time installs (skills.sh)
- Ranked #696 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill launch-strategyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 583 |
|---|---|
| repo stars | ★ 23.5k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 17, 2026 |
| Repository | alirezarezvani/claude-skills ↗ |
How do you plan a repeatable SaaS feature launch?
Plan repeatable product and feature launches using owned, rented, and borrowed channels instead of one-off release posts.
Who is it for?
Product and engineering leaders preparing phased SaaS launches with owned, rented, and borrowed channel coverage and measurable readiness gates.
Skip if: Teams shipping silent backend refactors with no user-facing announcement or developers seeking implementation code rather than go-to-market planning.
When should I use this skill?
A user mentions launch, Product Hunt, go-to-market, feature release, waitlist, or beta access for a shipped product.
What you get
Launch plan markdown, ORB channel map, launch-day checklist, Product Hunt brief, and readiness score report
- Launch plan document
- ORB channel map
- Readiness score report
By the numbers
- ORB framework covers 3 channel types: Owned, Rented, and Borrowed
- Phase model spans pre-launch, launch day, and 30-day post-launch windows
- Readiness scorer outputs a 0–100 launch readiness score
Files
Launch Strategy
You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
Before Starting
Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
---
Core Philosophy
A launch is a momentum system, not a day. Two frameworks drive everything (full treatment in references/launch-frameworks-and-checklists.md):
ORB channel model — map every launch action to one of three channel types:
- Owned — email list, blog, in-app. You control reach; activate first.
- Rented — social platforms, communities. Algorithmic reach; you play by their rules.
- Borrowed — partner audiences, newsletters, podcasts, Product Hunt. Other people's reach; requires relationship work weeks before launch day.
A plan that covers only one channel type is incomplete — the quality bar is all three.
Phase model — sequence the launch instead of betting on one day: 1. Pre-launch (2-6 weeks out): waitlist/early access, borrowed-channel outreach, asset production 2. Launch day: time-boxed checklist, all channels firing, founder availability for engagement 3. Post-launch (30 days): momentum content — comparison pages, case studies, roundup email, retargeting
Tools
| Tool | Invocation | Output |
|---|---|---|
| Readiness scorer | python3 scripts/launch_readiness_scorer.py --checklist launch.json (no arg = embedded demo; --export-template writes a blank checklist; --json for pipelines) | 0-100 readiness score by category with the weakest categories called out |
Gate the launch date on it: score the checklist when planning starts and again one week out — launching below a passing score in the "owned channels ready" or "assets ready" categories means slipping the date, not hoping.
Task-Specific Questions
1. What are you launching? (New product, major feature, minor update) 2. What's your current audience size and engagement? 3. What owned channels do you have? (Email list size, blog traffic, community) 4. What's your timeline for launch? 5. Have you launched before? What worked/didn't work? 6. Are you considering Product Hunt? What's your preparation status?
---
Proactive Triggers
Proactively offer launch planning when:
1. Feature ship date mentioned — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity. 2. Waitlist or early access mentioned — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page. 3. Product Hunt consideration — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline. 4. Post-launch silence — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo). 5. Pricing change planned — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.
---
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| Launch Plan | Markdown doc | Phase-by-phase plan with owners, dates, channels, and success metrics |
| ORB Channel Map | Table | Owned/Rented/Borrowed channel strategy with tactics per channel |
| Launch Day Checklist | Checklist | Complete day-of execution checklist with time-boxed actions |
| Product Hunt Brief | Markdown doc | Listing copy, asset specs, pre-launch timeline, engagement playbook |
| Post-Launch Momentum Plan | Bulleted list | 30-day post-launch actions to sustain and compound the launch |
---
Communication
Launch plans should be concrete, time-bound, and channel-specific — no vague "post on social media" recommendations. Every output should specify who does what and when. Reference marketing-context to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.
---
Related Skills
- email-sequence — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.
- social-content — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.
- paid-ads — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.
- content-strategy — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.
- pricing-strategy — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.
- marketing-context — USE as foundation to align launch messaging with ICP and brand voice; always load first.
launch-strategy reference
Core Philosophy
The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
A strong launch isn't about a single moment. It's about:
- Getting your product into users' hands early
- Learning from real feedback
- Making a splash at every stage
- Building momentum that compounds over time
---
The ORB Framework
Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
Owned Channels
You own the channel (though not the audience). Direct access without algorithms or platform rules.
Examples:
- Email list
- Blog
- Podcast
- Branded community (Slack, Discord)
- Website/product
Why they matter:
- Get more effective over time
- No algorithm changes or pay-to-play
- Direct relationship with audience
- Compound value from content
Start with 1-2 based on audience:
- Industry lacks quality content → Start a blog
- People want direct updates → Focus on email
- Engagement matters → Build a community
Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
Rented Channels
Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
Examples:
- Social media (Twitter/X, LinkedIn, Instagram)
- App stores and marketplaces
- YouTube
How to use correctly:
- Pick 1-2 platforms where your audience is active
- Use them to drive traffic to owned channels
- Don't rely on them as your only strategy
Example - Notion: Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
Platform-specific tactics:
- Twitter/X: Threads that spark conversation → link to newsletter
- LinkedIn: High-value posts → lead to gated content or email signup
- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
Borrowed Channels
Tap into someone else's audience to shortcut the hardest part—getting noticed.
Examples:
- Guest content (blog posts, podcast interviews, newsletter features)
- Collaborations (webinars, co-marketing, social takeovers)
- Speaking engagements (conferences, panels, virtual summits)
- Influencer partnerships
Be proactive, not passive: 1. List industry leaders your audience follows 2. Pitch win-win collaborations 3. Use tools like SparkToro or Listen Notes to find audience overlap 4. Set up affiliate/referral incentives
Example - TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
---
Five-Phase Launch Approach
Launching isn't a one-day event. It's a phased process that builds momentum.
Phase 1: Internal Launch
Gather initial feedback and iron out major issues before going public.
Actions:
- Recruit early users one-on-one to test for free
- Collect feedback on usability gaps and missing features
- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
Goal: Validate core functionality with friendly users.
Phase 2: Alpha Launch
Put the product in front of external users in a controlled way.
Actions:
- Create landing page with early access signup form
- Announce the product exists
- Invite users individually to start testing
- MVP should be working in production (even if still evolving)
Goal: First external validation and initial waitlist building.
Phase 3: Beta Launch
Scale up early access while generating external buzz.
Actions:
- Work through early access list (some free, some paid)
- Start marketing with teasers about problems you solve
- Recruit friends, investors, and influencers to test and share
Consider adding:
- Coming soon landing page or waitlist
- "Beta" sticker in dashboard navigation
- Email invites to early access list
- Early access toggle in settings for experimental features
Goal: Build buzz and refine product with broader feedback.
Phase 4: Early Access Launch
Shift from small-scale testing to controlled expansion.
Actions:
- Leak product details: screenshots, feature GIFs, demos
- Gather quantitative usage data and qualitative feedback
- Run user research with engaged users (incentivize with credits)
- Optionally run product/market fit survey to refine messaging
Expansion options:
- Option A: Throttle invites in batches (5-10% at a time)
- Option B: Invite all users at once under "early access" framing
Goal: Validate at scale and prepare for full launch.
Phase 5: Full Launch
Open the floodgates.
Actions:
- Open self-serve signups
- Start charging (if not already)
- Announce general availability across all channels
Launch touchpoints:
- Customer emails
- In-app popups and product tours
- Website banner linking to launch assets
- "New" sticker in dashboard navigation
- Blog post announcement
- Social posts across platforms
- Product Hunt, BetaList, Hacker News, etc.
Goal: Maximum visibility and conversion to paying users.
---
Product Hunt Launch Strategy
Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
Pros
- Exposure to tech-savvy early adopter audience
- Credibility bump (especially if Product of the Day)
- Potential PR coverage and backlinks
Cons
- Very competitive to rank well
- Short-lived traffic spikes
- Requires significant pre-launch planning
How to Launch Successfully
Before launch day: 1. Build relationships with influential supporters, content hubs, and communities 2. Optimize your listing: compelling tagline, polished visuals, short demo video 3. Study successful launches to identify what worked 4. Engage in relevant communities—provide value before pitching 5. Prepare your team for all-day engagement
On launch day: 1. Treat it as an all-day event 2. Respond to every comment in real-time 3. Answer questions and spark discussions 4. Encourage your existing audience to engage 5. Direct traffic back to your site to capture signups
After launch day: 1. Follow up with everyone who engaged 2. Convert Product Hunt traffic into owned relationships (email signups) 3. Continue momentum with post-launch content
Case Studies
SavvyCal (Scheduling tool):
- Optimized landing page and onboarding before launch
- Built relationships with productivity/SaaS influencers in advance
- Responded to every comment on launch day
- Result: #2 Product of the Month
Reform (Form builder):
- Studied successful launches and applied insights
- Crafted clear tagline, polished visuals, demo video
- Engaged in communities before launch (provided value first)
- Treated launch as all-day engagement event
- Directed traffic to capture signups
- Result: #1 Product of the Day
---
Post-Launch Product Marketing
Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
Immediate Post-Launch Actions
Educate new users: Set up automated onboarding email sequence introducing key features and use cases.
Reinforce the launch: Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
Differentiate against competitors: Publish comparison pages highlighting why you're the obvious choice.
Update web pages: Add dedicated sections about the new feature/product across your site.
Offer hands-on preview: Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
Keep Momentum Going
It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
---
Ongoing Launch Strategy
Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
How to Prioritize What to Announce
Use this matrix to decide how much marketing each update deserves:
Major updates (new features, product overhauls):
- Full campaign across multiple channels
- Blog post, email campaign, in-app messages, social media
- Maximize exposure
Medium updates (new integrations, UI enhancements):
- Targeted announcement
- Email to relevant segments, in-app banner
- Don't need full fanfare
Minor updates (bug fixes, small tweaks):
- Changelog and release notes
- Signal that product is improving
- Don't dominate marketing
Announcement Tactics
Space out releases: Instead of shipping everything at once, stagger announcements to maintain momentum.
Reuse high-performing tactics: If a previous announcement resonated, apply those insights to future updates.
Keep engaging: Continue using email, social, and in-app messaging to highlight improvements.
Signal active development: Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.
---
Launch Checklist
Pre-Launch
- [ ] Landing page with clear value proposition
- [ ] Email capture / waitlist signup
- [ ] Early access list built
- [ ] Owned channels established (email, blog, community)
- [ ] Rented channel presence (social profiles optimized)
- [ ] Borrowed channel opportunities identified (podcasts, influencers)
- [ ] Product Hunt listing prepared (if using)
- [ ] Launch assets created (screenshots, demo video, GIFs)
- [ ] Onboarding flow ready
- [ ] Analytics/tracking in place
Launch Day
- [ ] Announcement email to list
- [ ] Blog post published
- [ ] Social posts scheduled and posted
- [ ] Product Hunt listing live (if using)
- [ ] In-app announcement for existing users
- [ ] Website banner/notification active
- [ ] Team ready to engage and respond
- [ ] Monitor for issues and feedback
Post-Launch
- [ ] Onboarding email sequence active
- [ ] Follow-up with engaged prospects
- [ ] Roundup email includes announcement
- [ ] Comparison pages published
- [ ] Interactive demo created
- [ ] Gather and act on feedback
- [ ] Plan next launch moment
---
#!/usr/bin/env python3
"""
launch_readiness_scorer.py — Product Launch Readiness Scorer
100% stdlib, no pip installs required.
Usage:
python3 launch_readiness_scorer.py # demo mode
python3 launch_readiness_scorer.py --checklist checklist.json
python3 launch_readiness_scorer.py --checklist checklist.json --json
python3 launch_readiness_scorer.py --export-template > my_checklist.json
checklist.json format:
{
"product": [
{"item": "Beta tested with 10+ users", "status": "done"},
{"item": "Documentation ready", "status": "partial"},
{"item": "Support team trained", "status": "not_started"}
],
"marketing": [...],
"technical": [...]
}
Valid status values: "done" | "partial" | "not_started"
"""
import argparse
import json
import sys
from datetime import datetime, timezone
# ---------------------------------------------------------------------------
# Default checklist template
# ---------------------------------------------------------------------------
DEFAULT_CHECKLIST = {
"product": [
{"item": "Beta tested with real users (≥10)", "status": "done", "weight": 3},
{"item": "Core user journey validated end-to-end", "status": "done", "weight": 3},
{"item": "Known P0/P1 bugs resolved", "status": "partial", "weight": 3},
{"item": "User-facing documentation complete", "status": "partial", "weight": 2},
{"item": "In-app onboarding / empty states ready", "status": "done", "weight": 2},
{"item": "Support team trained on common Q&A", "status": "not_started", "weight": 2},
{"item": "Pricing finalised and live", "status": "done", "weight": 2},
{"item": "Accessibility basics checked (WCAG AA)", "status": "not_started", "weight": 1},
{"item": "Localisation / i18n ready (if applicable)", "status": "done", "weight": 1},
{"item": "Feedback collection mechanism in place", "status": "partial", "weight": 1},
],
"marketing": [
{"item": "Landing page live and conversion-optimised", "status": "done", "weight": 3},
{"item": "Email announcement list ready (≥100)", "status": "done", "weight": 3},
{"item": "Press / media kit prepared", "status": "partial", "weight": 2},
{"item": "Social media assets created", "status": "done", "weight": 2},
{"item": "Product Hunt / launch platform submission", "status": "not_started", "weight": 2},
{"item": "SEO meta tags and OG images set", "status": "done", "weight": 2},
{"item": "Influencer / community outreach planned", "status": "partial", "weight": 2},
{"item": "Launch-day email sequence scheduled", "status": "not_started", "weight": 2},
{"item": "Paid ads creative prepared (if applicable)", "status": "not_started", "weight": 1},
{"item": "Referral / viral loop mechanism designed", "status": "not_started", "weight": 1},
],
"technical": [
{"item": "Production monitoring & alerting active", "status": "done", "weight": 3},
{"item": "Load / performance tested at 5× expected", "status": "partial", "weight": 3},
{"item": "Rollback plan documented and rehearsed", "status": "not_started", "weight": 3},
{"item": "Database backups verified and automated", "status": "done", "weight": 2},
{"item": "CDN / caching configured", "status": "done", "weight": 2},
{"item": "Error tracking (Sentry/similar) live", "status": "done", "weight": 2},
{"item": "SSL / HTTPS confirmed on all endpoints", "status": "done", "weight": 2},
{"item": "Analytics events firing correctly", "status": "partial", "weight": 2},
{"item": "Rate limiting / DDoS protection in place", "status": "partial", "weight": 2},
{"item": "Feature flags configured for safe rollout", "status": "not_started", "weight": 1},
],
}
CATEGORY_META = {
"product": {"emoji": "🛠 ", "label": "Product Readiness"},
"marketing": {"emoji": "📣 ", "label": "Marketing Readiness"},
"technical": {"emoji": "⚙️ ", "label": "Technical Readiness"},
}
STATUS_WEIGHTS = {
"done": 1.0,
"partial": 0.5,
"not_started": 0.0,
}
BLOCKERS_THRESHOLD = 0.0 # not_started items with weight ≥3 are blockers
# ---------------------------------------------------------------------------
# Core scoring
# ---------------------------------------------------------------------------
def score_category(items: list) -> dict:
"""Score a single category 0-100 using weighted item scores."""
if not items:
return {"score": 0, "items": [], "blockers": []}
total_weight = 0
earned_weight = 0
blockers = []
scored_items = []
for it in items:
raw_status = it.get("status", "not_started").strip().lower()
status = raw_status if raw_status in STATUS_WEIGHTS else "not_started"
weight = it.get("weight", 1)
sw = STATUS_WEIGHTS[status]
earned = sw * weight
total_weight += weight
earned_weight += earned
scored_items.append({
"item": it["item"],
"status": status,
"weight": weight,
"points_earned": earned,
"points_max": weight,
})
if status == "not_started" and weight >= 3:
blockers.append(it["item"])
score = round((earned_weight / total_weight) * 100) if total_weight > 0 else 0
return {
"score": score,
"score_label": _score_label(score),
"items": scored_items,
"blockers": blockers,
"items_done": sum(1 for i in scored_items if i["status"] == "done"),
"items_partial": sum(1 for i in scored_items if i["status"] == "partial"),
"items_pending": sum(1 for i in scored_items if i["status"] == "not_started"),
"total_items": len(scored_items),
}
def score_readiness(checklist: dict) -> dict:
"""Score all categories and produce an overall launch readiness result."""
categories = {}
all_scores = []
all_blockers = []
for cat, items in checklist.items():
result = score_category(items)
categories[cat] = result
all_scores.append(result["score"])
all_blockers.extend(result["blockers"])
overall = round(sum(all_scores) / len(all_scores)) if all_scores else 0
return {
"overall": {
"score": overall,
"score_label": _score_label(overall),
"launch_decision": _launch_decision(overall, all_blockers),
"blockers": all_blockers,
"generated_at": datetime.now(timezone.utc).strftime("%Y-%m-%dT%H:%M:%SZ"),
},
"categories": {
cat: {**CATEGORY_META.get(cat, {"emoji": "📋", "label": cat.title()}),
**res}
for cat, res in categories.items()
},
"action_plan": _action_plan(categories),
}
def _launch_decision(score: int, blockers: list) -> str:
if blockers:
return f"⛔ NOT READY — {len(blockers)} blocker(s) must be resolved before launch."
if score >= 80:
return "✅ LAUNCH READY — all categories are in good shape."
if score >= 60:
return "🟡 CONDITIONAL — address partial items but launch is defensible."
if score >= 40:
return "🟠 CAUTION — significant gaps; soft launch / waitlist recommended."
return "🔴 NOT READY — major preparation required across multiple areas."
def _action_plan(categories: dict) -> list:
"""Build a prioritised action list: blockers first, then by score ascending."""
actions = []
for cat, res in categories.items():
label = CATEGORY_META.get(cat, {}).get("label", cat.title())
for bl in res.get("blockers", []):
actions.append({
"priority": "🚨 BLOCKER",
"category": label,
"action": bl,
})
for cat, res in sorted(categories.items(), key=lambda x: x[1]["score"]):
label = CATEGORY_META.get(cat, {}).get("label", cat.title())
for it in res.get("items", []):
if it["status"] == "partial":
actions.append({
"priority": "⚠️ PARTIAL",
"category": label,
"action": f"Complete: {it['item']}",
})
return actions[:15] # top 15 actions
def _score_label(s: int) -> str:
if s >= 90: return "Excellent"
if s >= 75: return "Good"
if s >= 60: return "Fair"
if s >= 40: return "Poor"
return "Critical"
# ---------------------------------------------------------------------------
# Pretty-print
# ---------------------------------------------------------------------------
def pretty_print(result: dict) -> None:
ov = result["overall"]
print("\n" + "=" * 65)
print(" 🚀 LAUNCH READINESS SCORER")
print("=" * 65)
print(f"\n Overall Score : {ov['score']}/100 ({ov['score_label']})")
print(f" Launch Decision : {ov['launch_decision']}")
if ov["blockers"]:
print(f"\n 🚨 BLOCKERS ({len(ov['blockers'])}):")
for b in ov["blockers"]:
print(f" • {b}")
print(f"\n{'─'*65}")
print(f" {'CATEGORY':<30} {'SCORE':>6} {'DONE':>5} {'PARTIAL':>7} {'PENDING':>7}")
print(f"{'─'*65}")
for cat, res in result["categories"].items():
bar = "█" * (res["score"] // 10) + "░" * (10 - res["score"] // 10)
print(f" {res['emoji']} {res['label']:<27} {res['score']:>5}/100 "
f"{res['items_done']:>5} {res['items_partial']:>7} {res['items_pending']:>7} {bar}")
print(f"\n{'─'*65}")
print(f" 🗂 CATEGORY DETAILS\n")
for cat, res in result["categories"].items():
print(f" {res['emoji']} {res['label']} — {res['score']}/100 ({res['score_label']})")
for it in res["items"]:
icon = {"done": "✅", "partial": "🔶", "not_started": "⬜"}.get(it["status"], "⬜")
print(f" {icon} [{it['status']:<11}] (w={it['weight']}) {it['item']}")
print()
ap = result["action_plan"]
if ap:
print(f" 📋 ACTION PLAN (top {len(ap)} items)\n")
for i, a in enumerate(ap, 1):
print(f" {i:>2}. {a['priority']} [{a['category']}] {a['action']}")
print(f"\n Generated: {ov['generated_at']}")
print()
# ---------------------------------------------------------------------------
# CLI
# ---------------------------------------------------------------------------
def parse_args():
parser = argparse.ArgumentParser(
description="Score product launch readiness across categories (stdlib only).",
formatter_class=argparse.RawDescriptionHelpFormatter,
epilog=__doc__,
)
parser.add_argument("--checklist", type=str, default=None,
help="Path to JSON checklist file")
parser.add_argument("--json", action="store_true",
help="Output results as JSON")
parser.add_argument("--export-template", action="store_true",
help="Print the default checklist template as JSON and exit")
return parser.parse_args()
def main():
args = parse_args()
if args.export_template:
print(json.dumps(DEFAULT_CHECKLIST, indent=2))
return
if args.checklist:
with open(args.checklist) as f:
checklist = json.load(f)
else:
print("🔬 DEMO MODE — using embedded sample checklist\n")
checklist = DEFAULT_CHECKLIST
result = score_readiness(checklist)
if args.json:
print(json.dumps(result, indent=2))
else:
pretty_print(result)
if __name__ == "__main__":
main()
Related skills
Seo AuditRun structured SEO audits on their SaaS site or content hub and receive a prioritized action plan.173k42.2kCopywritingGenerate, rewrite, or strengthen persuasive website and landing-page copy that converts visitors into users.164k42.2k
Viral Short FormQuickly generate high-retention hooks, scripts, and outlines for TikTok, Reels, YouTube Shorts, and carousels.132k67Viral HooksWrite and critique viral hooks for short-form video opening sequences.123k67Viral Captions And CtasOptimize social media captions and CTAs for viral short-form video reach and saves.123k67Viral Youtube ShortsWrite and diagnose YouTube Shorts for Shorts Feed and long-form funnel.123k67How it compares
Use launch-strategy for channel planning and timelines; pair with email-sequence for announcement copy execution.
FAQ
What is the ORB framework in launch-strategy?
launch-strategy ORB divides channels into Owned (email, blog, in-app), Rented (social algorithms), and Borrowed (partners, newsletters, Product Hunt). Complete plans must cover all three types.
How does launch-strategy score readiness?
launch-strategy includes launch_readiness_scorer.py, which reads checklist JSON by product, marketing, and technical categories and outputs a 0–100 readiness score highlighting the weakest categories before launch day.
Is Launch Strategy safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.