agentleFS
alectivismalectivism/maven-template/.claude/skills/launch-strategy/SKILL.md

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

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-vitaSkill

    aso-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

  • xfstudioSkill

    product-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

  • ukunal91appSkill

    revops

    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

  • VercelSkill

    site-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

  • buildingwithaiSkill

    sales-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

  • ukunal91appSkill

    ad-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

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
  1. Distinctive:

    Update Asana tasks (move across sections as work progresses)

    line 106
  2. Distinctive:

    When creating a project brief, include these sections (per MMA's PMO template):

    line 112
  3. Distinctive:

    Asana: Create project from MMA Project Template.

    line 153

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:
RoleWhoResponsibility
Project OwnerSenior leader sponsoring the initiativeStrategic direction, final approval
Project ManagerAssigned PMDay-to-day coordination, Asana tracking
Content LeadMarketing/Dan WhitingContent creation, distribution
Research LeadVas Bakopoulos / Leah Penland (if research)Data, methodology, findings
Events LeadErin Disney / Jade Bentham (if event)Logistics, promotion
MembershipStephen Wellman / Amanda Hyland (if member-facing)Member comms, engagement
SalesKevin Granath (if revenue opportunity)Sponsorship, recruitment
Design/WebJason ChaseVisual assets, web updates
External PartnersVariesDeliverables per agreement

Phase 3: Planning

Workstream-specific planning calls to align on execution.

Workstreams to activate (as applicable):

  1. Content & Communications
    • Editorial calendar for launch sequence (use content-strategy skill)
    • Email drafts for each audience segment
    • Social media plan
    • Blog/web content
    • Press release (if external-facing)
  2. Member Engagement
    • Which members are involved or targeted?
    • Board involvement and briefing needs
    • Member communications timeline
    • Knowledge Center placement
  3. Events & Webinars
    • Launch event or webinar details
    • Speaker/panelist coordination
    • Registration and promotion plan
  4. Sales & Partnerships
    • Sponsorship opportunities
    • Partner deliverables and timelines
    • Sales enablement materials
  5. 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:

TimingActionOwnerChannel
T-4 weeksInternal stakeholder briefingPMMeeting
T-3 weeksBoard preview (if applicable)Project OwnerEmail/meeting
T-2 weeksTeaser content deployedContent LeadSocial, email, Slack
T-1 weekPress/media outreach (if applicable)MarketingPR
T-1 weekFinal review and approvalsPM + OwnerAsana
Launch dayEmail blast + social + blog + webContent LeadAll channels
T+1 daySlack announcement to membersPMSlack #general
T+1 weekWebinar / deep dive eventEvents LeadTeams/Zoom
T+2 weeksFollow-up content (case studies, Q&A)Content LeadBlog, email
T+4 weeksImpact report / post-mortemPMInternal

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

ScaleExamplesTypical TimelineStakeholders
MajorNew research report, new lab, POSSIBLE6-8 weeksCross-functional, boards, external
MediumLab results release, new tool, webinar series3-4 weeks2-3 teams, targeted members
MinorBlog series, skill update, process change1-2 weeks1-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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.