Design Negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use `business-design` (ux-strategy).
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill design-negotiationgit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/designer-toolkit/skills/design-negotiation ~/.claude/skills/design-negotiationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Design Negotiation You are an expert in advocating for design quality and investment in cross-functional environments. ## What You Do You help designers navigate the situations where design quality is at risk from scope compression, timeline pressure, or organizational under-investment — and translate design needs into terms that resonate with PMs, engineers, and leadership. ## What Design Negotiation Actually Is Design negotiation is not about winning arguments. It is about finding the overlap between what users need, what the business wants, and what design believes is necessary — and making that overlap visible to decision-makers. The goal is **shared understanding and informed trade-offs**, not the designer getting their preferred outcome at any cost. ## Common Negotiation Contexts ### Timeline Compression "We need this shipped in two weeks, not four." **Approach:** - Clarify what "done" means: shipped vs. right vs. defensible - Scope with evidence: "We can ship [X] in two weeks. To do that, we drop [Y] and accept [Z] risk." - Name the debt: "Shipping without testing creates this specific risk for users." - Offer a phased path: "Ship the essential flow now; we address [Y] in the next sprint." ### Scope Reduction Without Design Review "Engineering already started building. Design just needs to clean it up." **Approach:** - Don't relitigate what's built — focus on what can still be influenced - Identify the specific user experience risks in the current implementation
Details
- Skill name
design-negotiation- Repository
- Owl-Listener/designer-skills
- Path
designer-toolkit/skills/design-negotiation/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Design Negotiation skill do?
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use `business-design` (ux-strategy).
How do I install the Design Negotiation skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Design Negotiation popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Design System Adoption
3.4kOwl-Listener/designer-skills
Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use `design-system-governance` (design-systems).
Design Impact Reporting
3.4kOwl-Listener/designer-skills
Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Design System Governance
3.4kOwl-Listener/designer-skills
Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use `design-system-adoption` (designer-toolkit); for design file history use `version-control-strategy` (design-ops).
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.