# Frac Team Interface Agreement

> Drafts a one-page agreement between a fractional leader and the people who carry the function on the off days, with what a complete request looks like, who decides what without you, the response window, the urgent route, a shared status view, and a one-cycle trial with a review date. Use for "run frac-team-interface-agreement", "work stops when I am not there", "working agreement with the team", "how does the team reach me on my off days", "who decides when I am with another client", "interface agreement for my fractional role", "requests keep coming back incomplete", part of the Claude for Fractional Leaders Pack by 90n.

- Skill: `polar-bear-org/frac-team-interface-agreement` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/frac-team-interface-agreement`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/frac-team-interface-agreement/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-team-interface-agreement

---


# Team Interface Agreement

## When To Use
Work stops on the days you are with another client. A request waits three days for your approval, a brief comes back twice because it was half complete, and the team lead does not know which calls are theirs to make. This answers: how does one piece of work travel from request to done when you are only there part of the week?

## When Not To Use
If the rules to settle are between you and the CEO (your decision rights, your days), run Engagement Charter. If the trouble is one broken commitment with one person, run Relationship Repair Plan; a process page will not mend it.

## Inputs
- One real recent item that stalled or bounced: what was asked, by whom, when, and what happened at each step
- The charter's decision-rights lists and your days for this client
- The tools the team already uses to track work
If you have none of this, I start from the type of request that stalls most often, and mark the page as a first draft to test on one real item.

## Approach
An interface agreement, a practitioner convention: follow one real item from request to acceptance, see where it waited and why, and agree the few rules that would have let it move. The judgment is to agree it with the team, not hand it down, and to try it for one cycle before calling it settled. The failure this prevents is the part-time bottleneck: a function that runs at the speed of your calendar, and a team that learns to wait.

## Workflow
1. Ask at most three questions: which item should we trace; who carries the function day to day when you are away; what do they already decide alone?
2. Trace the item step by step: asked, received, clarified, decided, done, accepted. Mark where it waited, for whom, and whether authority was assumed or confirmed.
3. Define a complete request: the minimum someone must give you so you can decide in one pass, and what you return when it is incomplete (a question or a "not yet" with the reason, the same day you see it).
4. Write who decides what without you, taken from the charter's lists and extended only with the CEO's agreement. Silence from you is not approval unless you both wrote that it is, for a named kind of decision.
5. Set the response window for your off days and the urgent route, with what counts as urgent, and a shared status view with the fewest fields that work (item, owner, waiting on, since when).
6. Agree a trial of one work cycle and a review date. At the review both sides say what got faster, what got heavier, and what to change.

## Output Format
```markdown
# Team Interface Agreement
Client: [name] · Between: [you] and [team lead and team, by role] · Trial: [dates] · Review: [date]
## The item we traced
| Step | Date | Waited on | Why |
|---|---|---|---|
| [asked / received / clarified / decided / done / accepted] | [date] | [role] | [missing input / unclear authority / off day] |
## A complete request
A request is complete when it has: [fields]. If it is not, I reply with [question or "not yet" and the reason] within [window].
## Who decides without me
| Kind of decision | Decided by | Tell me after? |
|---|---|---|
| [decision] | [role] | [yes, in the status view / no] |
## Reaching me
My days: [days] · Other days: replies within [your window] by [channel] · Urgent: [route], for [what counts as urgent]
## Shared status view
[Where it lives] · Fields: item, owner, waiting on, since when
## Decision
[Team lead] and [you] agree the trial by [date]; [CEO] confirms any decision right added beyond the charter.
```

## Done When
- One real item has been traced, with every wait explained
- A complete request is defined in fields someone can check
- Every decision the team takes alone is listed, with nothing beyond the charter unconfirmed
- There is a trial period and a review date

## Quality Bar
- The page describes how work moves, never who is slow
- An incomplete request can be returned without it being personal
- Response windows fit the days you really have; none is promised for another person
- It is agreed with the team and amended together after the trial
- Claude drafts from the item you give it, invents no step or delay, uses nothing from another client's team, and you agree the page with the team yourself

## Next
Run frac-relationship-repair-plan (Relationship Repair Plan) if tracing the item showed a commitment that one of you broke.

## 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).

