What do I need to use Collaboration Contract?

The project and the teams; The likely decisions; The handoff shapes; The leads.

Is Collaboration Contract free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Collaboration Contract

Q: How do I know the Collaboration Contract output is good?

The skill verifies itself against its own quality checks: The both-teams-assume-they-own decisions were forced and settled; Every handoff type carries a done-definition; The cadence is justified by need, not reassurance; The no-surprise-escalation clause is explicit with the 48h talk first.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

Start a cross-team project with the collaboration contract that prevents the classic collisions — who decides what, how work flows between teams, the communication channels and cadence, and what done means — agreed before the first collision instead of during it. Use when asked kick off this cross-team project right, our two teams keep colliding, define how we'll work with the other team, or set up the partnership before we start. Produces the one-page contract: decision rights, interfaces, cadence, and the done-definition.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The project and the teams — what's being built/done, which teams, their prior history (a scarred partnership needs the contract more and trusts it less — the tone adjusts)

▸The likely decisions — the calls this project will force (scope, priority conflicts, quality bars, launch timing); the table pre-decides the deciders, and the awkward ones ("who wins when priorities conflict?") are exactly the ones to force now

▸The handoff shapes — what actually crosses the seam (designs → build? data → analysis? approvals?); each shape gets its done-definition

▸The leads — the two humans who own the seam; the contract is theirs to sign and theirs to enforce

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The both-teams-assume-they-own decisions were forced and settled

✓Every handoff type carries a done-definition

✓The cadence is justified by need, not reassurance

✓The no-surprise-escalation clause is explicit with the 48h talk first

✓The milestone review is dated

⚠️ What it refuses to do

Do not skip the contract because the teams get along — the contract is *why* they'll keep getting along

Do not leave "who wins priority conflicts" unassigned — that's the fight, pre-scheduled

Do not accept vibe-based done — bounced handoffs are definition gaps wearing quality-complaint costumes

Do not escalate surprises — the 48h clause is the partnership's real load-bearing wall

Do not write three pages — one page gets signed and remembered; three get filed and violated

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="collaboration-contract"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Collaboration Contract is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog