agentleFS
scottcrosby-securebinescottcrosby-securebine/doctrine-skills/skills/doctrine-handoff/SKILL.md

doctrine-handoff

Skill0 starsChanged 9 days agoMITView on GitHub

Use when the user asks for a handoff document, "a detailed backup and a handoff so I can clear the session", or anything that carries this session's detail to the next cleared session. Writes a new file under docs/handoffs/ tied to the plan, then runs doctrine-backup so the memory file points at it and both are red-teamed.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the handoff: the verbose, tactical slice of the plan that carries this session's detail to the next cleared session.

    line 8
  2. Very specific:

    Run doctrine-backup step 0 before writing anything, so the predecessor this file supersedes is already at its standard path.

    line 15
  3. Very specific:

    Check your host's user skill directory, then the project's, for handoff/SKILL.md (the hub's host reference names both).

    line 20
  4. Distinctive:

    When neither path exists, say so once and continue:

    line 27
  5. Very specific:

    When the record the header names is on this host and has no wrapper: line (any case), append wrapper: <skill name> as the record's last …

    line 52
  6. Very specific:

    Run doctrine-backup from its step 1, unless this handoff was written from inside a backup, which then continues on its own.

    line 98

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

Doctrine Handoff

Write the handoff: the verbose, tactical slice of the plan that carries this session's detail to the next cleared session. The memory file is context; this is where the detail lives, organized under the plan it serves. In a repo a doctrine project file tracks, the plan is that project: the epic, its Done means items, the phase. In a repo with none, it is the repo's GitHub issues and the task at hand.

1. Conform first

Run doctrine-backup step 0 before writing anything, so the predecessor this file supersedes is already at its standard path.

2. Content rules

Check your host's user skill directory, then the project's, for handoff/SKILL.md (the hub's host reference names both). Read the first that exists and apply its content rules: reference specs, plans, issues and commits by path or number instead of restating them, and name the skills the next session should invoke. Take only its content discipline; its storage instruction (a scratch file in the OS temp directory) does not apply, since this file lives in docs/handoffs/. Pointing at that skill rather than copying it means its improvements land here.

When neither path exists, say so once and continue:

No handoff skill installed; writing the handoff without it. Source: mattpocock/skills → skills/productivity/handoff/SKILL.md.

3. Write the file

One file at docs/handoffs/<YYYY-MM-DD>-<slug>.md, where <slug> names the piece of work. A new file every time this skill runs, even when one was written earlier today, beside the previous one and never overwriting: when the name is taken, append -2, -3. No earlier handoff is edited.

Header lines, the first lines of the file, above its title:

  • supersedes: <path>: resolved before you create this file, the current handoff as doctrine-backup step 3 defines it, else none. It is never this file. Never the newest file in the directory, which on a clone is any of them.
  • Then whatever header lines the skill that owns the work requires. A doctrine phase's are given in doctrine step 5; carry them in full, each on its own line, and never fold one into another: the phase: line, the record: line, the wrapper: line (the record's last wrapper: line; only where the record has none, the source order the next bullet gives), and the invoke doctrine:doctrine first line while the phase is Open or Blocked. A handoff written from inside doctrine-backup carries the same four. When that skill is not loaded this session, copy the previous handoff's header lines below supersedes: forward, so the record's path stays in the chain, and refresh the state header, the quoted record state line with its line number, and the wrapper: line from the record itself; when the record is not on this host, suffix the quoted line with "(copied from <previous handoff>; record not found <today>)".
  • When the record the header names is on this host and has no wrapper: line (any case), append wrapper: <skill name> as the record's last line, before you quote its state line: a record is appended to and never edited (doctrine step 5), so nothing above it moves, and the last wrapper line is the one read (doctrine step 1). Name the wrapper the phase runs under, taken from the record's own title line, else from the handoff this one supersedes (its wrapper: line, else the wrapper its phase: line names), else the doctrine-* wrapper this session invoked for the phase, else none. Write the name without a doctrine: prefix, carry the same line in this header, and say in your report that you appended it to the record.

Sections, in this order and no others:

  1. State in one paragraph: where the work stands, what is live, the immediate next step.
  2. Where this sits in the plan. In a tracked repo: the project file's path, the epic, each Done means item in play with its obligation exactly as the epic record states it (satisfy, contribute or preserve), the phase and its record's path, and the GitHub issues this work touches, each with the plan item it serves or "none". A plan item here is a Done means item, never the phase or the epic that holds it. In a repo with no project file: the GitHub issues this work touches, or that none do.
  3. Read these, in this order: each by repo path, never "the newest file in a directory". Every path must exist.
  4. Work by plan item: one heading for each plan item or issue this work serves, and one heading, "Serves no plan item", for whatever serves none. Every task and issue this handoff names appears under exactly one of them by its name or number, one line each, with its status and a pointer to where the detail lives: an issue, the record's line, a spec section. The heading is the item it serves, and an issue section 2 ties to an item goes under that item. Neither its status nor what kind of problem the line records moves it: an issue closed or merged, a discrepancy between the record and the tree, and a check still owed all stay under the item served. Carry the detail here: the reasoning, the dead ends, what was tried and why it failed. This is what survives the clear.
  5. Do this first: exactly one action, the first the next session takes, in one sentence with one thing to do. Two things joined by "then", "and" or "before" are two actions, and so is an action and its precondition: the precondition is the first action. Everything else due goes in section 4.
  6. Gotchas this phase produced: the ones the memory file will not carry, including any true Gotcha its cap moved here.
  7. Suggested skills: which to invoke, and which first.

This document is as long as the next session needs; the memory file's word target does not apply. Rules, each one a failure found in a live repo:

  • Reference, never duplicate what already lives elsewhere. Cite code by symbol, not line number.
  • No scratchpad path and no plugin-cache version path (<plugin-cache>/<x>/1.53.0/...): the first dies on a bounce, the second on the next version bump, and both were found dead in committed files.

4. Finish with a backup

Run doctrine-backup from its step 1, unless this handoff was written from inside a backup, which then continues on its own. Its kickoff then names the file you wrote, its red-team seat checks this handoff beside the memory file, and its commit lands both. A handoff is not done until that backup is.

Done when

The handoff is written at a new path under docs/handoffs/, the memory file's kickoff names it, the red team's findings are fixed or rejected with a reason, and both files are committed or reported local and ignored.

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.