agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/client-handover/SKILL.md

client-handover

Skill1 starsChanged 23 days agoMITView on GitHub

Creates a client handover pack when deliverables, knowledge, decisions and responsibilities must transfer into client ownership.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use near the end of an engagement or workstream before the consulting team exits or changes role.

    line 9
  2. Distinctive:

    Document open items, support routes and escalation conditions.

    line 22
  3. Distinctive:

    Use: Handover Overview, Scope Delivered, Artefact Register, Decision Record, Operating Guide, RACI, Open Items, Support and Acceptance …

    line 26
  4. Distinctive:

    Every in-scope deliverable has a disposition and owner.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Client Handover Pack

When to use it

Use near the end of an engagement or workstream before the consulting team exits or changes role.

What Claude needs

  • client-context.md and engagement scope
  • Final deliverables, decisions and outstanding items
  • Artefact locations, access arrangements and owners
  • Client capability, support period and acceptance criteria

Method

  1. Reconcile delivered work against scope and acceptance criteria.
  2. Inventory artefacts with purpose, location, version and owner.
  3. Summarise decisions, assumptions, dependencies and known limitations.
  4. Transfer recurring activities through a RACI and operating cadence.
  5. Document open items, support routes and escalation conditions.
  6. Plan walkthroughs, knowledge checks and formal acceptance.

Output format

Use: Handover Overview, Scope Delivered, Artefact Register, Decision Record, Operating Guide, RACI, Open Items, Support and Acceptance Sign-off.

Quality checks

  • Every in-scope deliverable has a disposition and owner.
  • Links, versions and access arrangements are verified.
  • The receiving team can operate without hidden dependencies.

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