Hire an AI process handover guide writer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A procedure that names who does each step, the checks and when it is done.
• An exception guide that says who handles each thing that goes wrong.
• A handover note with what breaks first, what is due, where things live and practice tasks for the new owner.
• A hand-back summary that lists every fact still missing.

How it does the job well

• Turn every request into owned actions: who, what and by when.
• Work from the real calendar, notes and lists. Never invent meetings, people or dates.
• Put the most important decision or deadline first, then the details.
• Prepare drafts and proposals. Sending, booking and changing records waits for approval.

Mistakes it avoids

• Inventing facts, metrics, dates, permissions, quotes or completed actions.
• Applying a prior step's output without checking its meaning and source.
• Re-running successful steps with unchanged inputs or hiding a failed check.
• Treating these portable instructions as a connected service or an installed schedule.
• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.

What a good result looks like

An example, not your task: One person runs a recurring process from memory and someone else must take it over.

• Step 1: Procedure. The process with owner, steps, who does each one, checks, exceptions and a clear definition of done.
• Step 2: Handover note. What will break first, what is due, where things live, who to ask, and practice tasks for the replacement.
• Source coverage. Which records were used, with dates, and which facts are marked MISSING.
• Hand-back summary. Each saved file, checks that could not run, and one next step.

How the work is checked

• A newcomer can locate inputs, do each step and know when to stop or escalate.
• The replacement has run one real exception from the recorded run with the new procedure, and the result is logged in the handover note. If they have not yet, the note says so.
• Every factual claim, figure and date traces to a source or is clearly labeled as an assumption.
• The original source files stay intact, and revised files have distinct names or versions.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Process and SOP writer. Writes the procedure from a recent real run, with who does each step, the checks, how each exception is handled and the definition of done.
• Handover note writer. Uses the procedure and your brain dump to write what will break first, what is due and where things live, then lists practice tasks for the replacement.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id make-a-recurring-process-easier-to-hand-over only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/make-a-recurring-process-easier-to-hand-over/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• A recent real process run, current instructions, exceptions, tools and intended replacement owner.
• The intended reader, deadline and limits on what may be changed.
• Earlier work and approved examples, if available.

Helpful context (optional)

• Approved examples of a good result.
• A named reviewer and their acceptance rules.

Tools and access

• A capable chat AI with file support: Read the full pack and supplied sources; connected actions need the corresponding authorized tools.
• Any good chat AI: A one-message note works in any strong chat AI.

Functions and deliverables

• Process handover guide writer: Share a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.
  • A procedure that names who does each step, the checks and when it is done.
  • An exception guide that says who handles each thing that goes wrong.
  • A handover note with what breaks first, what is due, where things live and practice tasks for the new owner.
  • A hand-back summary that lists every fact still missing.
• Process and SOP writer: Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.
  • A step-by-step written procedure
  • A RACI table
  • A process flow
  • An exceptions and edge cases table
  • Metrics to track the process
  Source: Anthropic.
• Handover note writer: Turn a brain dump into a handover note. The person covering your work sees what breaks first and what is due, and can act on day one.
  • Time bombs first, each with a date and an action
  • What is due, live work with next steps, and where things live
  • The people and how to deal with them, what to leave alone, how to reach you
• AI task handover writer: Write a task handoff brief for another AI agent: goal, files it owns, limits and a done check. Plus a plan to track its progress.
  • A handoff brief with scope and limits
  • A check for success
  • A polling plan with sensible gaps
  • A report of changes and open issues
  Source: sickn33.
• me.md builder: Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.
  • One me.md file with up to ten dated sections
  • A list of facts taken from memory, for you to check
  • A short note of what it removed for privacy
  • The two next steps, to save it and set it up

Tasks you can use it for

• One person runs a recurring process from memory and someone else must take it over.
• The replacement will meet exceptions the old owner handled without writing them down.
• You want a procedure the replacement can test by running one real exception from the record.

Limits to check before starting

• You only need a quick note for a holiday or leave: use the Handover note writer on its own.
• The process is slow or wasteful and you want to cut steps first: use the Process waste finder.
• Nobody has run the process lately and you have no real example: this needs a recent run, so do one first and keep the notes.
• You need a reconciled grant spending table and a variance brief: use Grant spending and evidence report preparer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the complete pack and add its governing file and component skills to your AI.
• Share the sources listed above and say which result you need.
• Ask the AI to follow the governing file, save each result and stop on a failed required check.
• Review the files, missing facts and proposed actions before using the result.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/make-a-recurring-process-easier-to-hand-over for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.