agentleFS
ohanyanohanyan/adulting/skills/partner-checkin/SKILL.md

partner-checkin

Skill1 starsChanged 7 months agoMITView on GitHub

Weekly dedicated partner check-in (30 minutes, same time, phones away). Based on Gottman's stress-reducing conversation + Brené Brown rumble language. Protects the single highest-leverage relationship ritual there is.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not in bed. Somewhere you sit up.

    line 17
  2. Distinctive:

    No problem-solving. No advice.

    line 34
  3. Distinctive:

    No defense. No explanation.

    line 57
  4. Very specific:

    If yes, use Brené's rumble language: "The story I'm telling myself is..." Speak from the story, not the accusation.

    line 63
  5. Distinctive:

    Write it down. Put it on the calendar if it needs a calendar.

    line 69
  6. Very specific:

    After the check-in, optionally log to ~/adulting-data/journal/partner-checkin-YYYY-MM-DD.md:

    line 81
  7. Distinctive:

    If they say no, ask what version they would say yes to.

    line 111

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/partner-checkin

The research is unambiguous. Gottman's 40+ years of couples work lands on one pattern: couples who thrive have structured weekly contact that is not about logistics. Not kids, not calendar, not groceries. Them.

This is that ritual.

Setup

  • 30 minutes minimum, ideally 45.
  • Same day and time each week if possible. Friday night, Sunday morning, whatever is yours.
  • Phones off or in another room. Not face-down. Away.
  • Not in bed. Somewhere you sit up.
  • Drinks are fine. Screens are not.

The structure

1. Appreciation (2 minutes)

Each of you shares one specific appreciation from the week. "Thank you for handling bath time Tuesday when I was on that call. I know it wasn't your turn."

Specific beats general. Behavior beats trait. ("You are a great partner" is worse than "You picked up the dry cleaning without me asking.")

2. High of the week, low of the week (5-10 minutes)

Each of you, in turn, shares:

  • The high.
  • The low.

No problem-solving. No advice. The other person says something like: "That sounds heavy. Tell me more."

3. What are you carrying? (5-10 minutes)

The real question. Ask:

"What is on your mind this week that I might not know about? Work, family, friends, health, the kids, us. Anything."

Listen without responding. When they finish, use Kate Murphy's support response: stay with their content. Do not shift to your content. Ask one curiosity question: "What was that like?" or "What do you make of that?"

Then they ask you the same question. You answer.

4. Us (5-10 minutes)

Two questions, taken seriously:

  • "What did I do this week that made you feel loved?"
  • "What did I miss?"

The "miss" question is the one most couples skip. It is the one that matters most. It should be answered with one specific thing, not a list of grievances. "When I came home Wednesday and you were on your phone for the first 10 minutes, that felt like I didn't matter."

The receiver's only response is: "Thank you for telling me. I hear you. I'm sorry. How can I repair that?"

No defense. No explanation. No "but."

5. Anything unsaid (3 minutes)

"Is there anything between us right now that we haven't named?"

If yes, use Brené's rumble language: "The story I'm telling myself is..." Speak from the story, not the accusation. If it needs more than 10 minutes, schedule a dedicated time and use /hard-conversation.

6. One thing for this week (2 minutes)

Each of you names one thing you will do for the other this week. In their love language (see /love-map-refresh).

Write it down. Put it on the calendar if it needs a calendar.

7. Close

A 20-second hug. Not a side hug. A real one.

The rule about logistics

Logistics can have 10 minutes at the END if needed. Never the start. Never the whole check-in. If logistics try to eat the slot, stop, and schedule a separate 15-minute "ops meeting" for the week.

Output

After the check-in, optionally log to ~/adulting-data/journal/partner-checkin-YYYY-MM-DD.md:

# Partner check-in — <date>

## Appreciations
Mine: <...>
Theirs: <...>

## Carried this week
Mine: <...>
Theirs: <...>

## The miss
What they said I missed: <...>
My repair: <...>

## This week for them
<specific action, day>

## Unsaid
<anything parked for later>

This journal is private. Never share it without their consent.

Before the first one

If you have never done this and your partner might think it's weird, don't spring it. Tell them: "I want to try something. A weekly 30-minute sit-down where we actually talk about us. No phones, no logistics. Would you be up for trying it for a month?"

If they say no, ask what version they would say yes to. Meet them there.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.