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

codexkit-go-to-market-planner

Build a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md4.5 KB
  • agents/openai.yaml168 B
  • examples/common-mistakes.md787 B
  • examples/good-output.md865 B
  • verification/checklist.md1.4 KB

SKILL.md(原文)

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

Go-to-Market Planner

Purpose

Create a structured GTM plan that aligns product, marketing, sales, and customer success for a successful launch — from market analysis to day-one execution.

When to use

  • launching a new product or service
  • entering a new geographic market or customer segment
  • repositioning an existing product
  • preparing a major feature launch that needs cross-functional coordination

When not to use

  • ongoing campaign management (use campaign-brief-writer)
  • brand identity or visual design work
  • daily marketing operations

Inputs

  • product or feature description and key differentiators
  • target audience (existing segment or new)
  • competitive landscape overview
  • launch timeline or constraints
  • available budget and resources
  • sales model (self-serve, sales-led, product-led, hybrid)
  • geographic scope

Procedure

  1. Market sizing — TAM/SAM/SOM analysis:
    • TAM: total market value if 100% penetration
    • SAM: segment the company can realistically serve
    • SOM: the achievable share in 12–18 months
  2. Competitive positioning:
    • map competitors on a 2×2 matrix (e.g., ease-of-use vs. feature completeness)
    • identify your unique positioning angle
    • write a positioning statement: "For [target], we are the [category] that [differentiator] unlike [alternative]"
  3. Messaging framework:
    • headline value proposition (one sentence)
    • 3 supporting pillars (feature → benefit → evidence)
    • objection handling for top 5 buyer concerns
  4. Channel strategy (prioritize 3–4 channels):
    • rank by expected ROI and lead quality
    • include content, paid, partnerships, community, product-led
  5. Pricing approach:
    • value-based or competitive pricing rationale
    • packaging tiers if applicable
    • free trial or freemium consideration
  6. Launch timeline with milestones:
    • T-30: pre-launch (beta, waitlist, press outreach)
    • T-0: launch day (announcement, activation campaigns)
    • T+30: post-launch (analysis, iteration, feedback loop)
  7. Success metrics and review cadence:
    • leading indicators (sign-ups, trials, pipeline)
    • lagging indicators (revenue, retention, NPS)
    • review: weekly for first 30 days, then monthly

Output

  • market sizing summary (TAM/SAM/SOM with sources)
  • competitive positioning map
  • messaging framework document
  • channel prioritization matrix
  • launch timeline with milestones and owners
  • success metrics dashboard definition

Definition of done

  • TAM/SAM/SOM are quantified with sources
  • positioning statement is specific, not generic
  • messaging pillars have evidence, not just claims
  • launch timeline has milestone owners and dates
  • success metrics include both leading and lagging indicators

Examples

  • "Create a GTM plan for our new AI writing tool targeting SMB content teams."
  • "Plan the launch of our Vietnam market expansion for the existing SaaS product."
  • "We're repositioning from enterprise to mid-market — build the messaging and channel plan."

Quality Criteria

  • All claims reference specific frameworks, standards, or quantifiable data
  • Content matches the stated audience's expertise level
  • Recommendations are actionable — each includes a concrete next step
  • No unsupported assertions or generic filler language

Verification (4C)

CheckQuestion
CorrectnessDo referenced frameworks and standards match their official definitions?
CompletenessAre all key concepts covered without significant gaps for the stated audience?
Context-fitWould this be useful for someone new to this domain, or is it too advanced/too basic?
ConsequenceIf a stakeholder acted on this immediately, what could they misinterpret?

Edge Cases

  • Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
  • Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
  • Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

  • v1.0.0 — Initial release

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

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

hoavdc/CodexKit252026年10月11日 更新

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

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

hoavdc/CodexKit252026年10月11日 更新

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

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

hoavdc/CodexKit252026年10月11日 更新

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

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

hoavdc/CodexKit252026年10月11日 更新

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

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

hoavdc/CodexKit252026年10月11日 更新

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

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

hoavdc/CodexKit252026年10月11日 更新

hoavdc のスキルをすべて見る

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