Write the band agreement before the money or the breakup arrives — who owns the songs, how money splits (writing vs performing distinguished), who owns the name, what happens when someone quits, and the decision rules for offers — decided while everyone still shares a van. Use when a band asks 'how should we split money', 'who owns our songs', 'our drummer quit, what happens', or is about to record/release/sign anything. Produces a plain-language band agreement and the meeting script to agree it. Not legal advice — it's the conversation that makes the lawyer cheap later.
“How should we split money?”“Who owns our songs?”“Our drummer quit.”“What happens?”
What to give it
▸The band — members, roles (who writes? who books? who fronts money?), how long together, what's released already
▸The current reality of songs — who's been writing, how arrangements happen, anything already registered anywhere
▸Money so far — gig fees, who's owed for gear/van/recording fronted
▸Any storm clouds already visible — (the member half-out, the founder possessive of the name) — the agreement is written toward the real band, not the ideal one
✅ 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.
✓Writing and recording rights are decided separately and explicitly
✓The name section answers the leaving-case by name
✓Fronted money (gear, van, recording) is logged with a repayment
✓rule
✓Every section is a decision — zero "the band will discuss"
✓placeholders
✓The not-legal-advice line and the lawyer triggers are present;
✓society/registration mechanics are flagged, not asserted
⚠️ What it refuses to do
Do not default everything to equal-split without showing what
equal costs the writers (or writer-split costs the arrangers) —
informed beats harmonious-for-now
Do not write the founder's name-ownership in by assumption —
it's the menu's most contested item; make it explicit either way
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 -p pm-claude-skills pm-claude-skills-mcp