launch-plan
Skill0 starsChanged 51 days agoMITView on GitHub
Plan taking something to an audience by positioning against the alternative the buyer actually has, including doing nothing, reaching the audience you can actually reach, and choosing the channel where their attention already sits. Use when planning a launch, release announcement, product reveal, feature rollout, or go-to-market, when deciding where and when to announce, when the total addressable market is being confused with the reachable audience, or when a first launch landed quietly and the question is what to do next. Triggers on plan a launch, how do I launch this, go to market, launch strategy, where should I announce, launch day plan, nobody noticed my launch, my launch flopped, product hunt launch, how to get attention, positioning, who is my audience, launch checklist, relaunch after a flop.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- 2104178150-ai/megaphonetheir own version, first seen Oct 20, 2026
- kitloomlk-stack/marketing-seo-kittheir own version, first seen Oct 15, 2026
- agentmart/pm-ostheir own version, first seen Oct 15, 2026
- duncan-buildroom/profit-room-skillstheir own version, first seen Oct 13, 2026
- duncan-buildroom/freeskillstheir own version, first seen Oct 13, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
Used with
Projects with it also use offer-builder.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
duncan-buildroomSkilloffer-builder
Build a Hormozi-style "Grand Slam Offer" so good people feel stupid saying no — engineered around the Value Equation (bigger dream outcome, higher belief it'll work, less time, less effort). Use this when the user says "build my offer", "make my offer irresistible", "help me package what I sell", "I don't know how to price/pitch this", "grand slam offer", "I built a product but nobody's buying", or when they have a thing to sell but no compelling way to present it. Push to run this before they try to sell anything.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- indranilbanerjee/digital-marketing-pro★ 934same name
- duncan-buildroom/freeskills★ 65same name
- duncan-buildroom/profit-room-skills★ 18same name
- calven-ai/marketing-as-code★ 10same name
- styfinity/claude-marketing-department★ 6same name
- 2104178150-ai/megaphone★ 5same name
- 45ck/marketing-product-skills★ 3same name
- impactbrussels/FounderOS★ 2same name
- agentmart/pm-os★ 1same name
- agentdynarq/founder-skills★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- accessibility-auditSkill
- agent-orchestrateSkill
- arch-decideSkill
- auth-implementSkill
- backend-buildSkill
- build-pilotSkill
- business-modelSkill
- career-strategySkill
- codebase-onboardSkill
- code-craftSkill
- code-reviewSkill
- compliance-mapSkill
- content-craftSkill
- cost-controlSkill
- data-analysisSkill
- data-layerSkill
- debug-methodSkill
- deep-researchSkill
- dependency-guardSkill
- design-systemSkill
- devex-toolingSkill
- doc-forgeSkill
- email-deliverSkill
- finance-booksSkill
- frontend-buildSkill
- git-disciplineSkill
- growth-experimentSkill
- human-proseSkill
- i18n-localizeSkill
- incident-responseSkill
- index-fastSkill
- infra-deploySkill
- job-huntSkill
- landing-convertSkill
- llm-app-buildSkill
- llm-visibilitySkill
- memory-keeperSkill
- migration-planSkill
- ml-buildSkill
- mobile-buildSkill
- numbers-checkSkill
- observability-setupSkill
- payments-integrateSkill
- performance-tuningSkill
- pricing-modelSkill
- prompt-forgeSkill
- queue-designSkill
- reality-checkSkill
- refactor-safelySkill
- release-manageSkill
- security-hardeningSkill
- seo-optimizeSkill
- ship-auditSkill
- skill-forgeSkill
- test-strategySkill
- ui-designSkill
- user-researchSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read the situation before writing the plan.
- Distinctive: line 74
When the user says "stop", "just execute", or "skip the launch checks", that is the off switch.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch plan
Asked to plan a launch, a model produces a checklist that assumes a crowd is waiting: post everywhere at once, count the total market as the audience, position against a named competitor, and treat launch day as the finish line. Then the launch lands to silence, because the crowd was never there and the plan had no answer for the quiet. This skill positions against doing nothing, sizes the audience you can actually reach, and plans for the likely quiet outcome.
Fit to the project
Read the situation before writing the plan.
- Find out who already pays attention to this maker or product: an email list and its real open rate, existing users, a following on one platform, a community they are part of. This reachable audience is the launch, and it is almost always far smaller than the total market. If it is close to zero, the honest first step is building it, not announcing.
- Detect what the buyer does today instead. Read support tickets, forum threads, and sales notes for the workaround people currently use, which is often a spreadsheet, a manual process, or nothing. That workaround is the real competitor.
- Find where the target audience already spends attention: which forum, which subreddit, which newsletter, which conference. Launching where the maker is comfortable rather than where the audience already gathers is the most common wasted effort.
Non-negotiables
- Position against the alternative the buyer actually has, and include doing nothing. Most launches lose to inertia, not to a competitor, and a plan that only compares against a named rival has no answer for the buyer who will simply keep coping. Ignoring the do-nothing option is the failure that sinks the most launches.
- Plan for the reachable audience, not the total market. A market of ten million means nothing if you can reach 300 people this month. Sizing the plan to the big number produces targets that guarantee the launch looks like a failure.
- Choose channels by where the audience's attention already sits, not by what is easy for the maker. A perfect post in a channel the audience does not read reaches no one.
- Assume the launch lands quietly and plan the follow-through, because a single quiet launch is the normal outcome, not the exception. A plan that only describes the best case has nothing to do on the far more likely ordinary day.
- Never buy or fabricate attention: no purchased reviews, no fake upvotes, no sockpuppet comments, no invented testimonials. It is against the terms of every serious platform, it is often unlawful, and a public unmasking costs more than the launch could ever earn. Refuse to plan it even when asked.
Procedure
Step 1, position against the real alternative
Write down what the buyer does today to solve this problem, in one sentence, including the option of doing nothing. State why your thing is worth the switching cost, because a buyer with a working spreadsheet needs a reason large enough to overcome the effort of change. If the only honest answer is a small improvement over doing nothing, the launch messaging has to be about the cost of the status quo, not about features. The positioning method sits in references/positioning.md.
Step 2, size the reachable audience
Count the people you can actually put this in front of in the launch window: list subscribers times a realistic open rate, community members who will see a post, followers who see any given message. This number, not the market size, sets the launch expectations. Write down the expected result at this size so success and failure are defined before launch day, not rationalized after. Sizing detail is in references/audience.md.
Step 3, pick the channels where attention already sits
For the target audience, list the two or three places they already gather and pay attention. Rank by reachability and fit, not by size. Pick the smallest number of channels you can execute well, because a strong presence in one right channel beats a thin presence in five. Note the norms of each channel, since a post that works on one reads as spam on another. Channel selection guidance is in references/audience.md.
Step 4, sequence the launch and its prerequisites
List what has to be true before launch day: the page live, the signup working, the first users ready to vouch, the payment path tested, the support inbox watched. Order the launch as a sequence, not a single day: warm the closest audience first, gather early proof, then widen. A launch that fires everything at once has no way to fix a broken step before the whole audience sees it. Sequencing detail is in references/positioning.md.
Step 5, run launch day on a written plan
Write the launch-day plan: what posts where, in what order, who responds to comments and questions, and how fast. Presence in the first hours matters more than the announcement itself, because a launch is a conversation and an unanswered comment is a dropped one. Have the answers to the obvious hard questions written before they are asked.
Step 6, plan for the quiet outcome
Write down, before launch, what you will do if the launch lands quietly, which is the likely case. The plan is not to relaunch louder. It is to learn: talk to the few who did engage, find what resonated, fix the positioning, and reach the audience again through a different channel or a narrower message. A launch is a start of distribution, not a one-time event, and the makers who win treat a quiet day as data rather than a verdict. The recovery method is in references/audience.md.
Self-audit
- Is the positioning written against what the buyer does today, with doing nothing named explicitly?
- Is the reachable audience counted as a real number, separate from the total market?
- Is the expected launch result written down before launch day?
- Are the chosen channels the ones where the audience already pays attention?
- Is there a prerequisite list, and is every item verified before the launch fires?
- Is there a written plan for who answers comments and how fast on launch day?
- Is there a specific follow-through plan for the case where the launch lands quietly?
- Is the plan free of any purchased, faked, or fabricated attention?
Honest limits
This skill plans the launch. It does not write the announcement copy or the substance of the posts, which is content-craft, or the page the traffic lands on, which is landing-convert. Run those for the assets the plan calls for.
It does not choose the pricing or the business model behind the launch, which is business-model, and it does not verify any market-size figure you bring to it, which is numbers-check and reality-check. The audience-sizing and timing guidance here is a rule of thumb for setting expectations, not a forecast, and it does not replace talking to real buyers.
When the user says "stop", "just execute", or "skip the launch checks", that is the off switch. Deliver the plan as asked and stop applying the checks for the rest of the session unless asked again. The refusal to plan faked attention in non-negotiable 5 stays even then.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

