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

running-decision-processes运行决策过程

Agent Skill

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

总安装

742

周安装

30

GitHub Stars

3

下载量

233
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/oldwinter/skills --skill running-decision-processes

简介

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。

  • 适合围绕代码变更和仓库状态进行整理与分析。
  • 可结合来源仓库 README 核验具体用法和权限范围。
  • 安装前建议确认是否会触发命令执行或文件读写操作。
  • running-decision-processes 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Running Decision Processes

Scope

Covers

  • Running an end-to-end decision process for a cross-functional, high-stakes, or high-ambiguity decision
  • Making implicit assumptions explicit (so they can be tested and reviewed later)
  • Avoiding “decision drift” (hesitation, hidden vetoes, unclear decision rights)
  • Capturing durable artifacts: decision brief, roles, meeting plan, decision log, comms, and a review loop

When to use

  • “Draft a decision memo / pre-read and run the decision meeting.”
  • “We’re stuck between two bad options—help us decide and commit.”
  • “Set up RAPID/DACI/RACI for this decision and clarify who decides.”
  • “Create an options + criteria matrix and a decision log entry.”
  • “This feels like a one-way door / irreversible decision—tighten the process.”

When NOT to use

  • You need to decide what problem to solve (do problem definition first).
  • You need prioritization across many opportunities (use a roadmap/prioritization workflow).
  • The “decision” is actually a status update or routine coordination (use a meeting/operating cadence).
  • The decision is personal/legal/HR or requires specialist counsel (escalate to humans and domain experts).

Inputs

Minimum required

  • Decision to make (one sentence) and decision deadline (or “no later than” date)
  • Context/why now (what changed; what happens if you don’t decide)
  • Scope boundaries + non-negotiables (policy, budget, timeline, customer commitments)
  • Stakeholders and required approvers (who can block / who must live with the outcome)
  • Current options under consideration (even if rough) and key uncertainties

Missing-info strategy

  • Ask up to 5 questions from references/INTAKE.md.
  • If answers are unavailable, proceed with explicit assumptions and label unknowns.

Outputs (deliverables)

Produce a Decision Process Pack (Markdown in-chat, or files if requested) in this order:

  1. Decision Brief / Pre-read (problem, context, decision statement, constraints, criteria, options, recommendation if any)
  2. Options + Criteria Matrix (including assumptions/unknowns that drive the choice)
  3. Decision Rights + Process (RAPID/DACI/RACI, roles, timeline, meeting plan)
  4. Decision Log Entry (decision, rationale, tradeoffs, assumptions, owner, review date)
  5. Decision Communication (announcement + what changes + next steps)
  6. Decision Review Plan (what to measure, when to revisit, how to learn)
  7. Risks / Open questions / Next steps (always included)

Templates: references/TEMPLATES.md

Workflow (8 steps)

1) Classify the decision (speed vs rigor)

  • Inputs: Decision statement (draft); deadline; stakes.
  • Actions: Classify as one-way door (hard to reverse) vs two-way door (reversible). Set a timebox and required rigor (light/standard/heavy). Name the failure cost (what’s the worst credible outcome?).
  • Outputs: Decision classification + process intensity + timebox.
  • Checks: The process chosen matches reversibility and stakes (no “heavy process” for reversible choices; no “wing it” for irreversible ones).

2) Make the decision explicit (anti-hesitation)

  • Inputs: Context/why now; constraints; success criteria.
  • Actions: Turn implicit debate into a crisp decision: “We are deciding X by date to achieve Y.” List non-negotiables and what “good” means.
  • Outputs: Decision Brief sections: Decision statement, Why now, Success criteria, Constraints.
  • Checks: A stakeholder can restate the decision in one sentence without adding qualifiers.

3) Gather context (historian pass)

  • Inputs: Prior docs; past decisions; stakeholder perspectives.
  • Actions: Reconstruct relevant history (what was tried, what failed, and why). Surface “baggage” and hidden constraints. Collect only the decision-relevant facts.
  • Outputs: Decision Brief sections: Background, Prior decisions + rationale, Known constraints.
  • Checks: The brief distinguishes facts vs assumptions vs opinions.

4) Generate options + criteria; log assumptions

  • Inputs: Candidate options; goals; constraints.
  • Actions: Define evaluation criteria and (if helpful) weights. Expand to 2–4 viable options (including “do nothing” if appropriate). For each option, make key assumptions explicit (what must be true for this to work?).
  • Outputs: Options + Criteria Matrix; Assumptions/Unknowns list.
  • Checks: Each option has at least 2–3 explicit assumptions; criteria reflect actual tradeoffs (not “everything is important”).

5) Design the decision process + decision rights

  • Inputs: Stakeholder list; org constraints; decision intensity.
  • Actions: Choose a decision-rights model (RAPID/DACI/RACI). Assign roles (who recommends, who decides, who must be consulted, who is informed). Create a tight plan: pre-read, input window, meeting, decision capture, comms.
  • Outputs: Decision Rights + Process doc; meeting plan.
  • Checks: There is exactly one Decider (or a clearly defined decision body), and veto power is explicit.

6) Run a “curiosity loop” (contextual advice)

  • Inputs: Key unknowns; list of 8–12 people to consult (mix of experts + context-aware peers).
  • Actions: Ask lightweight, specific questions that demand rationale (“pick top 2 and why”, “what would change your mind?”). Capture inputs, disagreements, and decision-relevant evidence. Update options/assumptions accordingly.
  • Outputs: Curiosity Loop input summary; updated matrix/assumptions.
  • Checks: Inputs are specific and actionable (not generic opinions); dissent is recorded, not smoothed over.

7) Decide and commit (document the why)

  • Inputs: Final brief + matrix; role assignments; meeting agenda.
  • Actions: Run the decision meeting (or async decision) with a bias toward clarity. Make the decision explicit, name the tradeoffs, assign an owner, and set a review date. Document rationale and what would cause a revisit.
  • Outputs: Decision Log Entry; committed next steps; decision announcement draft.
  • Checks: The decision and owner are unambiguous; the team knows what changes tomorrow.

8) Communicate, execute, and review (learning loop)

  • Inputs: Decision log; implementation plan; metrics.
  • Actions: Send the decision communication. Translate into tasks/milestones. Schedule a review to compare outcomes vs assumptions and capture learning (keep “intuition” testable).
  • Outputs: Sent comms (or ready-to-send); review plan; retrospective prompts.
  • Checks: A review date and measurement plan exist; assumptions are testable and tracked.

Quality gate (required)

Examples

Example 1: “We need to decide whether to sunset Feature X by March 15. Create a decision memo, run a RAPID decision process, and draft the announcement.” Expected: Decision Brief + options/criteria matrix + RAPID roles + decision log entry + comms + review plan.

Example 2: “We’re split on building vs buying an analytics tool. It’s a one-way door. Set up a rigorous process and capture assumptions so we can learn.” Expected: One-way door classification + weighted criteria + assumptions log + consultation loop + decision log with review date.

Boundary example: “Help me decide if I should change careers.” Response: This skill is for organizational product/leadership decisions; suggest a personal decision framework or coach instead.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.83%
按下载量换算79

Claude

32.45%
按下载量换算76

Cursor

17.2%
按下载量换算40

Gemini CLI

10.09%
按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills