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 / Use
npx skills add Owl-Listener/designer-skills --skill design-negotiationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of design-negotiation
design-negotiation scores 83/100 on our quality scale, 3092nd of 4,700 Development & Engineering skills we index.
Its SKILL.md is 5.4 KB long, well organised into 17 sections and no code examples: a solid amount of guidance for an agent.
With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so design-negotiation is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
design-negotiation compared with similar skills
All 4 of these similar skills score higher than design-negotiation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| design-negotiation (this skill)by Owl-Listener | 83 | 2.7k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install design-negotiation?
- Run
npx skills add Owl-Listener/designer-skills --skill design-negotiation. The install tabs above show the steps for each supported agent. - Which AI agents does design-negotiation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is design-negotiation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is design-negotiation still maintained?
- The repository was last updated about 2 months ago, so design-negotiation is actively maintained.
Skill content
View source on GitHubname: design-negotiation
description: 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).
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
- Prioritize the 2–3 highest-impact changes; accept the rest as debt to document
- Establish a process agreement for next time
Stakeholder Override of Design Decisions
"The CEO wants the button to be red." Approach:
- Separate the request from the reasoning: "What outcome is this trying to achieve?"
- Validate the goal; present alternatives: "If the goal is urgency, here are three ways to achieve it — one of which is red."
- Bring data: user testing, accessibility, precedent in the design system
- Document the decision either way: what was decided, who made it, what the trade-off was
Headcount and Resource Requests
"We need a third designer on this project." Approach:
- Quantify current scope vs capacity: "We have X design dependencies for Y delivery date; current capacity covers Z."
- Translate to business risk: "Without the additional resource, we ship [specific feature] without design, or we push [milestone] by X weeks."
- Propose alternatives if headcount isn't available: scope reduction, phased delivery, design system acceleration
Evidence-Based Advocacy
Design negotiation is strongest when grounded in evidence:
- User research: "We tested this flow with 8 users; 6 couldn't complete the task."
- Metrics: "The current pattern has a 34% drop-off at step 3."
- Competitive context: "Every comparable product in this space supports X."
- Accessibility and legal: "This pattern fails WCAG 1.4.3; that's a compliance risk."
- Design system precedent: "The system already solves this — deviating creates maintenance debt." Avoid arguments based on taste ("this looks better") or authority ("I'm the designer") — they don't land with non-designers and they shouldn't have to.
Negotiation Principles
Start with the user problem, not the design solution
"Users are confused at this step" is more compelling than "this layout is unclear." Lead with the problem; the solution follows.
Acknowledge constraints
Engineers have technical constraints; PMs have delivery pressure; leadership has business goals. Dismissing these weakens your position. Name them first: "I understand we need this by Q3…"
Make trade-offs explicit
Decision-makers often don't know they're making a trade-off. Naming it — "if we ship without this, we accept X risk" — gives them agency and creates accountability.
Pick your battles
Not every design decision is worth negotiating. Reserve your credibility for the things that genuinely affect users. Let go of things that won't.
Document outcomes
When a decision goes against design's recommendation, write it down: what was decided, why, and what the expected impact is. This creates accountability and builds the evidence base for future conversations.
Building Long-Term Influence
Negotiation outcomes depend heavily on the relationships and credibility you've built before the negotiation:
- Deliver consistently: teams trust designers who ship; trust opens room for pushback
- Speak the business language: designers who understand revenue, cost, and risk are taken more seriously in strategic conversations
- Bring data habitually: teams that routinely hear research in design reviews start expecting it everywhere
- Celebrate shared wins: when design investment leads to measurable outcomes, make sure the team knows — publicly and with specifics
Best Practices
- Prepare for high-stakes conversations in advance: know the data, anticipate objections, have alternatives ready
- Never go into a negotiation without a fallback position — what's the minimum acceptable outcome?
- Ask questions before proposing solutions; understand the other party's constraints before defending yours
- Follow up in writing after verbal agreements — misremembers are common under deadline pressure
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
