working-agreements
Write a team's working agreements — the small set of explicit norms (communication, meetings, decisions, conflict) that replace the assumptions people were silently violating, built from the team's actual frictions and revisited on a cadence. Use when asked create team working agreements, set norms for our new team, we keep clashing over how we work, or onboard people into how this team operates. Produces the friction-derived agreement set, the specific-behavior phrasing, the disagreement protocol, and the review cadence.
npx skills add mohitagw15856/pm-claude-skills --skill working-agreements --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.
# Working Agreements Skill Teams run on invisible rules — response-time expectations, camera norms, how decisions happen, whether 6pm messages demand answers — and every clash between two people's invisible rules gets misread as a character flaw ("he's unresponsive," "she's pushy"). Working agreements make the rules visible: a *small* set (6–10, not a constitution), derived from the team's actual frictions (not copied from a blog), phrased as observable behaviors ("we respond to non-urgent messages within one working day" — checkable) rather than values ("we communicate respectfully" — vibes), and revisited quarterly, because teams change and dead agreements poison live ones. ## What This Skill Produces - **The agreement set** — 6–10 norms across the friction zones: communication, meetings, decisions, availability, conflict - **The friction derivation** — each agreement traces to a real clash it resolves (the trace is what makes it stick) - **The disagreement protocol** — the one agreement every set needs: how we disagree, escalate, and commit - **The living rules** — where the set lives, how newcomers meet it, and the quarterly revisit ## Required Inputs Ask for these if not provi
- What This Skill Produces
- Required Inputs
- Framework: The Agreement Rules
- Output Format
- The Set
- The Disagreement Protocol (spelled out)
- Living Rules
- Quality Checks
- Anti-Patterns
What does the working-agreements skill do?
Write a team's working agreements — the small set of explicit norms (communication, meetings, decisions, conflict) that replace the assumptions people were silently violating, built from the team's actual frictions and revisited on a cadence. Use when asked create team working agreements, set norms for our new team, we keep clashing over how we work, or onboard people into how this team operates. Produces the friction-derived agreement set, the specific-behavior phrasing, the disagreement protocol, and the review cadence.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill working-agreements --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 mohitagw15856/pm-claude-skills, a repository with 1,255 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.