← 返回
未分类 中文

Compensation

Offers, compensation framing, and negotiation planning. Use when evaluating offers or raises.
提供、薪酬框架和谈判规划。在评估报价或加薪时使用。
clawkk clawkk 来源
未分类 clawhub v1.0.0 1 版本 100000 Key: 无需
★ 0
Stars
📥 374
下载
💾 0
安装
1
版本
#latest

概述

Compensation

Structured guidance for offers, pay, and negotiation (not legal or tax advice): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

When to Offer This Workflow

Trigger conditions:

  • User mentions negotiation, offers, raises, compensation, or closely related work
  • They want a structured workflow rather than ad-hoc tips
  • They are preparing a review, rollout, or stakeholder communication

Initial offer:

Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style.

Workflow Stages

Stage 1: Clarify context & goals

Anchor on market context and priorities. Ask what success looks like, constraints, and what must not break. Capture unknowns early.

Stage 2: Design or plan the approach

Translate goals into a concrete plan around total comp components. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

Stage 3: Implement, validate, and harden

Execute with verification loops tied to negotiation script and BATNA. Prefer small steps, measurable checks, and rollback points where risk is high.

Stage 4: Operate, communicate, and iterate

Close the loop with written follow-ups: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle.

Checklist Before Completion

  • Goals and constraints are explicit for compensation discussions
  • Risks and trade-offs are stated, not hand-waved
  • Verification steps match the change’s impact (tests, canary, peer review)
  • Operational follow-through is covered (monitoring, docs, owners)

Tips for Effective Guidance

  • Be procedural: stage-by-stage, with clear exit criteria
  • Ask for missing context (environment, scale, deadlines) before prescribing
  • Prefer checklists and concrete examples over generic platitudes
  • If the user declines the workflow, switch to freeform help without lecturing

Handling Deviations

  • If the user wants to skip a stage: confirm and continue with what they need.
  • If context is missing: ask targeted questions before strong recommendations.
  • Prefer concrete examples, trade-offs, and verification steps over generic advice.

Quality Bar

  • Each recommendation should be actionable (what to do next).
  • Call out failure modes relevant to compensation talks (relationship risk, miscommunication, or unrealistic asks).
  • Keep tone direct and respectful of the user’s time.

版本历史

共 1 个版本

  • v1.0.0 当前
    2026-05-03 09:25 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

business-ops

Stripe

byungkyu
Stripe API 集成,支持托管 OAuth,实现对客户、订阅、发票、产品、价格和支付的可写金融集成。
★ 27 📥 26,121
ai-agent

Guard

clawkk
深度AI安全防护工作流—策略定义、输入/输出过滤、监控、升级与误报处理。用于降低有害内容。
★ 0 📥 998
business-ops

Calendar

ndcccccc
日历管理与日程安排。创建事件、管理会议,并实现多日历平台同步。
★ 7 📥 23,253