launch-plan
/launch-plan
Planuje i prowadzi start produktu od poznania go po dzień startu i czas po nim, także dla aplikacji i narzędzi AI.
- Autor
- devsolanki001 ↗
- Repozytorium
- product-launch ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Planuje i prowadzi start produktu od poznania go po dzień startu i czas po nim, także dla aplikacji i narzędzi AI.
Wyzwalacze z opisu
Oryginalny opis (EN)
Plan and run the launch of a product someone built - software, an app, an AI tool, an open-source project or a digital product - end to end, from understanding the product to launch day and after. Use when the person says launch, go live, release, ship it publicly, Product Hunt, Show HN, "how do I get users", "nobody knows about my product", go-to-market or GTM. Start here; it says which other launch skill to open for each stage.
Jak działa
- Rules that never bend
- The stages
- Readiness check (stage 2)
- Owned, rented, borrowed
- Pick the launch size
- Output for the person
- Credits
Podgląd SKILL.md
--- name: launch-plan description: Plan and run the launch of a product someone built - software, an app, an AI tool, an open-source project or a digital product - end to end, from understanding the product to launch day and after. Use when the person says launch, go live, release, ship it publicly, Product Hunt, Show HN, "how do I get users", "nobody knows about my product", go-to-market or GTM. Start here; it says which other launch skill to open for each stage. --- # Launch plan You help a person launch something they built. Most builders know how to make the product and not how to get it in front of the right people. Your job is to take them from "it works" to "the right people know about it, tried it, and can come back" - with a plan they can follow and the work done for them where it can be. ## Rules that never bend - **Nothing goes out in the person's name without their approval.** Every post, email, comment, listing and message is a draft until they approve that exact text and destination. In Vonit, ask for it as an action; the person approves it on the card. - **No spam.** No bulk cold email, no buying lists, no fake accounts, no asking for upvotes, no vote rings, no posting the same text in many communities. These get products banned and burn the founder's name. Keep outreach personal and small (see the outreach skill for the caps). - **Never invent facts.** No made-up users, numbers, quotes, logos, press or reviews. A missing fact is a clearly marked placeholder: `[number of users]`. - **Follow each platform's current rules.** They change; the platform notes here are a starting point - check the rules page before posting. ## The stages Work through them in order. Each is short when the person already has the answer. Open the skill named for each stage when you reach it. | # | Stage | Open | What comes out | |---|---|---|---| | 1 | Understand the product | `understand-product` | A one-page product brief and its product type | | 2 | Readiness check | (below) | Go, or the one thing to fix first | | 3 | Audience and positioning | `positioning` | Who it is for, the alternative it replaces, the one-line pitch | | 4 | Channels and timeline | `launch-channels` | Where to launch for this product type, and a dated plan | | 5 | Assets | `launch-assets` | Launch page check, screenshots, images, a short demo video, copy for each channel | | 6 | Outreach | `outreach` | A small, personal list and drafts - each approved before sending | | 7 | Launch day | `launch-day` | A run sheet hour by hour, replies, watching for problems | | 8 | After launch | `after-launch` | Follow-ups, what worked, the next launch moment | Ask only what you cannot find. Read the product first (its site, repository, app store page, README) and ask the person for what is missing - never a long questionnaire up front. ## Readiness check (stage 2) A launch amplifies what is there. Before spending attention on it: - **It does one clear thing** someone can try in minutes, without a call. - **Someone would choose it**, not just tolerate it - ideally a few real users already said so. (Adapted from Jason Cohen's "Simple, Lovable, Complete".) - **The first five minutes work**: sign-up or install, the first useful result, on a phone if the audience is on phones. - **There is somewhere to come back to**: an email list, a waitlist, a community, an account - launch traffic that leaves with nothing to return to is lost. Two ways launches die: polishing forever in private, and adding "one more feature" before every date. If the product passes the four points, launch; if not, name the single thing to fix and stop there. ## Owned, rented, borrowed Every launch uses three kinds of channel (adapted from marketingskills' "ORB framework", MIT): - **Owned** - the person's email list, site, blog, community. Slow to build, theirs forever. Every launch should grow these. - **Rented** - platforms they post on: X, LinkedIn, Reddit, Product Hunt, Hacker News, app stores, YouTube. Fast reach, their rules, short-lived. - **Borrowed** - other people's audiences: newsletters, podcasts, creators, communities, press. Credibility and reach, earned one relationship at a time. Use rented and borrowed attention to fill owned channels: every launch post points somewhere the visitor can stay. ## Pick the launch size Not every release needs a big launch: - **Big** (a new product, a major new version): the full stages, several channels, a launch day. - **Medium** (a notable feature, an integration): positioning check, one or two channels, an email to users, a changelog entry. - **Small** (fixes, small improvements): changelog and release notes only. Launch again and again: each meaningful release is a new chance to be noticed. ## Output for the person At the end of stage 4, give the person one page: 1. The product in one sentence, and who it is for. 2. The channels chosen, and why these and not others. 3. The dates: preparation, launch day, follow-up. 4. What they must do themselves (record a voice-over, be online on launch day, answer comments) and what will be prepared for their approval. Keep it short and plain. The person is a builder, not a marketer. ## Credits Ideas adapted from `coreyhaines31/marketingskills` (MIT) and `RefoundAI/lenny-skills` (MIT); see NOTICE.md.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · devsolanki001/product-launch | 90 | MIT |
| tansuasici/claude-marketing-kit | 100 | MIT |
| calven-ai/marketing-as-code | 100 | MIT |
| SimonFoote-greensparx/CopilotForge | 100 | CC-BY-4.0 |
| Sidsaladi9/persona-os | 100 | MIT |
| karix-ai/launch-skills | 90 | MIT |
| styfinity/claude-marketing-department | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 594249e5c741 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90product-launch
Planuje start produktu: strategię, kanały i listę kontrolną, a także ogłoszenie oraz działania po premierze. - 90product-launch
Planuje premierę produktu, uruchamia kanały launchu i tworzy listę kontrolną, odsyłając do osobnych skilli dla strategii GTM, zimnego startu i dnia na Product Hunt. - 100launch-strategy
Planuje premierę produktu, ogłoszenie funkcji i strategię wydania, w tym Product Hunt i plan go-to-market. - 100launch
Pomaga zaplanować premierę produktu, ogłoszenie funkcji i strategię wydania, w tym Product Hunt, beta, wczesny dostęp, listę oczekujących i plan go-to-market. - 100launch
Pomaga zaplanować premierę produktu, ogłoszenie funkcji i strategię wydania, w tym Product Hunt, beta, wczesny dostęp, listę oczekujących i plan go-to-market. - 100launch
Pomaga planować premierę produktu, ogłoszenie funkcji i strategię wydania: Product Hunt, beta, early access, lista oczekujących, lista kontrolna startu, GTM, changelog i notatki o wydaniu.