# Frac Relationship Repair Plan

> Prepares a repair plan after a missed commitment between a fractional leader and a peer, with facts against accounts against open questions, a short acknowledgment of the specific action and its effect, remedies within your authority, one prevention change with an owner, and a follow-up the other person can decline. Use for "run frac-relationship-repair-plan", "I missed a commitment to a colleague at my client", "repair a working relationship", "how do I apologise to a peer", "the work has gone cold with the finance lead", "they let me down and I need to raise it", "prepare a difficult conversation after a broken promise", part of the Claude for Fractional Leaders Pack by 90n.

- Skill: `polar-bear-org/frac-relationship-repair-plan` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/frac-relationship-repair-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/frac-relationship-repair-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/frac-relationship-repair-plan

---


# Relationship Repair Plan

## When To Use
You missed a commitment to a peer on the leadership team, or they to you, and the work has gone cold. Replies are slower, a meeting was skipped, and you are in the building too rarely for it to mend by itself. This answers: what happened in fact, what do I own, and what do I offer?

## When Not To Use
If the problem is a recurring handoff and nobody broke a promise, run Team Interface Agreement. If what happened looks like serious misconduct, harassment or retaliation, stop: that goes to the CEO or the client's proper channel, not into a repair conversation.

## Inputs
- What was committed, by whom, by when, and what happened, with messages or notes if you have them
- The effect on the other person or their team, as far as you know it, and their account if they have given one
- What you are able to offer within your role at this client
If you have none of this, I start from your own account, mark it as one side only and mark the plan as a first draft.

## Approach
The components of an effective apology studied by Lewicki, Polin and Lount (Negotiation and Conflict Management Research, 2016), as summarised by Ohio State News: of six elements, acknowledging responsibility and offering repair mattered most to readers, and asking for forgiveness mattered least. The studies used written scenarios, so this is guidance on what to include, not a promise about the result. The failure this prevents is the explanation dressed as an apology, three paragraphs of context about your other clients in which the words "I did not do what I said" never appear.

## Workflow
1. Ask at most three questions: what exactly was committed and what happened; what did it cost the other person; what is in your power to put right?
2. Sort what you have into three columns: established facts, accounts (yours and theirs, each labelled), open questions. Nothing moves from account to fact without a source.
3. If the commitment was yours, draft the acknowledgment: the specific action, its effect on them, and the responsibility taken in plain words. Context may follow in one sentence; it never comes first, and "I was at another client" is context, not a reason.
4. If the commitment was theirs, draft the opening instead: what was agreed, what happened, the effect on the work, and a question. No verdict on why.
5. List the remedies within your authority, and one prevention change that addresses the cause, with an owner and how you will both know it is done.
6. Offer one follow-up, with the choice of whether and how left to them. No request for forgiveness, no condition, no deadline for things to feel normal. You have the conversation yourself, in person or on a call.

## Output Format
```markdown
# Relationship Repair Plan
Client: [name] · With: [role] · The commitment: [what, by whom, by when]
## What we know
| Established facts (source) | Accounts (whose) | Open questions |
|---|---|---|
| [fact, message or record] | [my account / their account] | [what to ask] |
## What I will say
[If mine: the specific action, its effect, responsibility taken · If theirs: what was agreed, what happened, the effect, a question]
## Remedies within my authority
- [remedy] · by [date]
## One prevention change
| Change | Addresses which cause | Owner | Done when |
|---|---|---|---|
| [change] | [cause] | [owner] | [observable condition] |
## Follow-up
[What you offer] · Their choice: [whether, when, how]
## Decision
[You] decide by [date] when and where to have the conversation, and have it yourself.
```

## Done When
- Facts, accounts and open questions are separate
- The acknowledgment names the action and its effect before any context
- Every remedy is within your authority at this client
- The prevention change has an owner and an observable end

## Quality Bar
- No admission is invented and no known fact is blurred
- Nothing is said about the other person's character or motives
- No demand for forgiveness, a good word to the CEO or a quick return to normal
- The plan does not promise the relationship will recover
- Claude works only from what you give it about this client, and you have the conversation yourself; nothing is sent for you

## Next
Run frac-decision-brief (Decision Brief) if the cold spell hid a question the leadership team never framed.

## About the makers

This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

