plugins/marketing/skills/launch-orchestrator/SKILL.md
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
npx skillsauth add petrogurcak/skills launch-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Routes launch-planning requests to the right specialist based on product type. This skill does NOT plan launches itself — it detects whether the product is generic (SaaS, app, physical, service) or info-product (course, membership, ebook, cohort, community) and delegates to the right sub-skill. Two launch playbooks share DNA (pre-launch list, beta, testimonials, offer mechanics) but diverge sharply in cadence, pricing, and sales mechanic — picking the wrong one wastes the launch window.
Philosophy:
marketing-orchestrator (top router for all marketing)
↓ detects "launch, spuštění, go-to-market, release"
launch-orchestrator (this skill — launch family router)
↓ detects product type
├── launch-strategy (GENERIC — SaaS, apps, physical, services, hardware)
└── info-product-launch (INFO — courses, memberships, ebooks, cohorts, communities)
Announce: "Using launch-orchestrator to route this launch request."
| User says... | Product type | Route to |
|---|---|---|
| SaaS launch, app release, uvedení SaaS, web product launch | Software product | launch-strategy |
| iOS app launch, Android app release, mobilní app spuštění | Mobile app | launch-strategy |
| hardware launch, physical product, e-commerce launch, produktová řada | Physical goods | launch-strategy |
| service launch, agency launch, consulting launch, spuštění služby | Service / agency | launch-strategy |
| course launch, kurz launch, spuštění kurzu, online kurz | Online course | info-product-launch |
| cohort launch, bootcamp launch, mastermind launch, skupinový program | Cohort program | info-product-launch |
| membership launch, community launch, launch členské sekce, placená komunita | Membership / community | info-product-launch |
| ebook launch, paid newsletter, digitální produkt launch, info-produkt | Digital content product | info-product-launch |
| PLF, Product Launch Formula, open cart / close cart, launch sequence Jeff Walker | PLF-style launch | info-product-launch |
| Generic launch / spuštění without product type | Unknown | ASK |
Co přesně spouštíš?
A) SaaS / web app / mobilní app → launch-strategy
B) Fyzický produkt / hardware / e-shop → launch-strategy
C) Service / agentura / consulting → launch-strategy
D) Online kurz / cohort program / bootcamp → info-product-launch
E) Membership / placená komunita / mastermind → info-product-launch
F) Ebook / paid newsletter / digitální obsah → info-product-launch
Use launch-strategy when the product is:
Signal: launch follows a continuous availability model (buy anytime after launch day), not a window mechanic.
Use info-product-launch when the product is:
Signal: launch follows a windowed sales mechanic (limited enrollment period) with email sequence and webinar/video pre-launch content.
Both launch playbooks share these foundations — both sub-skills assume these are in place:
marketing:testimonial-harvesting)marketing:offer-creation)marketing:uvp-optimization)The DIVERGENCE is in cadence and sales mechanic:
| Dimension | launch-strategy (generic) | info-product-launch (info) | |---|---|---| | Sales window | Continuous after launch | Open cart / close cart (3–7 days) | | Pre-launch | PR, beta signups, waitlist | PLC video sequence (3 videos) | | Price discovery | Tiered, ongoing optimization | Anchored at launch, rarely discounted later | | Sales mechanic | Trial → conversion / direct buy | Webinar → cart open → email sequence | | Urgency lever | Limited beta seats, launch price | Cart close date, bonuses expire |
User: "Chci spustit nový online kurz pro freelancery"
→ Orchestrator detects: online kurz + freelancers = info-product → Routes to: marketing:info-product-launch
User: "Plánuju go-to-market pro nový SaaS"
→ Orchestrator detects: SaaS = generic software product → Routes to: marketing:launch-strategy
User: "Chci pomoct s launchem"
→ Orchestrator: product type unknown → ASK using the menu (A–F) above → Then routes based on answer
User: "Spouštím placenou komunitu pro CFO"
→ Orchestrator detects: placená komunita = membership → Routes to: marketing:info-product-launch
Wrong specialist: "Spouštím kurz" → info-product-launch (NOT launch-strategy — courses need PLF sequence, not generic GTM)
Calling orchestrator when product type is clear: "Plánuju launch SaaS" → launch-strategy directly. No need to route.
Missing the info-product signal: "Spouštím produkt pro online vzdělávání" — if it's a course/cohort it's info-product-launch, but if it's a SaaS PLATFORM for educators it's launch-strategy. When in doubt, ASK.
Treating membership as service: Membership / paid community = info-product-launch (windowed enrollment), NOT launch-strategy (continuous service sales).
plugins/marketing/skills/launch-strategy/SKILL.md — generic launch playbook (SaaS, apps, physical, services)plugins/marketing/skills/info-product-launch/SKILL.md — info-product launch playbook (courses, memberships, PLF)plugins/marketing/skills/testimonial-harvesting/SKILL.md — shared by bothplugins/marketing/skills/offer-creation/SKILL.md — shared by bothplugins/marketing/skills/uvp-optimization/SKILL.md — positioning foundation for bothplugins/marketing/skills/marketing-orchestrator/SKILL.md — top-level marketing routerPhilosophy: Conductor doesn't play instruments. Orchestrator doesn't plan launches — it picks the right playbook.
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).
data-ai
Use when writing long-form video scripts that need retention engineering and narrative structure. Trigger phrases - "writing YouTube video script", "VSL (video sales letter)", "long-form video script", "course module video", "explainer video", "retention curve optimization", "video script for course", "scénář YouTube videa", "VSL skript", "long-form video", "scénář kurzového videa", "video script". Do NOT use for short-form TikTok/Reels under 60s — use copywriting:ig-content.