launch-playbook

Generate launch checklists and sequencing plans from GTM specifications.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill launch-playbook-nomarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-playbook
Source: https://github.com/NOMARJ/sigil/tree/main/packs/business/skills/growth/launch-playbook
Command: npx skills add https://github.com/NOMARJ/sigil --skill launch-playbook-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Launches often break down because launch activities are uncoordinated, incomplete, or misaligned with the GTM motion; this Skill produces a clear, sequenced checklist to align teams and ensure the right distribution actions happen at the right time.

Core Features & Use Cases

  • Pre-launch, launch day, and post-launch coverage: Generates T-30, T-7, launch day, T+7, and T+30 task lists tailored to the product and GTM motion.
  • Motion-specific guidance: Prescribes actions and anti-patterns for developer-led, content-led, community-led, and relationship-led launches.
  • Operational output: Reads business context and GTM spec, then saves a markdown checklist and tracks progress using the .nomark paths for easy handoff and audit.
  • Use case: Prepare a developer-led CLI product launch with a public GitHub repo, HN/Reddit posts, and post-launch metric reviews.

Quick Start

Use the launch-playbook skill to generate a full pre-launch, launch day, and 30-day post-launch checklist and sequencing plan for Product X using the provided GTM spec and business context.

Frequently Asked Questions about launch-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a go-to-market checklist for a product launch?

To create a go-to-market checklist, you need to generate sequenced task lists covering pre-launch, launch day, and post-launch phases. This ensures launch activities are coordinated and aligned with your specific GTM motion, preventing breakdowns from incomplete or uncoordinated distribution actions.

What should be included in a pre-launch and post-launch sequencing plan?

A pre-launch and post-launch sequencing plan should include structured task lists for T-30, T-7, launch day, T+7, and T+30 phases. It prescribes specific distribution actions and anti-patterns tailored to your product and GTM motion to align teams throughout the timeline.

Does the launch playbook support developer-led and community-led GTM motions?

Yes, the launch playbook supports developer-led, content-led, community-led, and relationship-led GTM motions. It prescribes specific actions and anti-patterns for each motion type, ensuring your product launch checklist matches your specific distribution strategy.

How do I track product launch progress alongside the generated checklist?

You track product launch progress by saving the generated markdown checklist to a designated project path and updating a progress file using a specific story identifier. This operational output provides easy handoff, tracks tasks across launch phases, and enables auditability.

When do I need a structured launch playbook for my GTM strategy?

You need a structured launch playbook when your product launches suffer from uncoordinated activities, incomplete task coverage, or misalignment with your GTM motion. It provides a clear, sequenced checklist to align teams and ensure the right distribution actions happen at the right time.

Can I generate a launch checklist for a CLI product using a GTM spec?

Yes, you can generate a launch checklist for a CLI product by reading your provided business context and GTM specification. The output covers pre-launch, launch day, and post-launch phases, including tasks like public repo setup, community posts, and metric reviews.