메뉴
Plan product launches with the right tier and coordinated checklists. Use when asked to plan a launch, coordinate a release, prepare for go-to-market, or figure out how to announce a new feature or product. Covers silent, soft, and big-bang launch tiers.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Evaluate product bets and shape pitches using Shape Up's appetite model and Bezos's Type 1/Type 2 decision framework. Use when asked to assess a product bet, evaluate initiative risk, decide resource allocation, or shape a pitch for a new feature or project.
Analyze competitive landscape with feature matrices, positioning maps, and strategic gap analysis. Use when asked to analyze competitors, map the competitive landscape, find differentiation, or evaluate alternatives to a product.
Design hypothesis-driven experiments and A/B tests with proper methodology. Use when asked to design an A/B test, validate a hypothesis, plan an experiment, or set up a test for a product change. Covers hypothesis writing, sample size, and common mistakes.
Prioritize features and backlog items using RICE scoring and Linear's enablers vs blockers lens. Use when asked to rank features, prioritize a backlog, decide what to build next, or evaluate feature requests against each other.
Analyze customer motivations using Jobs-to-be-Done and Forces of Progress. Use when asked about jobs-to-be-done, why customers switch products, what job a product is hired for, or when analyzing the forces that drive or resist product adoption.
Define product metrics with a North Star, input/output tree, and counter-metrics. Use when asked to define metrics, set up measurement, choose KPIs, pick a north star metric, or build a metrics framework. Prevents vanity metrics and gaming.
| name | launch-plan |
| description | Plan product launches with the right tier and coordinated checklists. Use when asked to plan a launch, coordinate a release, prepare for go-to-market, or figure out how to announce a new feature or product. Covers silent, soft, and big-bang launch tiers. |
Launch based on the size of the bet, not the size of your ambition. Most features deserve a silent or soft launch. Save the big-bang for genuinely new products or major pivots. Linear's principle: launch early, launch often, launch multiple times.
Ship it, turn it on, see what happens. No announcement.
Use for: Bug fixes, minor improvements, internal tools, infrastructure changes, experiments.
Checklist:
Ship it, tell existing users, collect feedback before going wide.
Use for: New features for existing users, significant UX changes, pricing changes, beta programs.
Checklist:
Example: Launching real-time collaboration — Changelog: "Edit together, see cursors live." Support FAQ covers latency expectations and max concurrent editors. Roll out to 20% of teams for 3 days via feature flag, then 100%. Rollback: disable WebSocket sync, fall back to polling. Feedback widget live for 2 weeks. Success metric: % of teams with 2+ simultaneous editors.
Coordinated, public, designed for maximum reach. Expensive in time and attention.
Use for: New product launch, major pivot, rebrand, entering a new market. Maximum 2-3 per year.
Checklist:
Product
Content
Distribution
Support
Measurement
Regardless of tier:
Built on Linear's "launch multiple times" philosophy. Skills from productskills.
