agentleFS
Sign inStart free
BuddhiliveBuddhilive/buddhi-cli/.agents/skills/handoff-spec/SKILL.md

handoff-spec

Skill1 starsChanged 15 days agoMITView on GitHub

Hand a spec that is mid-implementation to another machine or another agent.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-spec-with-codex, audit-decisions and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    implement-spec-with-codex

    Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.

    Also in 4 projects that use this

  • wolverin0Skill

    audit-decisions

    Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

    Also in 4 projects that use this

  • dzhngSkill

    port-features

    Port a feature from an existing repository by copying its actual code and editing the copy, so its bug fixes and behavioral nuances survive, then naturalizing it to this project's names and environment. Use when asked to copy or port an existing feature (especially an exact copy), when moving one into a different framework or host, or when a previous reimplementation missed upstream behavior.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Leave the spec so that session can carry on as if it had been here.

    line 12
  2. Distinctive:

    Write it into the spec's own handoff, in place: the spec stays one current account, not a transcript with a new note on top.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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 Spec

I'm moving this spec's work to another machine or another agent. The next session starts cold: it has the repository and nothing else. It has none of this conversation, none of this machine's files and none of your memory. Leave the spec so that session can carry on as if it had been here.

Collect what this session knows and the spec doesn't yet say, from the discussion and from the work itself, and put it in the spec:

  • what is done, what is half-done and exactly where it stopped, and what is next;
  • what I decided or corrected along the way, and how I want the work done;
  • calls you made where I was silent, and anything still waiting on me;
  • what is known to be broken or unverified, with what you already found out about it;
  • anything that lives only on this machine and the next session needs: unpushed branches, uncommitted work, scratch results worth keeping.

Write it into the spec's own handoff, in place: the spec stays one current account, not a transcript with a new note on top. Then push, so everything the spec points at exists on the remote.

Done when a fresh agent, given only the repository, would pick the same next step you would, and would not repeat a question I've already answered.

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.

Check your setup, free