인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
생산성 및 협업 · SKILL.md

launch-checklist

launch-checklist

Create a go-to-market launch checklist tailored to the product type, stage, and audience. Use when the user is preparing to launch a feature, product, or update and wants to make sure nothing is missed.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: launch-checklist description: Create a go-to-market launch checklist tailored to the product type, stage, and audience. Use when the user is preparing to launch a feature, product, or update and wants to make sure nothing is missed.

Ask the user:

  1. "What are you launching — a new feature, a product update, a new product, or something else?"
  2. "Who is the audience — existing users, new customers, enterprise, consumers?"
  3. "What's your target launch date and team size?"

Then produce a checklist organized by phase:

Launch Checklist: [Product/Feature Name]

Launch date: [X] Launch type: [soft launch / beta / public launch / coordinated release]


2 weeks before

  • PRD finalized and reviewed by engineering lead
  • Acceptance criteria written and QA plan in place
  • Legal/compliance review completed (if applicable)
  • Pricing and packaging confirmed
  • Support documentation drafted
  • Rollback plan documented

1 week before

  • Feature flag / release toggle configured
  • Analytics events implemented and verified in staging
  • Email announcement drafted and approved
  • In-app messaging or onboarding flow reviewed
  • Customer success and support teams briefed
  • Press / influencer outreach sent (if applicable)

Launch day

  • Staged rollout configured (10% → 50% → 100%)
  • Error monitoring and alerts confirmed active
  • All-hands Slack channel open for real-time issues
  • First metrics checkpoint scheduled (T+2h)
  • Announcement posted (email / social / in-app)

Post-launch (first week)

  • Day 1 and Day 7 metrics reviewed against target
  • User feedback collected (in-app, support tickets, interviews)
  • Known issues triaged and prioritized
  • Internal retro scheduled

Mark any item that is blocked or unassigned — those are your launch risks.

저장한 Skills