agentleFS
erikperttuerikperttu/steering-coding-agents/.claude/skills/handoff-update/SKILL.md

handoff-update

Skill1 starsChanged 5 months agoMITView on GitHub

Close out a work session cleanly. Fold "what we did" into the history, prune the forward worklist against the mechanical rule, migrate any closed backlog items, and run the rotation check. Invoke at the end of a session before context is lost.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. furenzhong/awoo-vibe-coding-governance★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Very specific:

    Write a new ## Session <N> (<date>): <theme> block at the top of SESSION_HISTORY.md, following the template: theme, built/changed, …

    line 31
  2. Very specific:

    Run scripts/archive_rotate.py.

    line 50
  3. Distinctive:

    No closed items remain in the live backlog.

    line 58

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

Handoff Update

The session-close routine that keeps the three handoff documents from rotting. Run it at the end of a session. The point is to make a good handoff the path of least resistance: you do the thinking, the skill does the mechanical bookkeeping.

Not Claude-specific. This is packaged as a Claude Code skill, but the routine is just four steps. In any other setup it's a slash command, a make handoff, or a script you run by hand. Nothing below depends on Claude, so adapt the invocation and keep the steps.

Run it as the last thing before you shut down

This is the session-close checkpoint, the last thing you do before closing the terminal or editor. It is the natural place to hang the rest of your closing ritual: run the full test suite, the linter, a type check, regenerate any derived docs, whatever your project gates on before a session counts as done. The four steps below are the documentation side of the close; pair them with your own checks so you leave the project green and the handoff clean in one pass. If you skip it, the next session starts blind.

What this skill does NOT touch

It does not change project code. It only edits the three handoff documents and their archives.

Steps

1. Fold "what we did" into the history

Write a new ## Session <N> (<date>): <theme> block at the top of SESSION_HISTORY.md, following the template: theme, built/changed, what-it-proves, carry-forward. This is where all past-tense narrative goes. Everything you were tempted to write into the worklist during the session belongs here.

2. Prune the forward worklist against the rule

Open CONTINUE_FROM_HERE.md and apply the mechanical rule to every bullet under Current state: if a bullet contains a session marker (a session number, a date, a run id) or a closure verb (closed, done, landed, fixed, added, re-proven), it is a changelog entry, not a worklist entry.

For each offending bullet, either delete it (the narrative is now in the history) or rewrite it as the present-tense fact (keep only the live consequence, drop how it got there). Then update the Next-session priority list to reflect what's actually next, and refresh the _Last updated_ line.

3. Migrate closed backlog items

For each row in ARCHITECTURE_GAPS.md whose status reached done this session, move the row out to ARCHITECTURE_GAPS_CLOSED.md (with a one-line note on how it closed). The live backlog must only ever contain open, in-progress, or deferred work. Check that no row left in ARCHITECTURE_GAPS.md carries a closure marker.

4. Run the rotation check

Run scripts/archive_rotate.py. If SESSION_HISTORY.md or ARCHITECTURE_GAPS_CLOSED.md crossed its size threshold, it peels the oldest block into a numbered archive and leaves a pointer behind. This keeps the files the next session loads small; their length should track what's live, not what's total.

Done when

  • A new history block exists for this session.
  • The worklist passes the rule (no changelog bullets) and its next-priority list is current.
  • No closed items remain in the live backlog.
  • The rotation check has run.

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.