launch-plays

Use when orchestrating Tier 1/2/3 launches with repeatable workstreams and governance.

⭐31stars🔀7forks📁View on GitHub🕐Updated Dec 23, 2025⬇️4downloads

When & Why to Use This Skill

The Launch Playbooks skill is a comprehensive framework designed to orchestrate complex Tier 1, 2, and 3 product launches. It streamlines go-to-market (GTM) strategies by providing repeatable workstreams, governance models, and cross-functional alignment tools. By standardizing the launch process, it ensures operational efficiency, reduces scope creep, and provides clear accountability through RACI frameworks and performance measurement templates.

Use Cases

  • Product Launch Orchestration: Systematically managing high-impact product or feature releases using a tiered impact model to determine resource allocation.
  • Operational Governance: Establishing clear RACI roles and communication cadences across marketing, product, and sales teams to ensure accountability.
  • Process Standardization: Onboarding new Product Marketing Managers (PMMs) with pre-defined templates for project management tools like Notion, Jira, or Asana.
  • Performance Measurement: Defining KPI stacks and reporting templates to audit launch success and capture retrospective learnings for continuous improvement.
namelaunch-plays
descriptionUse when orchestrating Tier 1/2/3 launches with repeatable workstreams

Launch Playbooks Skill

When to Use

  • Planning upcoming product/feature launches.
  • Auditing current launch processes for efficiency gaps.
  • Onboarding new PMMs or cross-functional launch partners.

Framework

  1. Tiering Model – define Tier 1/2/3 criteria (impact, audience, readiness) with required workstreams.
  2. Workstreams – campaign, content, enablement, comms, success, ops, product readiness.
  3. RACI – assign responsible/approver for each deliverable.
  4. Cadence – stand-up schedule, checkpoints, risk reviews.
  5. Measurement – KPI stack + reporting templates.

Templates

  • Launch plan board (Notion/Jira/Asana) with tasks + owners.
  • Brief template capturing audience, goals, narrative, dependencies.
  • Retro template for capturing learnings.

Tips

  • Lock tier and scope early to prevent scope creep.
  • Maintain a risk log with mitigation owners.
  • Pair with workflow-testing and automation teams to confirm infra readiness.