Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计未展示

negotiation-alignment-governance谈判协调治理

Agent Skill

negotiation-alignment-governance 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,272

周安装

53

GitHub Stars

公开资料未说明

下载量

424
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:negotiation-alignment-governance(谈判协调治理)
来源仓库:https://github.com/lyndonkl/claude
仓库路径:skills/negotiation-alignment-governance
安装命令:
npx skills add lyndonkl/claude --skill "negotiation-alignment-governance"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

AgentSkills.tonpx skills
npx skills add lyndonkl/claude --skill "negotiation-alignment-governance"

简介

谈判协调治理用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果时使用。

  • 适用于谈判策略分析、组织对齐评估或治理框架研究等场景,可结合来源仓库进一步核验具体用法。
  • 通过 npx skills add lyndonkl/claude --skill "negotiation-alignment-governance" 命令安装,需确认权限范围和维护状态。
  • 使用前建议检查是否会触发联网、命令执行或文件读写操作,确保符合当前环境的安全策略。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

name
negotiation-alignment-governance
description
Use when stakeholders need aligned working agreements, resolving decision authority ambiguity, navigating cross-functional conflicts, establishing governance frameworks (RACI/DACI/RAPID), negotiating resource allocation, defining escalation paths, creating team norms, mediating trade-off disputes, or when user mentions stakeholder alignment, decision rights, working agreements, conflict resolution, governance model, or consensus building.

Negotiation Alignment Governance

Table of Contents

Purpose

Create explicit stakeholder alignment through negotiated working agreements, clear decision rights, and conflict resolution protocols—transforming ambiguity and tension into shared understanding and actionable governance.

When to Use

Decision Authority Ambiguity:

  • Multiple stakeholders believe they have final say
  • Unclear who should be consulted vs informed
  • Decisions blocked because no one owns them
  • Frequent "I thought you were doing that" moments

Cross-Functional Conflict:

  • Departments optimizing for different goals
  • Resource contention between teams
  • Trade-off disputes (quality vs speed, innovation vs stability)
  • Scope disagreements between stakeholders

Alignment Needs:

  • New team forming and needs working agreements
  • Org restructure creating unclear boundaries
  • Cross-functional initiative requiring coordination
  • Partnership or joint venture needing governance

Negotiation Scenarios:

  • Competing priorities requiring resolution
  • Stakeholder expectations needing alignment
  • SLAs and commitments to negotiate
  • Risk tolerance differences to reconcile

What Is It

Negotiation-alignment-governance creates explicit agreements on:

1. Decision Rights (Who Decides):

  • RACI: Responsible, Accountable, Consulted, Informed
  • DACI: Driver, Approver, Contributors, Informed
  • RAPID: Recommend, Agree, Perform, Input, Decide
  • Consent-based frameworks

2. Working Agreements (How We Work):

  • Communication norms (sync vs async, response times)
  • Meeting protocols (agendas, decision methods)
  • Quality standards and definition of done
  • Escalation paths and conflict resolution

3. Conflict Resolution (When We Disagree):

  • Structured dialogue formats
  • Mediation protocols
  • Disagree-and-commit mechanisms
  • Escalation criteria

Example: Product wants to ship fast, Engineering wants quality. Instead of endless debates:

  • Decision rights: Product owns feature scope (DACI: Approver), Engineering owns quality bar (veto on production issues)
  • Working agreement: Weekly trade-off discussion with data (bug rate, tech debt, customer complaints)
  • Conflict resolution: If blocked, escalate to VP with joint recommendation and decision criteria

Workflow

Copy this checklist and track your progress:

Negotiation Alignment Governance Progress:
- [ ] Step 1: Map stakeholders and tensions
- [ ] Step 2: Choose governance approach
- [ ] Step 3: Facilitate alignment
- [ ] Step 4: Document agreements
- [ ] Step 5: Establish monitoring

Step 1: Map stakeholders and tensions

Identify all stakeholders, their interests and concerns, current tensions or conflicts, and decision points needing clarity. See Common Patterns for typical stakeholder configurations.

Step 2: Choose governance approach

For straightforward cases with clear stakeholders → Use resources/template.md for RACI/DACI and working agreement structures. For complex cases with multiple conflicts or nested decisions → Study resources/methodology.md for negotiation techniques, conflict mediation, and advanced governance patterns.

Step 3: Facilitate alignment

Create negotiation-alignment-governance.md with: stakeholder map, decision rights matrix (RACI/DACI/RAPID), working agreements (communication, quality, processes), conflict resolution protocols, and escalation paths. Facilitate structured dialogue to negotiate and reach consensus. See resources/methodology.md for facilitation techniques.

Step 4: Document agreements

Self-assess using resources/evaluators/rubric_negotiation_alignment_governance.json. Check: decision rights are unambiguous, all key stakeholders covered, agreements are specific and actionable, conflict protocols are clear, escalation paths defined. Minimum standard: Average score ≥ 3.5.

Step 5: Establish monitoring

Set up regular reviews of governance effectiveness (quarterly), define triggers for updating agreements, establish metrics for decision velocity and conflict resolution, and create feedback mechanisms for stakeholders.

Common Patterns

Decision Rights Frameworks

RACI (Most Common):

  • Responsible: Does the work
  • Accountable: Owns the outcome (only ONE person)
  • Consulted: Provides input before decision
  • Informed: Notified after decision
  • Use for: Process mapping, task allocation

DACI (Better for Decisions):

  • Driver: Runs the process, gathers input
  • Approver: Makes the final decision (only ONE)
  • Contributors: Provide input, must be consulted
  • Informed: Notified of decision
  • Use for: Strategic decisions, product choices

RAPID (Best for Complex Decisions):

  • Recommend: Propose the decision
  • Agree: Must agree (veto power)
  • Perform: Execute the decision
  • Input: Consulted for expertise
  • Decide: Final authority
  • Use for: Major strategic choices with compliance/legal concerns

Advice Process (Distributed Authority):

  • Anyone can make decision after seeking advice from:

- Those who will be affected - Those with expertise

  • Decision-maker is accountable
  • Use for: Empowered teams, flat organizations

Typical Stakeholder Conflicts

Product vs Engineering:

  • Conflict: Feature scope vs technical quality
  • Resolution: Product owns "what" (feature priority), Engineering owns "how" and quality bar
  • Escalation: Joint recommendation with data to VP

Business vs Legal/Compliance:

  • Conflict: Speed to market vs risk mitigation
  • Resolution: Business owns opportunity decision, Legal has veto on unacceptable risk
  • Escalation: Risk committee with quantified trade-offs

Centralized vs Decentralized Teams:

  • Conflict: Standards vs autonomy
  • Resolution: Central team sets minimum viable standards, teams choose beyond that
  • Escalation: Architecture review board for exceptions

Working Agreement Templates

Communication Norms:

  • Synchronous (meetings): For collaboration, negotiation, brainstorming
  • Asynchronous (docs, Slack): For updates, approvals, information sharing
  • Response time expectations: Urgent (<2h), Normal (<24h), FYI (no response needed)
  • Meeting defaults: Agenda required, decisions documented, async-first when possible

Decision-Making Norms:

  • Reversible decisions: Use consent (no objections) for speed
  • Irreversible decisions: Use consensus or explicit DACI
  • Time-box decisions: If no consensus in N discussions, escalate with options
  • Document decisions: ADRs for architecture, decision logs for product

Conflict Resolution Norms:

  • Direct dialogue first (1:1 between parties)
  • Mediation second (neutral third party facilitates)
  • Escalation third (manager/leader decides with input)
  • Disagree-and-commit: Once decided, all commit to execution

Guardrails

Decision Rights:

  • Only ONE person/role is "Accountable" or "Approver"
  • Avoid "everyone is consulted" (decision paralysis)
  • Consulted ≠ consensus—input gathered, then decider decides
  • Define scope: What decisions does this cover?

Working Agreements:

  • Make agreements specific and observable (not "communicate well" but "respond to Slack in 24h")
  • Include both positive behaviors and boundaries
  • Revisit quarterly—agreements expire without review
  • Get explicit consent from all parties

Conflict Resolution:

  • Assume good intent—conflicts are about goals/constraints, not character
  • Focus on interests (why) not positions (what)
  • Use objective criteria when possible (data, benchmarks, principles)
  • Separate people from problem

Facilitation:

  • Remain neutral if mediating (don't take sides)
  • Ensure psychological safety (no retribution for honesty)
  • Make implicit tensions explicit (name the elephant)
  • Don't force consensus—sometimes need to escalate

Red Flags:

  • Too many decision-makers (slows everything)
  • Shadow governance (real decisions made elsewhere)
  • Agreements without accountability (no consequences)
  • Conflict avoidance (swept under rug, not resolved)

Quick Reference

Resources:

  • resources/template.md - RACI/DACI/RAPID templates, working agreement structures, conflict resolution protocols
  • resources/methodology.md - Negotiation techniques (principled negotiation, BATNA analysis), conflict mediation, facilitation patterns, governance design for complex scenarios
  • resources/evaluators/rubric_negotiation_alignment_governance.json - Quality criteria

Output: negotiation-alignment-governance.md with stakeholder map, decision rights matrix, working agreements, conflict protocols, escalation paths

Success Criteria:

  • Decision rights unambiguous (one Accountable/Approver per decision)
  • All key stakeholders covered in framework
  • Agreements specific and actionable (observable behaviors)
  • Conflict resolution protocol clear with escalation path
  • Regular review cadence established
  • Score ≥ 3.5 on rubric

Quick Decisions:

  • Clear stakeholders, simple decisions? → RACI or DACI template
  • Complex multi-party negotiation? → Use methodology for principled negotiation
  • Active conflict? → Start with mediation techniques from methodology
  • Distributed team? → Consider advice process over hierarchical approval

Common Mistakes:

  1. Multiple "Accountable" roles (diffuses responsibility)
  2. Everyone consulted (decision paralysis)
  3. Vague agreements ("communicate better" vs "respond in 24h")
  4. No review/update cycle (agreements decay)
  5. Shadow governance (official RACI ignored, real decisions made informally)
  6. Forcing consensus (sometimes need to disagree-and-commit)

Key Insight: Explicit governance reduces coordination costs over time. Initial investment in alignment pays dividends through faster decisions, less rework, and lower conflict.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

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

平台分布

Claude Code

29.43%
按下载量换算125

Gemini CLI

22.29%
按下载量换算95

Antigravity

17.82%
按下载量换算76

windsurf

13.86%
按下载量换算59

OpenCode

8.44%
按下载量换算36

github-copilot

3.27%
按下载量换算14

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills