Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计通过

making-product-decisions做出产品决策

Agent Skill

making-product-decisions 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

612

周安装

25

GitHub Stars

239

下载量

196
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:making-product-decisions(做出产品决策)
来源仓库:https://github.com/flpbalada/my-opencode-config
仓库路径:skills/making-product-decisions
安装命令:
npx skills add https://github.com/flpbalada/my-opencode-config --skill making-product-decisions
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/flpbalada/my-opencode-config --skill making-product-decisions

简介

making-product-decisions 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理时使用。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 当前分类为开发,暂无更详细说明可供参考。

SKILL.md

Making Product Decisions - Structured Decision Framework

A meta-framework for making and documenting product decisions. Combines decision science principles with practical product management needs to ensure better decisions, stakeholder alignment, and organizational learning.

When to Use This Skill

  • Choosing between competing priorities or approaches
  • Making irreversible or high-stakes decisions
  • Aligning stakeholders with different perspectives
  • Documenting decisions for future reference
  • Evaluating past decisions for learning
  • Delegating decision-making authority

Core Concepts

Decision Types (Bezos Framework)

+------------------+------------------+
|   Type 1         |   Type 2         |
|   (One-way door) |   (Two-way door) |
+------------------+------------------+
| Irreversible     | Reversible       |
| High stakes      | Lower stakes     |
| Slow, careful    | Fast, iterate    |
| Senior decision  | Delegate widely  |
+------------------+------------------+

Decision Quality vs. Outcome

Good OutcomeBad Outcome
Good DecisionDeserved successBad luck
Bad DecisionGood luckDeserved failure

Judge decisions by process quality, not just outcomes.

Data-Informed vs. Data-Driven

ApproachWhen to Use
Data-drivenClear metrics, sufficient data, understood system
Data-informedIncomplete data, novel situations, judgment needed
Intuition-ledTime pressure, expert domain, pattern matching

Most product decisions should be data-informed, not purely data-driven.

Analysis Framework

Step 1: Frame the Decision

ElementQuestion
WhatWhat exactly are we deciding?
WhyWhy does this decision matter?
WhoWho should be involved?
WhenWhen must we decide by?
ReversibilityType 1 or Type 2 door?

Step 2: Generate Options

Always have at least 3 options:

  1. Do nothing / status quo
  2. Option A
  3. Option B

Avoid binary framing - it limits thinking.

Step 3: Establish Criteria

CriterionWeightWhy It Matters
[Criterion 1][1-5][Explanation]
[Criterion 2][1-5][Explanation]
[Criterion 3][1-5][Explanation]

Step 4: Evaluate Options

OptionCriterion 1Criterion 2Criterion 3Total
Status quo[Score][Score][Score][Sum]
Option A[Score][Score][Score][Sum]
Option B[Score][Score][Score][Sum]

Step 5: Document and Decide

Record:

  • Decision made
  • Rationale
  • Dissenting views
  • Success criteria
  • Review date

Output Template

## Product Decision Record

**Decision:** [Clear statement of what was decided] **Date:** [Date] **Decision
maker:** [Name] **Status:** [Proposed/Approved/Implemented]

### Context

**Problem/Opportunity:** [What prompted this decision]

**Constraints:** [Time, resources, dependencies]

**Reversibility:** [Type 1 / Type 2]

### Options Considered

| Option     | Description | Pros | Cons |
| ---------- | ----------- | ---- | ---- |
| Status quo | [Desc]      | [+]  | [-]  |
| Option A   | [Desc]      | [+]  | [-]  |
| Option B   | [Desc]      | [+]  | [-]  |

### Decision Criteria

| Criterion | Weight | Rationale |
| --------- | ------ | --------- |
| [C1]      | [1-5]  | [Why]     |
| [C2]      | [1-5]  | [Why]     |

### Evaluation

| Option  | [C1]  | [C2]  | Weighted Total |
| ------- | ----- | ----- | -------------- |
| [Opt 1] | [x/5] | [x/5] | [Score]        |
| [Opt 2] | [x/5] | [x/5] | [Score]        |

### Decision

**Chosen option:** [Option name]

**Rationale:** [Why this option best meets criteria]

**Dissenting views:** [Captured disagreements and concerns]

### Success Criteria

| Metric | Current | Target  | Measure By |
| ------ | ------- | ------- | ---------- |
| [M1]   | [Value] | [Value] | [Date]     |

### Review

**Review date:** [Date] **What we'll evaluate:** [Criteria for success/failure]

Real-World Examples

Example 1: Build vs. Buy

Decision: Build custom analytics or use third-party tool?

CriterionWeightBuildBuy
Time to market525
Customization352
Long-term cost434
Maintenance burden425
Total4266

Decision: Buy, despite customization limitations.

Example 2: Feature Prioritization

Decision: Next quarter focus - mobile app or API improvements?

Applied decision criteria:

  • Revenue impact (weight: 5)
  • User retention (weight: 4)
  • Strategic positioning (weight: 3)
  • Engineering complexity (weight: 2)

Result: Mobile app scored higher on revenue and retention despite higher complexity.

Best Practices

Do

  • Make decision criteria explicit before evaluating
  • Include "do nothing" as an option
  • Document dissenting opinions
  • Set review dates for major decisions
  • Separate decision quality from outcome

Avoid

  • Analysis paralysis on Type 2 decisions
  • HiPPO (Highest Paid Person's Opinion) decisions
  • Retroactive justification
  • Ignoring intuition entirely
  • Forgetting to review past decisions

Decision Speed Guidelines

TypeApproach
Type 1, high stakesTake time, involve stakeholders
Type 2, reversibleDecide quickly, iterate
Unclear typeDefault to faster, can always slow down

Integration with Other Methods

MethodCombined Use
Hypothesis TreeStructure analysis of options
Jobs-to-be-DoneGround criteria in user needs
Five WhysUnderstand decision root causes

Resources

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.18%
按下载量换算69

Claude

30.66%
按下载量换算60

Cursor

16.28%
按下载量换算32

Gemini CLI

8.41%
按下载量换算16

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills