agentleFS
Sign inStart free
AlenroyfeildAlenroyfeild/ai-dev-workspace/skills/handoff/SKILL.md

handoff

Skill0 starsChanged 26 days agoMITView on GitHub

Save verified task progress and an exact next action.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-mapping, setup-ts-deep-modules and 10 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.
  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 93 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 87 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 51 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 54 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Use the user's task ID, or ws brief.

    line 7
  2. Very specific:

    Read back those sections with ws task show and state the saved next action.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 172 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

Use the user's task ID, or ws brief; ask if the task is still ambiguous. Read ws task show <ID> --section "Next action" --section Evidence --section Blockers. From the current session's verified work, run ws checkpoint <ID> --status <current-status> --next "<exact unfinished step>" --note "Evidence=<checklist items below>" --note "Blockers=<blockers or None>". If an approach was tried and failed or was rejected this session, add --note "Do not redo=<approach: why it failed>" so the next session, in any assistant, skips it. Preserve still-relevant evidence; never invent checks or include secrets/private identifiers.

In the Evidence note, record verified progress using this handoff checklist:

  • working tree: git status -sb and unpushed commits
  • branch/PR and CI status if known
  • running processes: dev servers, background processes, or tmux sessions, with attach or inspection commands
  • checks run and exact results (pass/fail counts or test names)
  • risks: remaining uncertainties, fragile assumptions, or known failure modes

Read back those sections with ws task show and state the saved next action. This saves workspace memory only; do not commit or push.

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