launch-strategy
Skill1 starsChanged 6 months agoMITView on GitHub
Plan launches for MMA programs, research, labs, events — scoping, stakeholders, phased rollout, GTM. Use for "plan a launch", "rollout plan", "go-to-market".
67 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
- About-Intelligence/awesome-marketing-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use aso-audit, product-marketing-context and 9 more.
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.
ai-vitaSkillaso-audit
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
Also in 8 projects that use this
xfstudioSkillproduct-marketing-context
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.
Also in 24 projects that use this
ukunal91appSkillrevops
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.
Also in 27 projects that use this
VercelSkillsite-architecture
Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.
Also in 26 projects that use this
buildingwithaiSkillsales-enablement
Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.
Also in 24 projects that use this
ukunal91appSkillad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
Also in 28 projects that use this
- +5 more from ukunal91app
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- TheCraigHewitt/seomachine★ 7.5ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- mysticaltech/marketingskills★ 352same name
- shawnpang/startup-founder-skills★ 331same name
- b1rdmania/ghostclaw★ 91same name
- drvoss/everything-copilot-cli★ 48same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- MoizIbnYousaf/marketing-cli★ 33same name
- robertbstillwell/marketing-skills★ 26same name
57 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 repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asana-taskSkill
- briefing-prepSkill
- case-studySkill
- content-draftSkill
- content-strategySkill
- email-draftSkill
- event-promoSkill
- handoffSkill
- lab-summarySkill
- linkedin-scrapeSkill
- meeting-followupSkill
- member-commsSkill
- mma-brand-guidelinesSkill
- mma-org-contextSkill
- mma-pptx-builderSkill
- mma-writing-styleSkill
- office-editingSkill
- press-releaseSkill
- reddit-scrapeSkill
- research-briefSkill
- researchSkill
- search-and-scrapeSkill
- sharepoint-findSkill
- slack-summarySkill
- zapier-workflow-builderSkill
- commitSkill
- content-shippedSkill
- daily-briefingSkill
- endSkill
- marvinSkill
- mavenSkill
- skill-creatorSkill
- template-skillSkill
- updateSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 67 edited versions we read keep these.
3
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 106
Update Asana tasks (move across sections as work progresses)
- Distinctive: line 112
When creating a project brief, include these sections (per MMA's PMO template):
- Distinctive: line 153
Asana: Create project from MMA Project Template.
“Common” is measured: kept by at least 6 in 10 of the 67 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 Strategy — MMA Standards
MMA Launch Framework
MMA follows a four-phase launch process for programs, research, labs, and initiatives. This skill guides you through each phase with MMA-specific templates, stakeholder mapping, and deliverables.
Phase 1: Scoping
Define the initiative before any work begins.
Key questions to answer:
- What is this? (program, research report, lab, event, tool, partnership)
- Who is the MMA owner? Who is the PM?
- What think tank or department does this sit under? (MATT, MOSTT, ALTT, DATT, Events, Marketing, Membership)
- What's the target launch date?
- Who are the external parties involved? (research partners, sponsors, vendors)
- What's the member audience? (all members, specific tier, regional, think tank participants)
- Are there revenue or partner opportunities?
- Does this involve any MMA boards? (Global, NA, Media & Data, CDO, EMEA, regional)
Deliverable: Completed Project Brief (see template below)
Phase 2: Kick Off
PM creates the formal project infrastructure.
Checklist:
- Complete Project Brief and upload to SharePoint (PMO folder or relevant think tank site)
- Create Asana project from MMA Project Template
- Sections: Project Set up, Prep, In Field, Launch, Calls
- Notes: Description, Key Project Members, Teams Folder, Primary Tracker, Website Landing page, Supporting Resource Pages
- Angela Gray arranges kickoff meeting with core internal group
- Identify all stakeholders and their roles:
| Role | Who | Responsibility |
| Project Owner | Senior leader sponsoring the initiative | Strategic direction, final approval |
| Project Manager | Assigned PM | Day-to-day coordination, Asana tracking |
| Content Lead | Marketing/Dan Whiting | Content creation, distribution |
| Research Lead | Vas Bakopoulos / Leah Penland (if research) | Data, methodology, findings |
| Events Lead | Erin Disney / Jade Bentham (if event) | Logistics, promotion |
| Membership | Stephen Wellman / Amanda Hyland (if member-facing) | Member comms, engagement |
| Sales | Kevin Granath (if revenue opportunity) | Sponsorship, recruitment |
| Design/Web | Jason Chase | Visual assets, web updates |
| External Partners | Varies | Deliverables per agreement |
Phase 3: Planning
Workstream-specific planning calls to align on execution.
Workstreams to activate (as applicable):
- Content & Communications
- Editorial calendar for launch sequence (use
content-strategyskill) - Email drafts for each audience segment
- Social media plan
- Blog/web content
- Press release (if external-facing)
- Editorial calendar for launch sequence (use
- Member Engagement
- Which members are involved or targeted?
- Board involvement and briefing needs
- Member communications timeline
- Knowledge Center placement
- Events & Webinars
- Launch event or webinar details
- Speaker/panelist coordination
- Registration and promotion plan
- Sales & Partnerships
- Sponsorship opportunities
- Partner deliverables and timelines
- Sales enablement materials
- Technical & Operations
- Website updates (landing pages, downloads, gating)
- Tool/platform setup (if applicable)
- Data collection and reporting setup
Phase 4: Execution
Track progress in Asana, surface blockers in weekly team calls.
Launch Sequence Template:
| Timing | Action | Owner | Channel |
| T-4 weeks | Internal stakeholder briefing | PM | Meeting |
| T-3 weeks | Board preview (if applicable) | Project Owner | Email/meeting |
| T-2 weeks | Teaser content deployed | Content Lead | Social, email, Slack |
| T-1 week | Press/media outreach (if applicable) | Marketing | PR |
| T-1 week | Final review and approvals | PM + Owner | Asana |
| Launch day | Email blast + social + blog + web | Content Lead | All channels |
| T+1 day | Slack announcement to members | PM | Slack #general |
| T+1 week | Webinar / deep dive event | Events Lead | Teams/Zoom |
| T+2 weeks | Follow-up content (case studies, Q&A) | Content Lead | Blog, email |
| T+4 weeks | Impact report / post-mortem | PM | Internal |
Weekly tracking:
- Update Asana tasks (move across sections as work progresses)
- Surface blockers in weekly team call
- Report progress in relevant Slack channel
Project Brief Template
When creating a project brief, include these sections (per MMA's PMO template):
# Project Brief: [Project Title]
## Overview
- **Parent Program:** [Think tank, department, or initiative this falls under]
- **Asana Project:** [Link to Asana project]
- **SharePoint Folder:** [Link to Teams/SharePoint folder]
- **Project Owner:** [Name, title]
- **Project Manager:** [Name]
- **External Parties:** [Partners, vendors, sponsors]
## Project Summary
[2-3 paragraph description of the initiative, its goals, and expected impact]
## Project Inputs
[What existing research, data, content, or assets feed into this project]
## Deliverables & Supporting Activities
[Sequenced list of deliverables with dates and owners]
| # | Deliverable | Target Date | Owner |
|---|-------------|-------------|-------|
| 1 | [First deliverable] | [Date] | [Name] |
| 2 | [Second deliverable] | [Date] | [Name] |
## Membership Engagement
- **Target member segments:** [Who benefits from this]
- **Engagement activities:** [Webinars, workshops, downloads, etc.]
- **Board involvement:** [Which boards need briefing or input]
## Revenue & Partner Opportunities
[Sponsorship, co-marketing, paid tiers, or partner deliverables]
## Promotional Activities
[How this will be promoted — channels, timeline, assets needed]Integration with MMA Tools
- Asana: Create project from MMA Project Template. Use sections: Project Set up → Prep → In Field → Launch → Calls
- SharePoint: Upload Project Brief to relevant site (PMO folder or think tank site)
- Slack: Post updates in relevant channels; use #general for org-wide launches
- Salesforce: Track member engagement and revenue attribution
- Pardot: Set up email sequences for launch communications
Launch Types by Scale
| Scale | Examples | Typical Timeline | Stakeholders |
| Major | New research report, new lab, POSSIBLE | 6-8 weeks | Cross-functional, boards, external |
| Medium | Lab results release, new tool, webinar series | 3-4 weeks | 2-3 teams, targeted members |
| Minor | Blog series, skill update, process change | 1-2 weeks | 1-2 teams, internal first |
Adjust the framework depth to match the launch scale. Not every launch needs all four phases fully built out — but every launch needs the scoping questions answered.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

