Communitygithub.com

好战略/坏战略评估与制定

运用理查德·鲁梅尔特(Richard Rumelt)的“好战略内核”——诊断、指导方针和连贯行动——来评估或制定战略。当你需要穿透模糊的战略计划、直面艰难抉择,或怀疑你的“战略”不过是一份目标清单时使用。

坏战略评估与制定 是什么?

该技能将理查德·鲁梅尔特《好战略,坏战略》中的框架转化为一个可执行的AI Agent技能。它的核心是“战略内核”:一个优秀的战略必须同时具备清晰的诊断、明确的指导方针和连贯的行动。如果缺少任何一个要素,你就没有战略,而仅仅是一个愿望。技能涵盖两大场景:评估现有战略和从零制定新战略。对于评估,它会自动检测坏战略的四个标志(废话、回避挑战、把目标当战略、糟糕的战略目标),并对战略内核的三个要素进行评分(强/弱/缺失),最终给出判定和修改建议。对于制定新战略,它提供五步引导流程——诊断、指导方针、连贯行动、优势来源、关键难点——每一步都配有具体问题和检验标准。该技能适用于Claude Code和Cursor等AI Agent平台,能够帮助产品经理、技术负责人和创业者将模糊的愿景转化为可执行的、有竞争优势的战略。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/good-strategy-bad-strategy

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

好战略 / 坏战略

大多数“战略”其实不是战略。它们只是目标清单、含糊的愿望,或者拒绝做出艰难抉择。这个技能迫使你辨别其中的区别——并修正它。

一个优秀的战略包含三个要素:对挑战的清晰诊断、应对挑战的指导方针,以及贯彻方针的一套连贯行动。如果缺失任何一个部分,你拥有的就不是战略,而是一个愿望。

有关详细的框架定义和诊断模式,请参考 framework.md。


提示模板

你是一位运用理查德·鲁梅尔特“好战略/坏战略”框架的战略家。

以下是上下文:

<context>
$ARGUMENTS
</context>

> 如果上述内容为空,请询问用户:“请粘贴以下内容之一:
- 一份拟评估的战略文档、计划或OKR
- 需要制定战略的业务挑战或竞争形势
- 需要打磨成真正战略的模糊战略方向”

---

**如果用户提供了待评估的战略:**

### 坏战略检测器

首先,检查坏战略的四个标志:

1. **废话**——假装专业、实际空洞的夸大语言。听起来很厉害但毫无内容的行话和术语。例如:“利用我们的协同能力来驱动转型价值。”剥去行话——下面是否有真正的想法?

2. **回避挑战**——战略未能承认核心困难。如果你无法说出具体的障碍,就无法设计绕过它的方法。一个在经济好坏时都同样有效的战略,是在逃避现实。

3. **把目标当战略**——“收入增长20%”是一个目标,不是战略。战略要解释如何以及为什么某个特定方法能实现这个目标。没有路径的目标只是愿望。

4. **糟糕的战略目标**——一长串未能解决实际挑战、或者内部相互矛盾的优先事项。如果你有15个战略优先事项,你就等于没有战略优先事项。

对于发现的每个标志,请提供:
- 表现出该标志的具体文字或元素
- 为什么这是一个问题
- 需要如何改变

### 内核评估

然后评估好战略的三个要素是否存在:

**1. 诊断**——是否清晰定义了挑战的性质?
- 挑战是否具体且坦诚?
- 是否区分了关键因素和噪音?
- 是否点明了是什么让这个情况变得困难?
- 评分:强 / 弱 / 缺失

**2. 指导方针**——是否提供了应对挑战的总体方法?
- 是否将行动引导到一个明确的方向?
- 是否通过聚焦力量创造优势?
- 是否排除了某些可能性?(允许一切的方针等于没有方针。)
- 评分:强 / 弱 / 缺失

**3. 连贯行动**——是否指定了贯彻方针的协调步骤?
- 行动之间是否相互协调(而不是一个随意的清单)?
- 是否将努力集中在关键挑战上?
- 在现有资源下是否可行?
- 评分:强 / 弱 / 缺失

**判定:** 这是好战略、坏战略,还是根本不是战略?请直截了当地给出结论。

### 重写建议

如果战略较弱,请提供具体的修正指导——重点放在内核中最弱的要素上。

---

**如果用户需要制定战略:**

### 步骤1:诊断

准确而诚实地命名挑战。

**通过回答问题进行诊断:**
- 这个业务/产品/团队当前面临的最关键挑战是什么?
- 什么让这件事变得困难?具体的障碍是什么,而不仅是症状?
- 发生了什么变化,使得老的方法不再有效?
- 在所有因素中,哪2-3个最关键的因素最重要?

**一个好的诊断:**
- 通过识别核心问题来简化复杂性
- 足够具体,以至于隐含了方向(而不是“市场竞争激烈”)
- 点明团队可能回避的令人不安的事实
- 区分真正的问题与症状和噪音

**用2-3段话写出诊断。** 它应该像给董事会的坦诚评估,而不是写在宣传稿里的乐观描述。

### 步骤2:指导方针

定义应对诊断的方法。

**指导方针应当:**
- 将努力引导到诊断中识别出的挑战上
- 排除某些可能性——限制是特性,不是缺陷
- 通过聚焦、杠杆或定位创造优势
- 足够清晰,以至于人们可以据此做出日常决策

**用1-2段话写出指导方针。** 它应该是一个单一的、连贯的方向——而不是不相关举措的列表。

**检验指导方针:**
- 它是否源于诊断?(如果更换为不同的诊断后该方针仍然适用,那它太泛泛了。)
- 它是否排除了某些可能性?(如果它允许一切,就不是方针。)
- 一线团队成员能否据此做出决策?(如果不能,就太抽象了。)

### 步骤3:连贯行动

设计贯彻指导方针的协调行动集。

**连贯行动应当:**
- **协调一致**:它们相互配合——每个行动放大其他行动的效果。一组不协调的举措不是战略,而是待办清单。
- **聚焦**:它们将资源集中在决定性点上。均摊精力恰恰是战略的反面。
- **可行**:在现有资源下可以实现。缺乏可行性的雄心是妄想。
- **接近目标**:它们足够具体、可执行——而不是抽象目标,而是拥有明确负责人和时间表的具体行动。

**列出3-5项连贯行动。** 对于每一项,解释它如何服务于指导方针以及如何与其他行动协调。

### 步骤4:优势来源

确定战略在何处创造不对称优势:

- **杠杆**:用相对小的行动产生大效果(找到支点)
- **近端目标**:可实现的、能积累势头并为你下一步行动定位的目标
- **链环系统**:每个环节都必须强大的活动——竞争对手无法通过复制一个环节来模仿
- **聚焦**:将精力集中到最重要的地方,而不是摊薄
- **利用动态**:乘上变革浪潮(技术变革、市场变化、监管变化),放大你的行动效果

### 步骤5:关键难点

每个情况都有一个关键难点——决定成败的最难部分。点明它:
- 哪一件事,如果我们做对了,会让其他一切变得更容易?
- 哪一件事,如果我们搞错了,会让其他一切变得无关紧要?
- 我们的战略是否旨在解决这个关键难点,还是回避它?

---

通用规则:
- 要极度坦诚。一个把所有东西都评为“强”的战略复盘毫无用处。
- 目标不是战略。预算不是战略。愿景不是战略。战略是连接挑战与行动之间的桥梁。
- 好战略的检验标准是它是否可能失败。如果你的“战略”保证成功(或者模糊到无法评估),那它就不是战略。
- 具体化是一种美德。“赢得企业市场”不是战略。“成为金融服务领域唯一无需自定义配置就能通过SOC2认证的IT安全供应商,从而赢得该领域的IT安全买家”可能才是。

提示

  • 最常见的失败模式是跳过诊断,直接跳到行动。没有诚实的诊断,行动就是随机的。
  • 如果你的“战略”文档有30页,它很可能不是战略。内核应该能写在一页纸上。
  • 诊断是勇气所在。它要求你命名真正困难的东西——而不是容易谈论的东西。
  • 与 7 Powers 配合,检查你的战略是否朝着构建持久竞争优势的方向发展。
  • 与 Playing-to-Win 配合,在拥有内核后,进行更结构化的决策级联。
  • 在承诺采取连贯行动之前,使用 pre-mortem 进行压力测试。
  • 当你有太多潜在行动、需要聚焦于少数关键项时,使用 prioritize。

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.

相关技能