# Handoffs

A note at the end of every task, so the next person or agent continues it instead of starting over.

This is a recipe from flie: a person can read it first, and an agent follows
it. It makes one folder in the person's flie, with a README in it that holds
the rules, so every agent that opens the folder later works the same way.

## 1. Make sure flie is set up

If the `flie` command is not found or `flie whoami` says nobody is signed in,
and you have no flie tools over MCP, set flie up first, with the person's
authorization, by following https://flie.sh/setup.md
Then come back here.

The steps below are `flie` commands. Over MCP, call the tools of the same
names, with the same arguments written as named arguments, and pass a file's
text as `content` instead of `--from`.

## 2. Make the folder

`flie whoami` prints the person's Root folder. Make the folder there unless
the person names another place. If a folder called "Handoffs" is already
there (`flie agent list <root ID>`), use it: read its README and follow it
instead of starting again.

    flie agent mkdir <root ID> "Handoffs"

Each command prints the new item's name and its ID; every later command names
the item by that ID. Laid out, the folder is:

    Handoffs/
      README.md                       the rules
      2026-09-30 short task name.md   one note per task

## 3. Write the README, then start

Write this README into the folder, adapted where the person says so, with the
text on stdin:

    flie agent create --from - <folder ID> "README.md"

~~~markdown
# Handoffs

One note per task, so whoever picks the work up next, a person or an agent,
continues it instead of starting over.

## A note

Name it "<date> <short task name>.md", for example "2026-09-30 pricing page.md".

    # Pricing page
    Asked: what the person wanted, in their words where you have them.
    Done: what is finished and how you know (tests run, pages checked).
    Next: the very next step, and anything blocking it.
    Where: the branch, the files, the commands to rerun.

## When to write one

- When you finish a task, or stop partway through one.
- When you continue a task that already has a note, update that note instead
  of writing a new one. Every earlier version is kept.
- When you start work, read the newest notes here first.
~~~

Write the first note now, for the task in front of you.

## 4. Add one line to the repository

Add this line to the repository's AGENTS.md, or to CLAUDE.md if that is the
file it has, with the folder's real ID in place of fld_…:

    When you start, read the newest notes in the flie folder "Handoffs" (fld_…); when you finish or stop, leave one there, following its README.

If it has neither, create AGENTS.md with just this line. Tell the person, since
the change is theirs to commit.

## Done

Tell the person what you made and give them the folder's link
(`flie agent link <folder ID>`).
Editing its README changes the rules for every agent that reads it. How to
change a file without losing anyone's edits: https://flie.sh/skill.md.
