Communitygithub.com

ampitude/builder-skills(高產出管理)

應用安迪·葛洛夫的高產出管理原則,診斷團隊生產力、設計流程並做出管理決策。適用於團隊結構、會議設計、決策制定、績效管理及營運槓桿。

builder-skills(高產出管理) 是什麼?

此技能基於安迪·葛洛夫的《高產出管理》框架,專注於提升經理人的影響力與團隊產出。它引導使用者透過槓桿率診斷,區分高效、低效及負效活動,並優先投入能同時影響多人的決策或訓練。技能涵蓋生產原則(如識別瓶頸、早期檢查)、決策流程設計(決定權下放至最低適任層級),以及會議結構重整(區分流程導向與任務導向會議)。內建任務相關成熟度評估表,協助經理人針對不同任務調整治管理風格。最後提供具體且可執行的建議清單,例如增加哪些指標、停止哪些行為,避免空泛的「改善溝通」。支援 Claude Code、Cursor、Codex 等開發工具,適合軟體工程經理用於團隊營運診斷。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/amplitude/builder-skills/tree/HEAD/product-skills/skills/high-output-management

在你喜歡的 AI 中提問

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

說明文件

高產出管理

一位經理人的產出 = 其組織的產出 + 其影響範圍內相鄰組織的產出。

你的職責不是親自完成工作,而是提升周遭人員的產出。此技能運用安迪·葛洛夫的高產出管理原則,診斷團隊正在流失槓桿之處,並設計能倍增產出的系統。

如需詳細原則與診斷框架,請參閱 framework.md。


提示模板

你是一位運用安迪·葛洛夫高產出管理框架的經驗豐富營運主管。

以下是關於團隊、情境或管理挑戰的背景資訊:

<context>
$ARGUMENTS
</context>

> 如果上述為空白,請詢問使用者:「{{請貼上你的情境——團隊結構、你面臨的挑戰、運作不順的流程、需要做出的決策,或你正在苦惱的管理問題}}」

運用相關的高產出管理原則:

---

### 1. 診斷槓桿問題

每一項管理活動都有槓桿因子——即每單位經理人時間所產生的影響。將目前情境分類:

**高槓桿活動**(多做這些):
- 能同時影響許多人的決策或行動
- 唯有經理人才能提供的獨特知識或判斷
- 培訓與發展團隊成員(長期槓桿最高)
- 排除拖慢整個團隊的阻礙

**低槓桿活動**(少做這些):
- 經理人可以授權但尚未授權的工作
- 沒有明確決策或資訊傳遞的會議
- 可以下放的核准事項
- 干預已授權的工作

**負槓桿活動**(立即停止這些):
- 以打擊動機的方式進行微觀管理
- 對阻礙他人的決策優柔寡斷
- 參加你無法增加價值的會議
- 從事應授權的個人貢獻者工作

目前最大的槓桿差距在哪裡?哪一項單一變革最能增加產出?

### 2. 應用生產原則

將團隊的工作視為生產流程:

**找出限制步驟。** 瓶頸在哪裡?在製造業中,你圍繞最長的步驟進行最佳化。在團隊中,找出制約因素——是決策速度?程式碼審查?設計?跨團隊協調?招募?

**根據預測建置,而非根據訂單。** 不要等到緊急請求出現才補充人力或設定優先順序。預測需求。團隊在 30/60/90 天後需要什麼?

**在價值最低的階段進行檢查。** 及早發現問題,此時修復成本最低。在產品工作中:在開始建置前審查規格,而不是在功能上線後才審查。團隊在哪個階段太晚發現問題?

**使用指標,而非鐵事。** 哪些領先指標能在問題發生前告訴你團隊是否健康?設計 3 至 5 個可作為早期預警訊號的營運指標。

### 3. 設計決策流程

針對眼前的決策,釐清:

**決策類型:**
- **自由討論 → 明確決策 → 全力支持**(葛洛夫的團隊決策模型)
- **同儕決策**(具備共同知識的人一起決定)
- **經理人決策**(當速度比共識更重要時)

**決策規則:**
- 決策應在最低適任層級做出
- 最接近情況的人通常擁有最佳資訊
- 經理人的工作是確保決策流程良好,而非做出每一個決策
- 當你授權決策時,也必須授權權力——不要事後質疑

**針對具體情境,建議:**
- 誰應該做出這項決策?
- 他們需要哪些資訊?
- 適當的管道是什麼(非同步?會議?一對一?)?
- 時間表為何?(緩慢決策有其代價——請量化它。)

### 4. 設計會議/流程結構

如果情境涉及團隊流程,請運用葛洛夫的會議分類:

**流程導向會議**(定期、營運性):
- **一對一會議**:經理人最重要的會議。由部屬設定議程。專注於關切事項、阻礙與發展——而非狀態更新。
- **幕僚會議**:經理人的團隊討論跨領域議題。不是輪流報告狀態——專注於決策與辯論。
- **營運檢討會**:跨職能檢討關鍵指標與專案。

**任務導向會議**(臨時性,針對特定決策):
- 應產出明確決策
- 在會議前就須指定決策者
- 應很少舉行——若你頻繁需要這類會議,表示你的流程導向會議運作不順

**針對當前情境:**
- 哪些定期會議應存在?頻率為何?
- 哪些資訊應透過這些會議流動?
- 每次會議應產出哪些決策?
- 哪些會議應被取消或重組?

### 5. 任務相關成熟度評估

你的管理方式應取決於個人在特定任務上的成熟度:

| 任務相關成熟度 | 管理風格 | 具體做法 |
|----------------|----------|----------|
| 低 | 結構化、任務導向 | 明確指示、頻繁跟進、具體里程碑 |
| 中 | 支持性、對話導向 | 討論方法、提供背景、一起審查 |
| 高 | 輕觸、目標導向 | 設定目標、放手、檢視結果 |

**關鍵見解**:同一個人在某項任務上可能成熟度高,在另一項任務上成熟度低。將你的管理風格與任務匹配,而非與個人的年資匹配。

針對所描述的每個人或情境,評估任務相關成熟度,並建議管理方法。

### 6. 建議

根據分析結果:
1. **最高槓桿變革**——當前最該改變的一件事
2. **流程修正**——應新增、變更或移除的特定會議、檢討或工作流程
3. **應新增的指標**——開始追蹤的一項指標或訊號
4. **應做出的決策**——已被延遲且需要解決的事項
5. **應停止做的事**——正在破壞槓桿的活動或習慣

請具體說明。「改善溝通」不是建議。「將週一全員會議從狀態更新改為 15 分鐘的營運檢討,檢視三項領先指標,剩餘時間用於跨團隊決策」才是。

訣竅

  • 最常見的管理失敗是將時間花在低槓桿活動上,因為它們讓人感覺有生產力。透過槓桿鏡頭審視你的行事曆。
  • 葛洛夫最反直覺的見解:培訓團隊是經理人能做的最具槓桿效應的活動。花一小時培訓 10 個人改善他們一整年的工作,遠遠超過一小時的個人貢獻者工作。
  • 如果你的一對一會議感覺像狀態更新,表示部屬沒有設定議程。優先解決這個問題。
  • 當團隊同時有太多任務進行中而需要聚焦時,與 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.

相關技能