# The /phoenix-protocol Skill

> Get your days back after a breakup, a lost job or burnout. Start today with one small action and an evening check-in. The plan grows only when a real week shows it can, and a missed day never means catching up.

- Category: Daily rhythm
- Status: Experimental
- Version: 0.1.1
- License: MIT
- Updated: 19 Nov 2026
- Source: https://github.com/tsirbiladze/phoenix-protocol
- Full SKILL.md: https://github.com/tsirbiladze/phoenix-protocol/blob/v0.1.1/skills/phoenix-protocol/SKILL.md
- Page: https://tsirbiladze.com/skills/phoenix-protocol
- Georgian version: https://tsirbiladze.com/ka/skills/phoenix-protocol.md

## Install

### Agent skill

```bash
npx skills@latest add tsirbiladze/phoenix-protocol
```

For agents that work with files on your computer and run Python 3.9 or newer; rehearsed in Claude Code and Codex. Then ask: “Help me get back on track.”

### Claude Code

```text
/plugin marketplace add tsirbiladze/phoenix-protocol
```

```text
/plugin install phoenix-protocol@phoenix-protocol
```

Run both in Claude Code.

## What it does

`phoenix-protocol` helps you rebuild your daily rhythm after a hard stretch. You answer a few questions, one at a time, and choose one small action for every day, the anchor: something like "when I get up → I walk for 10 minutes". The same evening, your agent checks in with you for the first time. From then on it comes by every evening for two to five minutes: what got done, one optional question, and tomorrow's first step.

Most plans are made for the perfect day. This one is made for the day after you fail. A bad day has a shorter version that still counts: the minimal day. A missed day is not a debt, so tomorrow is a normal day, not a double one. After two heavy days in a row, the next day becomes a minimal day by itself. After three days of silence, your agent welcomes you back with no numbers and no questions about where you were. And there is no "from Monday": the next step is always in the next hour.

The plan grows only when a real week shows it can. A week at 80% or more adds one item. A week under 50% makes the next one a level lighter, and it never drops back to zero. A script does every count, so the numbers are honest and come out the same every time.

![The dashboard of a fictional person: the week's score on a dial, days kept and returns, a ring of the cycle's twelve weeks, a map of the days, and today's plan](https://tsirbiladze.com/skills/phoenix-protocol/dashboard.png)

## When to reach for it

Ask your agent in plain words: "help me get back on track after my breakup", "I lost my job and my days are falling apart". Later, just "check-in" or "weekly review".

| You want | The skill gives you |
|---|---|
| To start without a big plan | One anchor action and an evening check-in, from today |
| Out of the all-or-nothing loop | A minimal day for bad days, with no catching up and no restarts |
| To see that you are coming back | A dashboard: the week's score, the days kept, the returns, a map of the cycle |
| The urge to text or check on someone to pass | The impulse pause: 48 hours, and an unsent text kept outside git (you turn it on) |
| Worries out of the rest of your day | A worry window: 15 minutes at a set time (you turn it on) |
| New ideas without losing the thread | An idea bank: one idea a cycle, 4 hours a week, after a strong week (you turn it on) |

It is not therapy and not a crisis service. If you are in crisis right now, please call your local emergency number or a crisis line first.

## After a miss

This is the heart of the skill. Every answer has the same shape: one accepting line, then one small action.

| What happened | What your agent does |
|---|---|
| Part of the day, or one missed day | Nothing changes. Tomorrow is a normal day, not a double one. |
| The check-in didn't happen | The day is "not logged yet", not missed. Next time you fill it in with one tap. After 48 hours it counts as missed, and that is all it means. |
| Two heavy days in a row | The next day is a minimal day, as the plan, not as a penalty. |
| Three days or more of silence | A welcome back with no numbers. Today is just the minimal day. |
| A week under 50% | The next week is a level lighter. Nothing is deleted, and nothing goes back to zero. |
| "I'll start properly on Monday" | Monday is for looking back. The next step is in the next hour. |

On the dashboard, what counts most is not the chain but the **returns**: how many times you came back after a miss. You can hide the chain altogether.

## Safety

- At the start of every session, your agent says in one line that it is an AI helper for rhythm, not a therapist and not an emergency service.
- Signs of a crisis stop the routine. Your agent asks one plain question and gives a crisis line for your country, from a small table checked against official sources and dated, never from memory. When the danger is immediate, the emergency number comes first.
- Some things it refuses: tracking a person, winning someone back by pressure, and contact after a block or a request for no contact, a "last apology" included.
- No diagnosis, no companion persona, short sessions. The minimal day always holds one real conversation with a person.
- For Georgia, no general psychological crisis line could be confirmed. The table holds 112 and 116 006 (violence against women and domestic violence, 24/7), and says so.

## Your data

Your plan is a folder on your computer of plain files: JSON, CSV and Markdown. Git keeps a local history if you want one. The skill never adds a remote or pushes on its own. Unsent texts and parked worries stay in a `private/` folder outside git. Other people appear by role, never by name, and nothing about your health is written down. What you write to your agent goes to the model provider like any chat.

## How the check-in reaches you

In Claude Code's desktop app, Codex in the ChatGPT desktop app and T3 Code, your agent can set a scheduled task that starts the evening check-in by itself, as long as the app is running and the computer is awake. Everywhere else, the skill makes a calendar file for your phone with a daily reminder. If an evening is missed, the next session asks about that day first.

## Limits

- Version 1 is for coding agents that work with files on your computer and can run Python 3.9 or newer. claude.ai and ChatGPT keep no folder between sessions.
- Your agent speaks your language. The plan file and the dashboard are in English or Georgian.
- One person per folder. Not for anyone under 18.
- The 80% and 50% thresholds and the 12-week cycle are conventions, not findings, and you can change them.

## The research behind it

Each lever has research behind it. Their combination is a hypothesis that no study has tested.

- Plans in the form "when X, then Y" help people act on their goals ([Sheeran et al. 2024](https://doi.org/10.1080/10463283.2024.2334563)).
- Tracking progress helps, more so when it is written down or reported ([Harkin et al. 2016](https://pubmed.ncbi.nlm.nih.gov/26479070/)).
- A planned fallback keeps people going after a slip ([Sharif & Shu 2021](https://doi.org/10.1016/j.obhdp.2019.01.004)). A broken streak lowers engagement, and a way to repair it softens that ([Silverman & Barasch 2023](https://doi.org/10.1093/jcr/ucac029)).
- One missed day does not materially affect forming a habit ([Lally et al. 2010](https://doi.org/10.1002/ejsp.674)).
- Waiting for a fresh start lowers effort before it arrives ([Koo et al. 2020](https://doi.org/10.1016/j.obhdp.2020.06.002)).
- After a separation, writing about it in depth slowed recovery for some people ([Sbarra et al. 2013](https://doi.org/10.1177/2167702612469801)), so reflection here is short and optional.

The full notes and sources: [docs/research.md](https://github.com/tsirbiladze/phoenix-protocol/blob/v0.1.1/docs/research.md).

## Changelog

### 0.1.1 (19 Nov 2026)

- `SKILL.md` failed to parse as YAML: its description holds a colon, and strict parsers stop at it. `npx skills add` skipped the skill and installed nothing. The description is now quoted, word for word the same, and a test holds every frontmatter to strict YAML.
- The skill's page on tsirbiladze.com names the job in search results and shares: "Get back on track after a breakup or burnout" (`searchTitle` in both page texts). The page's heading stays "The /phoenix-protocol Skill".

### 0.1.0 (19 Nov 2026)

First release.

- The skill: a ten-minute start that ends in a first check-in the same evening, evening check-ins, the after-miss ladder, weekly reviews and cycle reviews, with a condition that says when each is done.
- `phoenix.py` computes every number: day statuses (full, minimal, partial, missed, not logged yet), a 48-hour window to fill in a day, the week score, levels 1 to 3 (80% up, 50% down, never below level 1, never down in week zero), returns, the chain, and today's mode (normal, minimal by rule, return).
- The dashboard: one self-contained HTML file in English or Georgian, light and dark.
- Calendar reminders as an `.ics` file. Recipes for scheduled check-ins in the agents that support them.
- The safety layer: a disclosure line in every session, crisis signs that stop the routine, a dated table of crisis lines checked against official sources, red lines, and rules against dependence.
- Opt-in modules: the impulse pause, the worry window, the idea bank.
