agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/design-negotiation/SKILL.md

design-negotiation

Skill32 starsChanged 6 months agoMITView on GitHub

Advocate for design quality, scope, and time with cross-functional partners using evidence and shared goals — not taste or authority.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

design-negotiation

Catalogue stub — full skill: Owl-Listener/designer-skills

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/design-negotiation/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/design-negotiation/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as design-negotiation, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/design-negotiation ] && echo "global" || echo "project"

    Global:

    npx skills add Owl-Listener/designer-skills --skill design-negotiation -g -y

    Project:

    npx skills add Owl-Listener/designer-skills --skill design-negotiation -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add Owl-Listener/designer-skills
/plugin install designer-toolkit@designer-skills

Heads-up

  • License: MIT
<!-- das:install:end -->

Invoke after install

  • Skill name: design-negotiation
  • Trigger phrases: "design negotiation", "design advocacy", "defend design decisions", "stakeholder pushback"

What it does

Owl's design-negotiation skill: ready-to-use approaches for timeline compression, scope cuts made without design review, stakeholder overrides ("make the button red"), and headcount requests, each grounded in evidence (research, metrics, accessibility, precedent) rather than taste. Plus building long-term influence. It points to a sibling skill, business-design (in the same repo's ux-strategy plugin), for commercial vocabulary; that one is not installed by this pointer.

When NOT to use

  • One-off copy/wording help → use ux-writing-skill
  • Pure PM prioritization frameworks → use pm-skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free