Communitygithub.com

amplitude/builder-skills

使用 Playing to Win 級聯框架制定策略 — 包括勝利抱負、在哪競爭、如何取勝、核心能力與管理系統。當你需要就市場、定位與競爭優勢做出策略選擇時使用。

builder-skills 是什麼？

這項技能以 Playing to Win（致勝打法）框架為基礎，幫助使用者為事業、產品或專案制定真正的策略，而非單純的待辦事項清單。它源自 A.G. Lafley 與 Roger Martin 的經典方法論，強制要求使用者思考五大策略選擇：勝利抱負（Winning Aspiration）、在哪競爭（Where to Play）、如何取勝（How to Win）、核心能力（Capabilities）與管理系統（Management Systems）。每個選擇依序定義，並透過級聯一致性檢查確保彼此強化。技能還要求明確識別核心策略取捨（Key Strategic Tension），並逆向推導出「必須為真」的條件（Must-Be-True Conditions），作為驗證假設與管理風險的基礎。支援 Claude Code、Cursor、Codex 等平台，且可根據新產品、既有產品或平台型企業等不同情境調整分析重點。最終產出一個結構化策略文件，內含五層級聯、一致性檢查與具體後續行動。

相容平台~Claude Code~Codex CLI~Cursor
Part ofDesign & UI
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/playing-to-win
查看原文→瀏覽所有技能

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

OpenAIChatGPTClaudeClaudeGeminiGeminiGrokGrokPerplexityPerplexityDeepSeekDeepSeek

說明文件

Playing to Win（致勝打法）

策略是一套整合的選擇，讓你能夠取勝。讓這些選擇變得明確。

你的事業、產品或專案需要的是真正的策略，而不是披著策略外衣的待辦事項清單。這項技能運用 A.G. Lafley 與 Roger Martin 的 Playing to Win 框架，強制你思考五大關鍵策略選擇，並檢查它們是否相互強化。

關於每個選擇的詳細定義與診斷問題，請參閱 framework.md。

工作流程

  1. 釐清主體：確定需要策略的對象 — 公司、產品線、功能領域或新市場進入。若不明確，請詢問使用者。同時確定時間範圍（6 個月？3 年？）。

  2. 走完整個級聯 — 依序處理所有五個選擇。每個選擇會限制下一個選擇：

    選擇 1：我們的勝利抱負是什麼？ 以具體、可衡量的方式定義「贏」的模樣。不是「做到最好」——而是為哪些客戶取得何種具體成果？勝利抱負設定目標，並為之後的所有選擇定調。

    選擇 2：在哪競爭？ 選擇競爭領域。這是最重要的策略選擇——你決定不競爭的地方與決定競爭的地方同樣重要。考量維度：客戶群、地理區域、產品類別、通路、價值鏈階段。

    選擇 3：如何取勝？ 在所選的競爭領域內定義競爭優勢。只有兩種通用策略：成本領導或差異化。選擇哪一種，具體如何做到？什麼獨特價值主張讓你成為客戶的顯而易見選擇？

    選擇 4：必須具備哪些核心能力？ 找出 3-5 項在所選領域中取勝所需的關鍵能力。這些能力應互相強化——每一項能力都能提升其他能力的價值。區分你目前已具備的能力與需要培養的能力。

    選擇 5：需要哪些管理系統？ 定義建立並維持能力所需的系統、結構與流程。這是策略轉化為營運的環節——包括衡量系統、組織結構、人才、流程與文化。

  3. 測試級聯的一致性：五個選擇必須互相強化。檢查：

    • 在哪競爭的選擇是否與勝利抱負相符？
    • 如何取勝的選擇是否在所選領域中創造真正的優勢？
    • 核心能力是否確實能支撐如何取勝？
    • 管理系統是否建立並維持核心能力？
    • 競爭對手看完這套策略會不會立刻知道如何與你競爭？（如果會，表示你的如何取勝不夠獨特。）

  4. 識別關鍵策略取捨：每個策略都涉及核心取捨或權衡。明確指出——你放棄了什麼？你在下什麼賭注？這套策略要成功，什麼必須成立？

  5. 逆向推導「必須為真」的條件：針對每個選擇，列出 2-3 個該選擇成立所必須滿足的條件。這些條件將成為你的策略風險與需要驗證的假設。

輸出範本

# Playing to Win：[主體]

## 策略背景
[用 2-3 句話描述當前狀況、競爭格局，以及為何現在需要策略清晰度]

## 策略級聯

### 1. 勝利抱負
[勝利的模樣是什麼？為誰？何時達成？要具體且可衡量。]

### 2. 在哪競爭
**所選領域：**
- 客戶群：[具體是誰]
- 地理區域：[哪裡]
- 產品類別：[什麼]
- 通路：[如何觸及客戶]
- 價值鏈位置：[哪些環節]

**明確不競爭：**
- [你選擇不做的部分——這與選擇做什麼同等重要]

### 3. 如何取勝
**策略定位：** [成本領導 / 差異化 — 二選一]
**獨特價值主張：** [1-2 句話 — 客戶為何在替代方案中選擇你]
**關鍵差異化因素：**
- [差異化因素 1]
- [差異化因素 2]
- [差異化因素 3]

### 4. 核心能力
| 能力 | 目前已具備？ | 需要填補的缺口 | 優先級 |
|------|-------------|---------------|--------|
| [能力 1] | 是/部分/否 | [缺少什麼] | 關鍵/重要 |
| [能力 2] | ... | ... | ... |

### 5. 管理系統
| 系統 | 目的 | 狀態 |
|------|------|------|
| [系統 1] | [它支援什麼] | 已存在/需改善/缺失 |
| [系統 2] | ... | ... |

## 級聯一致性檢查
[每個層級是否互相強化？標出任何不一致之處。]

## 關鍵策略取捨
[核心權衡是什麼？你在下什麼賭注？]

## 必須為真的條件
| 選擇 | 條件 | 信心程度 | 如何驗證 |
|------|------|---------|----------|
| 在哪競爭 | [條件] | 高/中/低 | [測試或證據] |
| 如何取勝 | [條件] | ... | ... |
| ... | ... | ... | ... |

## 建議後續行動
1. [驗證風險最高的必須為真條件]
2. [填補最關鍵的能力缺口]
3. [建立或改善最重要的管理系統]

調整分析方法

針對新產品或新市場進入：將大部分時間花在「在哪競爭」與「如何取勝」。誘惑是想在所有地方競爭——請抵制它。狹窄的選擇才能致勝。

針對動能下滑的既有產品：從勝利抱負開始，檢查目前的「在哪競爭」是否仍然合理。市場在變——你的選擇也應該隨之調整。

針對平台或多產品公司：為每個產品/區塊獨立執行級聯，然後檢查整個產品組合的策略一致性。跨級聯共享的能力是你的槓桿點。

提示

  • 最難的部分是選擇不競爭的地方。如果你的「在哪競爭」包含所有人，那你就沒有策略。
  • 「如何取勝」不是功能列表。它是客戶選擇你的原因，必須用執行長能解釋的方式來陳述。
  • 如果你無法識別關鍵策略取捨，表示策略沒有做出夠困難的選擇。
  • 搭配 7-powers 使用，驗證你的「如何取勝」能否成為持久的競爭優勢。
  • 使用 amazon-working-backwards 測試你的勝利抱負是否能轉化為引人入勝的客戶敘事。
  • 對「必須為真」的條件執行 pre-mortem（事前驗屍），壓力測試風險最高的假設。

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

amplitude/builder-skills

Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.

amplitude/builder-skills

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

amplitude/builder-skills

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude/builder-skills

Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.

amplitude/builder-skills

Analyze MCP server usage instrumented with Amplitude's MCP Analytics SDK: break usage and errors down by tool, read the rationales within each tool to see what callers are trying to do, and produce a prioritized write-up of actionable fixes. Use this skill whenever the user asks to understand how their MCP server is being used, what agents/users are trying to do with it, why tool calls are failing, what to fix or improve in their MCP server, or asks for an "MCP usage report", "tool error analysis", "intent analysis", "rationale clustering", or "MCP insights". Also trigger when the user mentions [MCP]-prefixed events, tool rationale, tool call errors, or just finished instrumenting their MCP server and wants to see what the data says. Requires the Amplitude MCP connector.

amplitude/builder-skills

Read lost deals and churned accounts from your CRM, extract reasons clustered by theme (missing features, pricing, competitors, UX), and write a prioritized weekly analysis with product improvement recommendations. Use before roadmap planning or to build the case for prioritizing retention work.

amplitude/builder-skills

Creates Amplitude charts from natural language descriptions, handling event selection, filters, groupings, and visualization choices. Use when you know what you want to measure but prefer not to build the chart manually.

amplitude/builder-skills

Guide an Amplitude user through building a custom agent by suggesting use cases grounded in their role and data, shaping the idea into a well-formed spec, and generating a ready-to-run Global Agent deeplink that creates it. Use to create, build, or set up a custom agent, automate a recurring analysis, or put a repeated report on a schedule.

amplitude/builder-skills

Builds comprehensive Amplitude dashboards from requirements or goals, organizing charts into logical sections with appropriate layouts. Use when creating a complete dashboard from scratch or assembling existing charts into a cohesive view.

amplitude/builder-skills

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude/builder-skills

Pull Intercom tickets and Slack support messages from the past 7 days, classify each signal, enrich with CRM data (ARR, plan, renewal), score by customer value and churn risk, and output a tiered priority report saved to Drive. Use when you need a fast, data-driven view of what support signals matter most.

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

amplitude/builder-skills

Use this skill whenever a user wants to understand which external sources are being cited by AI models on topics relevant to their brand, and wants to create content that will outrank those sources — whether they say "what sources are AI models citing", "why is [third-party site] being cited instead of us", "we want to be the definitive source on X", "build something that gets cited more than G2 or TechRadar", "create an authoritative asset", or any variation where the goal is producing a new reference asset (definition page, benchmark, methodology, glossary, comparison hub) designed to beat existing top-cited sources. This skill analyzes AI Visibility source data, reverse-engineers what makes top-cited pages authoritative, and produces a superior source asset — then pushes it to CMS as a draft. Trigger on any mention of "sources", "third-party citations", "authoritative content", "definitional pages", or "outrank".

amplitude/builder-skills

Instrument a Node/TypeScript MCP server with Amplitude's @amplitude/mcp-analytics SDK so tool calls, sessions, and rationale are tracked as Amplitude events. Use this skill whenever the user wants to add Amplitude analytics to their MCP server, mentions "MCP Analytics", "@amplitude/mcp-analytics", "instrument my MCP server", "track MCP tool calls", "add rationale to my MCP tools", or wants agent traffic (Claude, Cursor, ChatGPT) attributed back to Amplitude. Also use for adding UTM tagging to MCP-returned links, or for troubleshooting identity/user_id mismatches between MCP events and web/mobile Amplitude data.

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

amplitude/builder-skills

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

相關技能

steipete/sag

ElevenLabs text-to-speech with mac-style say UX.

community

steipete/oracle

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

community

steipete/peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

community

mattpocock/design-an-interface

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

community

mattpocock/prototype

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

community

mattpocock/grill-me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

community