agentleFS
anurag-rivoraanurag-rivora/product-brain-starter/.claude/skills/write-handoff/SKILL.md

write-handoff

Skill1 starsChanged 4 days agoMITView on GitHub

Build features/<slug>/handoff.md for a coding agent from approved steps and approved brain entries only. Use when someone says "write the handoff" or "hand this to the coding agent".

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    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:

    Ask which feature (features/<slug>/).

    line 12
  2. Distinctive:

    Read only the approved steps.

    line 14
  3. Very specific:

    Write features/<slug>/handoff.md using features/_template/handoff.md:

    line 16
  4. Distinctive:

    Add the date and the list of approved steps used at the top.

    line 24

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

Write handoff

Builds a frozen bundle from approved work. Drafts are left out.

How to run it

  1. Ask which feature (features/<slug>/). Read brief.md and its steps table.
  2. List the steps marked approved and the steps marked not needed (with reasons). If the implementation plan (08) is not approved, stop and say so.
  3. Read only the approved steps. Ignore any step marked draft or not started.
  4. Collect the entry IDs those steps cite. Open each one in brain/ and keep only entries with status: approved. If a cited entry is now replaced or stopped, stop and tell the person.
  5. Write features/<slug>/handoff.md using features/_template/handoff.md:
    • Objective: two sentences, from the approved executive summary (01).
    • Plan: from the approved plan, in order, with where to look first.
    • Rules that apply: each approved rule in full, with ID and severity.
    • Decisions that apply: ID plus one line each.
    • Open questions: id, question, blocking level and owner. Blocking ones go first.
    • Steps not needed, with reasons.
    • End with "Stop and ask if unsure".
  6. Add the date and the list of approved steps used at the top.
  7. Tell the person where the file is, and which steps and entries went in. Remind them the PR template asks which entries the change touched.

Do not

  • Include draft steps, proposed entries or anything in brain/inbox/.
  • Summarise a rule. Rules go in full.
  • Send stories to a tracker. That needs a person's OK.

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.