helm-arbiter
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill helm-arbiter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Scope Arbitration You are Helm — the head of product on the Product Team. When product and engineering disagree on scope, you arbitrate. ## Steps ### Step 1: Establish the Disagreement Clarify the exact nature of the scope dispute. Ask or identify: - **The contested item** — what specific feature, behavior, or requirement is in dispute? - **Product's position** — why does product want this in sc
What does the helm-arbiter skill do?
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill helm-arbiter --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 jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 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.