Project Management

Client Handover

Prepares a professional handover: access boundaries, operating instructions, maintenance expectations, known issues.

What it does

Prepares a professional handover: access boundaries, operating instructions, maintenance expectations, known issues.

When to use it

Use after the final audit and before transferring project operation to the client or another team.

Problems it prevents

Stops handovers that leave a client locked out of their own accounts or unaware of a known limitation.

Typical workflow

  1. Document access and credentials boundary
  2. Write operating instructions
  3. List known issues honestly
  4. Confirm maintenance expectations

Example output

A handover document a client can actually operate from, including the parts of the build that still need attention.

What's included

  1. 01
    The complete prompt

    The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

  2. 02
    Install walkthrough

    Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

  3. 03
    Use notes

    How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Installation

Save the manual as SKILL.md in ~/.claude/skills/client-handover/ to use it on every project, or in .claude/skills/client-handover/ to scope it to one repository. Then invoke it directly:

/client-handover

Read the official Claude Code skills guide

Works well with