value-specification
Translating organisational values and user expectations into system constraints.
适合你，如果你需要把抽象价值观落地为可执行的技术规范。
npx oh-my-skill add owl-listener/ai-design-skills/value-specificationcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- owl-listener/ai-design-skills/value-specificationnpx oh-my-skill verify owl-listener/ai-design-skills/value-specification怎么用
商店整理自技能原文 · 版本 f41b650 · 表述以原文为准将抽象的组织价值观和用户期望转化为可测试的系统约束规则。当价值观冲突时，按安全、准确、帮助、尊重、品牌的层级解决冲突，并呈现选项供用户选择。
当你要求 Claude 基于特定价值观（如“要负责”“要公平”）来约束行为，或需要将抽象原则转化为具体规则时触发。
技能原文 SKILL.md
Value Specification
Values are abstract. AI systems need concrete rules. Value specification is the design work of translating organisational principles and user expectations into implementable constraints.
The Translation Problem
Organisations say things like "be helpful" and "be responsible." These are useless as system constraints because they conflict:
- Being maximally helpful might mean giving dangerous information
- Being maximally responsible might mean refusing to help at all
- Being "fair" means different things in different contexts
The designer's job is to resolve these tensions into specific, testable rules.
Value Hierarchy
Not all values are equal. Establish a hierarchy:
- Safety: Prevent harm to users and others. This overrides everything.
- Accuracy: Don't mislead. When uncertain, say so.
- Helpfulness: Actually accomplish what the user needs.
- Respect: Treat users as capable adults. Don't patronise.
- Brand alignment: Reflect the organisation's identity and tone.
When values conflict, the hierarchy resolves the conflict. A safety concern overrides helpfulness. Accuracy overrides brand voice.
From Values to Rules
For each value, derive concrete rules:
- Value: "We respect user autonomy"
- Rule: "Always present options rather than making decisions for the user"
- Implementation: When the AI has multiple valid approaches, present them as choices with tradeoffs rather than picking one
- Test: Give the AI an ambiguous request. Does it ask the user to choose, or decide unilaterally?
Stakeholder Alignment
Different stakeholders have different value priorities:
- Users want helpfulness and speed
- Legal wants compliance and liability protection
- Brand wants consistency and tone
- Ethics wants fairness and transparency
- Engineering wants feasibility and maintainability
The designer mediates between these perspectives and produces a unified specification.
Design Artefacts
- Value hierarchy document with conflict resolution rules
- Value-to-rule mapping table
- Stakeholder value alignment matrix
- Test cases derived from value specifications