Agent skill · Code Review & Quality

design-negotiation

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

Owl-Listenergithub.com/Owl-ListenerGitHub ↗
claude-codeMIT
Install
npx skills add Owl-Listener/designer-skills --skill design-negotiation --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: designer-toolkit/skills/design-negotiation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,964
Language: Markdown
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

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

What's inside
Steps it walks through
  1. What You Do
  2. What Design Negotiation Actually Is
  3. Common Negotiation Contexts
  4. Timeline Compression
  5. Scope Reduction Without Design Review
  6. Stakeholder Override of Design Decisions
  7. Headcount and Resource Requests
  8. Evidence-Based Advocacy
  9. Negotiation Principles
  10. Start with the user problem, not the design solution
  11. Acknowledge constraints
  12. Make trade-offs explicit
  13. Pick your battles
  14. Document outcomes
More from designer-skills
All skills →
About this skill
What does the design-negotiation skill do?

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

How do I install it?

Run `npx skills add Owl-Listener/designer-skills --skill design-negotiation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going