agentleFS
ohanyanohanyan/adulting/skills/screwup/SKILL.md

screwup

Skill1 starsChanged 7 months agoMITView on GitHub

The 4-step protocol for how a grown adult handles a mistake. Acknowledge, repair, change the system, move on. No wallowing, no grandstanding. Usage is /screwup [what happened].

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If missing, ask for a one-sentence description.

    line 16
  2. Distinctive:

    No softening ("Look, I want to say a few words...").

    line 24
  3. Distinctive:

    No PR language ("mistakes were made").

    line 25
  4. Distinctive:

    Ask the user: "Write the acknowledgment sentence.

    line 46
  5. Distinctive:

    Ask the harmed party (or parties) what they need.

    line 50
  6. Distinctive:

    Do not assume. Do not prescribe.

    line 52
  7. Distinctive:

    If you cannot do what they need (you cannot un-send the email, you cannot undo the missed game), do the closest adjacent thing.

    line 62
  8. Distinctive:

    Never apologize for the same thing twice.

    line 93
  9. Distinctive:

    When something breaks, the first word out of your mouth is "Good."

    line 100
  10. Distinctive:

    Add a fifth step: communicate the system change upward and laterally.

    line 135

≈ “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

/screwup

There is a shape to how a mature adult handles a mistake. It is the same shape whether the mistake was small (a missed deadline, a snapped tone) or large (a decision that cost the company money, a lie that damaged trust).

Four steps. In order. No skipping.

Usage

$ARGUMENTS should be the screw-up in one sentence. "Missed my kid's game." "Sent a reactive email to the board." "Forgot our anniversary." "Promised a delivery I can't make."

If missing, ask for a one-sentence description.

Step 1: Acknowledge

Plainly. To the person harmed, or the team, or the room.

Rules:

  • No "but."
  • No softening ("Look, I want to say a few words...").
  • No PR language ("mistakes were made").
  • Short, specific, declarative.

Templates by severity

Small:

"I dropped the ball on [x]. I'm sorry."

Medium:

"I made the wrong call on [x]. Here's what I got wrong: [specific]. I own it."

Large:

"I made a serious mistake. [Specifically what.] The impact is [what]. I am responsible. I am going to make it right in the following ways [...]."

Anti-patterns to avoid

  • "I'm sorry if you were offended." (Not an apology.)
  • "I'm sorry BUT you have to understand..." (Not an apology.)
  • "Mistakes were made." (Grammatical cowardice.)
  • Silence and hoping it blows over. (Does not blow over. Compounds.)

Ask the user: "Write the acknowledgment sentence. Read it back. Is there a 'but' in it? Remove it."

Step 2: Repair

Ask the harmed party (or parties) what they need.

Do not assume. Do not prescribe. Ask.

  • "What would make this right, from your side?"
  • "What do you need from me now?"
  • "Is there anything I can do to repair the specific damage?"

Sometimes the answer is "just don't let it happen again." Sometimes it's concrete (refund a client, redo the work, send a correction to the team). Sometimes it's emotional (time, space, an acknowledgment to a wider group).

Whatever it is: do it. Specifically, within a specific timeframe. No "let me think about it."

If you cannot do what they need (you cannot un-send the email, you cannot undo the missed game), do the closest adjacent thing. And name that you cannot undo it.

Step 3: Change the system

This is the step most people skip.

A mistake repeated is a system failure. If you did it once and apologized, congratulations, you are halfway. If it happens again because you did not change anything, the apology was performance.

Ask the user:

  • What was the system, rule, calendar entry, or habit that let this happen?
  • What structural change will prevent it?

Examples:

  • Missed kid's game? → recurring calendar invite 2 weeks out, travel blackout 48h before, a second-chair designated at work.
  • Sent a reactive email? → 24-hour rule for anything charged, draft folder.
  • Forgot an anniversary? → recurring calendar alert 2 weeks out, another 1 week, another 48h with a specific action (book dinner).
  • Missed a delivery promise? → don't commit to delivery dates without checking capacity, adjust process.

The change must be:

  • Written down.
  • Installed now, not "someday."
  • Communicated to the relevant people.

Step 4: Move on

Do not wallow.

Wallowing is self-indulgent. It centers you (the screwer-up) when the people harmed are the ones who deserve the attention. It also signals to yourself that you are the kind of person who does this, which makes you more likely to do it again.

Two rules:

  1. Never apologize for the same thing twice. Once, cleanly. Then stop.
  2. Shame is not discipline. Action is discipline. Get back to work.

If it haunts you for a week, run /repair with yourself: acknowledge (I did this), repair (I have apologized and changed the system), move on (I am the kind of person who can be trusted now because I own my mistakes, not the kind of person who does not make them).

The Jocko principle

When something breaks, the first word out of your mouth is "Good."

Good, now I know. Good, now I can fix it. Good, now the system is better. Good, now my team has seen me own something, which makes it safer for them to own the next one.

The "Good." reframe is not denial. It is reorientation. From "this is bad, I am bad" to "this is, now what do I do with it."

Output

Append to ~/adulting-data/journal/screwup-log.md:

# <date>

What happened: <...>

## Acknowledgment
Delivered to: <...>
When and how: <...>

## Repair
What they said they needed: <...>
What I did: <...>
By when: <...>

## System change
Root cause: <...>
New system: <...>
Installed on calendar/workflow: <Y/N>

## Move on
I am ready to stop carrying this: <Y/N>

For screw-ups that involved a team or a company

Add a fifth step: communicate the system change upward and laterally.

Nobody trusts a leader who apologizes in private and keeps the fix in their head. If it affected a team, write a short note: "I got X wrong. Here is what happened. Here is what I am changing so it doesn't happen again." Send it.

This is how you become the kind of leader people tell the truth to.

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.