AGENT SKILL

launch-strategist

Org role guidance for a launch strategist: sequence product launches from internal validation to full public release across owned, rented and borrowed channels. For the full imported launch playbook, use launch-strategy.

适用职业产品经理
License 许可
Apache-2.0
所属仓库
monoes/monomind
最近更新
2026-11-10
Stars
★ 23
Forks
2

01 前言 Front Matter

name
launch-strategist
tags
[ "product", "launch", "marketing" ]
tools
[]
source
https://github.com/monoes/monomind
license
Apache-2.0
description
Org role guidance for a launch strategist: sequence product launches from internal validation to full public release across owned, rented and borrowed channels. For the full imported launch playbook, use launch-strategy.

03 SKILL.md 正文

Launch Strategist — Best Practices

Focus

Plans and sequences product launches and feature announcements — from internal validation through full public release — to build momentum and convert attention into users.

Best practices

  • Use the ORB channel model: build Owned channels (email, blog, community) first since they compound; use Rented channels (social, marketplaces) to drive traffic to owned ones; use Borrowed channels (guest content, podcasts, influencers) to shortcut attention, then convert that attention into an owned relationship immediately.
  • Sequence launches in phases — internal (10-20 friendly users) → alpha (first external exposure + waitlist) → beta (broader access + teaser marketing) → early access (throttled or full expansion) → full launch (open self-serve, maximum visibility) — don't skip straight to public launch.
  • Coordinate multiple touchpoints on launch day: customer email, in-app notification, website banner, blog post, social posts, and relevant launch platforms (Product Hunt, Hacker News).
  • For Product Hunt: submit Tuesday-Thursday, brief your community in advance so upvotes aren't a surprise, write a founder-story first comment, and respond to every comment in the first 4 hours.
  • Write feature-announcement subject lines and taglines around the benefit/transformation, not the feature name.
  • Keep iterating after launch: collect qualitative feedback week 1, ship fixes by week 4, synthesize quantitative retention data by month 2, and run a second announcement wave with social proof by month 3.

Common pitfalls

  • Treating launch as a single event instead of a phased sequence — going straight to full public launch without internal/alpha/beta validation.
  • Over-investing in rented channels (social posts) without a plan to convert that traffic into an owned asset (email list, community).
  • Submitting to Product Hunt without a plan to be active and responsive all day.
  • No post-launch plan — momentum dies because there's no week 1/month 1/month 2 follow-through.
  • Announcing features with feature-name subject lines instead of benefit framing, so existing users skip the email.

Tools & techniques

  • Five-phase launch framework (internal → alpha → beta → early access → full launch) with a stated goal per phase.
  • ORB channel mapping exercise before planning any specific launch tactic.
  • Launch-day touchpoint checklist to ensure owned, rented, and borrowed channels all fire together.
  • Success-metric benchmarks to judge a launch: waitlist size (500-2000 pre-launch), launch-day signup multiplier (3-5x baseline), D7 retention (40%+) for the launch cohort.

04 同仓库更多 Skills

monoes
monoes/monomind

zk-steward

Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.

★ 23
monoes
monoes/monomind

writing-plans

Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.

内容创作者写作与文案
★ 23
monoes
monoes/monomind

write-spec

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

产品经理
★ 23
monoes
monoes/monomind

write-query

Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.

数据分析师
★ 23
monoes
monoes/monomind

workflow-automation

Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.

运维与部署Skill与智能体开发
★ 23
monoes
monoes/monomind

workflow-architect

Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.

Skill与智能体开发
★ 23