Communitygithub.com

amplitude/builder-skills

运用“求胜之道”（Playing to Win）级联框架制定战略——包括制胜愿景、战场选择、制胜方式、核心能力和管理体系。当需要就市场、定位和竞争优势做出战略选择时使用。

builder-skills 是什么？

该技能基于A.G. Lafley和Roger Martin的“求胜之道”（Playing to Win）框架，帮助用户系统性地制定商业、产品或项目战略。它通过五个相互关联的战略选择级联来引导用户：制胜愿景（Winning Aspiration）、战场选择（Where to Play）、制胜方式（How to Win）、核心能力（Capabilities）和管理体系（Management Systems）。技能的核心价值在于强制用户做出明确的取舍，并确保所有选择相互强化，形成一个连贯的战略整体。它支持任何需要真正战略而非任务清单的场景，包括新产品发布、现有产品转型或平台类战略。工作流程包括逐步走完级联、测试一致性、识别核心战略张力，并逆向推导出“必须为真”的条件，以识别假设和风险。该技能输出一个包含战略级联各部分详细信息的结构化模板，并附带针对不同场景（新产品、成熟产品、多产品公司）的适应指南，非常适合在Claude Code、Cursor等AI编程助手或对话式AI中使用，以结构化的方式辅助战略思考。

兼容平台~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的“求胜之道”框架，强制做出五个关键战略选择，并检查它们之间是否相互强化。

关于每个选择的详细定义和诊断问题，请参考 framework.md。

工作流程

  1. 明确主题：确定需要战略的对象——公司、产品线、功能领域或新市场进入。如有歧义，请询问用户。同时确定时间范围（6个月？3年？）。

  2. 走完级联——按顺序处理所有五个选择。每个选择都约束下一个选择：

    选择1：我们的制胜愿景是什么？ 以具体、可衡量的方式定义胜利的模样。不是“做到最好”——而是为哪些客户实现什么具体成果？制胜愿景设定了目标，并为后续所有选择奠定框架。

    选择2：在哪里竞争？ 选择竞技场。这是最重要的战略选择——你选择不参与的地方与选择参与的地方同样重要。维度：客户细分、地理区域、产品类别、渠道、价值链环节。

    选择3：如何获胜？ 在选定的竞技场内定义竞争优势。只有两种通用战略：成本领先或差异化。选择哪一种？具体如何实现？是什么独特的价值主张让你成为显而易见的选择？

    选择4：必须具备哪些核心能力？ 确定赢得所选竞技场所需的3-5个核心能力。这些能力应该相互强化——每一项能力都使其他能力更有价值。区分今天已经具备的能力和需要构建的能力。

    选择5：需要什么样的管理体系？ 定义建立和维护这些能力所需的系统、结构和流程。这是战略转变为运营的地方——衡量系统、组织架构、人才、流程和文化。

  3. 测试级联的一致性：五个选择必须相互强化。检查：

    • 战场选择是否符合制胜愿景？
    • 制胜方式是否在选定的竞技场中创造了真正的优势？
    • 核心能力是否真正实现了制胜方式？
    • 管理体系是否构建并维持了核心能力？
    • 竞争对手读到这份战略后，是否能明确知道如何与你竞争？（如果答案是肯定的，那你的制胜方式还不够独特。）

  4. 识别核心战略张力：每个战略都涉及一个核心张力或取舍。明确地命名它——你放弃了什么？你在赌什么？为了让这个战略奏效，什么必须为真？

  5. 逆向推导“必须为真”的条件：对于每个选择，列出2-3个必须成立的条件，该选择才能有效。这些条件将成为你的战略风险和需要验证的假设。

输出模板

# 求胜之道：[主题]

## 战略背景
[用2-3句话描述当前形势、竞争格局以及为何需要战略清晰度]

## 战略级联

### 1. 制胜愿景
[胜利意味着什么？为了谁？截止何时？要具体且可衡量。]

### 2. 战场选择
**选定竞技场：**
- 客户细分：[具体是谁]
- 地理区域：[哪里]
- 产品类别：[什么]
- 渠道：[如何触达他们]
- 价值链位置：[哪个环节]

**明确不参与：**
- [你选择放弃的部分——这同样重要]

### 3. 制胜方式
**战略定位：** [成本领先 / 差异化——二选一]
**独特价值主张：** [1-2句话——为什么客户选择你而不是替代方案]
**关键差异化因素：**
- [差异化因素1]
- [差异化因素2]
- [差异化因素3]

### 4. 核心能力
| 能力 | 目前具备？ | 差距 | 优先级 |
|------|-----------|------|--------|
| [能力1] | 是/部分/否 | [缺失什么] | 关键/重要 |
| [能力2] | ... | ... | ... |

### 5. 管理体系
| 系统 | 目的 | 状态 |
|------|------|------|
| [系统1] | [它支持什么] | 存在/需要改进/缺失 |
| [系统2] | ... | ... |

## 级联一致性检查
[每一层是否强化了其他层？标记任何不一致之处。]

## 核心战略张力
[核心取舍是什么？你在赌什么？]

## “必须为真”的条件
| 选择 | 条件 | 信心 | 如何验证 |
|------|------|------|----------|
| 战场选择 | [条件] | 高/中/低 | [测试或证据] |
| 制胜方式 | [条件] | ... | ... |
| ... | ... | ... | ... |

## 建议的下一步行动
1. [验证风险最高的“必须为真”条件]
2. [填补最关键的差距]
3. [构建或修复最重要的管理体系]

分析的适应性调整

对于新产品或新市场进入：将大部分时间花在战场选择和制胜方式上。诱惑是想要处处参与——请抵制它。狭窄的选择才能胜利。

对于失去动力的现有产品：从制胜愿景开始，并检查当前的战场选择是否仍然合理。市场在变化——你的选择也应该变化。

对于平台或多产品公司：为每个产品/细分市场独立运行级联，然后检查整个产品组合的战略一致性。跨级联的共享能力是你的杠杆点。

提示

  • 最难的部分是选择不参与哪里。如果你的战场选择包括所有人，那你并没有战略。
  • “制胜方式”不是功能列表。它是客户选择你的原因，位于CEO能解释的层次。
  • 如果你无法识别核心战略张力，说明战略还不够艰难。
  • 将此技能与 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