본문으로 건너뛰기
cccskills
무료GitHub에 공개

launch-strategy

Plan product launches, feature announcements, and release strategies — phased launches, channel strategy, Product Hunt, and momentum.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane스타 3(GitHub 3 + cccskills 0)

실행 점수 미검증

설치 방법 보기

포함된 파일(3)

  • SKILL.md4.0 KB
  • references/launch-frameworks-and-checklists.md10.6 KB
  • scripts/launch_readiness_scorer.py12.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

→ See references/launch-frameworks-and-checklists.md for details

Task-Specific Questions

  1. What are you launching? (New product, major feature, minor update)
  2. What's your current audience size and engagement?
  3. What owned channels do you have? (Email list size, blog traffic, community)
  4. What's your timeline for launch?
  5. Have you launched before? What worked/didn't work?
  6. Are you considering Product Hunt? What's your preparation status?

Proactive Triggers

Proactively offer launch planning when:

  1. Feature ship date mentioned — When an engineering delivery date is discussed, immediately ask about the launch plan; shipping without a marketing plan is a missed opportunity.
  2. Waitlist or early access mentioned — Offer to design the full phased launch funnel from alpha through full GA, not just the landing page.
  3. Product Hunt consideration — Any mention of Product Hunt should trigger the full PH strategy section including pre-launch relationship building timeline.
  4. Post-launch silence — If a user launched recently but hasn't followed up with momentum content, proactively suggest the post-launch marketing actions (comparison pages, roundup email, interactive demo).
  5. Pricing change planned — Pricing updates are a launch opportunity; offer to build an announcement campaign treating it as a product update.

Output Artifacts

ArtifactFormatDescription
Launch PlanMarkdown docPhase-by-phase plan with owners, dates, channels, and success metrics
ORB Channel MapTableOwned/Rented/Borrowed channel strategy with tactics per channel
Launch Day ChecklistChecklistComplete day-of execution checklist with time-boxed actions
Product Hunt BriefMarkdown docListing copy, asset specs, pre-launch timeline, engagement playbook
Post-Launch Momentum PlanBulleted list30-day post-launch actions to sustain and compound the launch

Communication

Launch plans should be concrete, time-bound, and channel-specific — no vague "post on social media" recommendations. Every output should specify who does what and when. Reference marketing-context to ensure the launch narrative matches ICP language and positioning before drafting any copy. Quality bar: a launch plan is only complete when it covers all three ORB channel types and includes both launch-day and post-launch actions.


Related Skills

  • email-sequence — USE for building the launch announcement and post-launch onboarding email sequences; NOT as a substitute for the full channel strategy.
  • social-content — USE for drafting the specific social posts and threads for launch day; NOT for channel selection strategy.
  • paid-ads — USE when the launch plan includes a paid amplification component; NOT for organic launch-only strategies.
  • content-strategy — USE when the launch requires a sustained content program (blog posts, case studies) in the weeks after; NOT for single-day launch execution.
  • pricing-strategy — USE when the launch involves a pricing change or new tier introduction; NOT for feature-only launches.
  • marketing-context — USE as foundation to align launch messaging with ICP and brand voice; always load first.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SebastianLuser/claude-code-arcane32026년 10월 27일 업데이트

SebastianLuser의 스킬 모두 보기

이 스킬의 문제 신고