本文へ移動
cccskills
無料GitHub で公開

go-to-market-checklist

Generate a pre-launch readiness checklist for feature releases. Use this skill when: - A feature is nearing completion and you need a launch readiness checklist - You want to ensure all pre-launch items are covered (docs, training, support, rollback) - You are planning a phased rollout and need a structured go-to-market plan

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Go-to-Market Checklist

Generate a comprehensive pre-launch readiness checklist covering documentation, training, support, communication, metrics, and rollback planning.

Workflow

  1. Read feature spec from your spec directory
  2. Identify GTM dimensions from spec (users, channels, metrics, risks)
  3. Generate checklist with status tracking
  4. Output — Print to conversation or write file

Checklist

Documentation

  • Release notes written
  • User-facing help/FAQ updated
  • Internal knowledge base updated
  • API documentation updated (if applicable)
  • Migration guide written (if breaking changes)

Training

  • Customer success team briefed
  • Support team trained on new feature
  • Demo video/walkthrough created
  • Sales enablement materials ready (if B2B)

Support Readiness

  • Known issues documented
  • Escalation path defined
  • FAQ for common questions prepared
  • Support ticket categories created

Communication

  • Internal announcement drafted
  • Customer communication drafted (if applicable)
  • Stakeholder notification sent
  • Changelog updated

Metrics & Monitoring

  • Analytics events instrumented
  • Dashboard configured
  • Alerting rules set for error thresholds
  • Baseline metrics captured pre-launch

Rollback Plan

  • Feature flag configured
  • Rollback procedure documented
  • Data migration rollback tested (if applicable)
  • Go/No-go criteria defined

Compliance

  • PII audit completed
  • Regulatory review signed off
  • Privacy policy updated (if needed)

Output Format

# Go-to-Market Checklist — {Feature Name}

**Target Launch:** {date}
**Feature Spec:** {path}
**Status:** {Ready / Not Ready — N of M items complete}

{checklist sections above}

## Go/No-Go Summary

| Dimension | Status | Blocker? | Notes |
|-----------|--------|----------|-------|
| Documentation | Ready/Not Ready | Y/N | {detail} |
| Training | Ready/Not Ready | Y/N | |
| Support | Ready/Not Ready | Y/N | |
| Communication | Ready/Not Ready | Y/N | |
| Metrics | Ready/Not Ready | Y/N | |
| Rollback | Ready/Not Ready | Y/N | |
| Compliance | Ready/Not Ready | Y/N | |

**Decision:** GO / NO-GO
**Blockers to resolve:** {list if NO-GO}

Anti-Patterns

  • Don't skip the rollback plan — every launch needs a reversal path
  • Don't launch without baseline metrics — you can't measure impact without a before
  • Don't treat compliance as optional — data privacy is non-negotiable

Quality Checklist

  • All 7 dimensions covered
  • Go/No-Go summary table present
  • Blockers identified if status is NO-GO
  • Rollback plan is specific, not just "we'll revert"

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する