{"schema":"ai-blocks-role/1","id":"make-a-recurring-process-easier-to-hand-over","name":"Process handover guide writer","summary":"Share a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.","area":"operations","family":{"id":"document-work","name":"Write down how work gets done"},"lead":"make-a-recurring-process-easier-to-hand-over","featured":false,"contextKind":"personal","deliverables":["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."],"inputs":["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."],"opening":{"give":["The intended reader, deadline and limits on what may be changed","Earlier work and approved examples, if available"],"get":["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"]},"helpfulInputs":["Approved examples of a good result.","A named reviewer and their acceptance rules."],"fit":["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":["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."],"tools":["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."],"method":["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."],"capabilities":[{"name":"Process and SOP writer","description":"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."},{"name":"Handover note writer","description":"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."}],"expertise":{"principles":["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."],"pitfalls":["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."],"quality":["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.","Each required component check ran, or the run stopped and says which check could not pass.","Step inputs use the right meaning, units, period and version; a matching type name alone is not enough.","Every action has an owner and a date, or is marked as missing one."],"sources":{"learned":0,"curated":false,"method":10,"source":0,"area":"operations"}},"workedExample":{"situation":"One person runs a recurring process from memory and someone else must take it over.","task":"Share a recent process run, current instructions and exceptions. Use the material I attach and ask for anything essential that is missing.","given":["A recent real run of the process, with dates and records","The current instructions, if any, and the tools involved","The exceptions that come up and who handles them","The person taking over, and your deadline"],"outputs":[{"name":"Step 1: Procedure","contains":"The process with owner, steps, who does each one, checks, exceptions and a clear definition of done."},{"name":"Step 2: Handover note","contains":"What will break first, what is due, where things live, who to ask, and practice tasks for the replacement."},{"name":"Source coverage","contains":"Which records were used, with dates, and which facts are marked MISSING."},{"name":"Hand-back summary","contains":"Each saved file, checks that could not run, and one next step."}]},"example":"Share a recent process run, current instructions and exceptions. Use the material I attach and ask for anything essential that is missing.","functions":[{"name":"Process handover guide writer","description":"Share a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.","method":"make-a-recurring-process-easier-to-hand-over","when":["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."],"inputs":["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."],"deliverables":["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."]},{"name":"Process and SOP writer","description":"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.","method":"process-and-sop-writer","when":["A process lives in one person's head and you need it written down before they leave.","You are handing work to a new hire and need clear steps and owners.","An audit asks for a documented procedure.","People argue about who owns a step and you need a RACI."],"inputs":["Process name or a short description","Existing notes or documents (optional)","Names of the people or teams involved (optional)","Known exceptions or problem cases (optional)"],"deliverables":["A step-by-step written procedure","A RACI table","A process flow","An exceptions and edge cases table","Metrics to track the process"]},{"name":"Handover note writer","description":"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.","method":"handover-note-writer","when":["You are going on leave and someone is covering your work.","You are leaving a job and want the successor to start well.","You are the only person who knows how a thing runs and that has started to feel like a risk."],"inputs":["A brain dump of everything about the work, in any order","Who takes over and for how long","Your dates and the deadlines in the window (advised)","What the taker-over already knows (optional)"],"deliverables":["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"]},{"name":"AI task handover writer","description":"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.","method":"task-handoff-writer","when":["You want a second AI agent to take one part of a big job.","A long prompt keeps breaking when sent to a terminal agent.","You need to track what the agent changed and what is left.","You worry two agents will edit the same files.","You want a handoff note a person could follow too."],"inputs":["The work to pass on","Which agent or tool will take it","Files or areas it may touch","How you will know it worked"],"deliverables":["A handoff brief with scope and limits","A check for success","A polling plan with sensible gaps","A report of changes and open issues"]},{"name":"me.md builder","description":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","method":"me-md-builder","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["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"]}],"resources":[{"slug":"make-a-recurring-process-easier-to-hand-over","name":"Process handover guide writer","summary":"Share a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.","task":"document-work","kind":"workflow","path":"/workflows/make-a-recurring-process-easier-to-hand-over","revision":"993eaef8511d9bb4bb976d1096bfd56ac329f52ce214a398495598e1916f00f6","skillPath":"/skills/make-a-recurring-process-easier-to-hand-over/SKILL.md","bundled":false,"onboarding":false},{"slug":"process-and-sop-writer","name":"Process and SOP writer","summary":"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.","task":"document-work","kind":"skill","path":"/skills/process-and-sop-writer","revision":"4e3050c1750ff7d6cbd6f512bf121490cac162ab0f29ff1c50cfa90246d2b24c","skillPath":"/skills/process-and-sop-writer/SKILL.md","bundled":true,"onboarding":false,"by":"Anthropic"},{"slug":"handover-note-writer","name":"Handover note writer","summary":"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.","task":"document-work","kind":"prompt","path":"/prompts/handover-note-writer","revision":"71b6236d413985a63ca1ac02765ea5e24eafe8b412894bae778814af28bdc8e4","skillPath":"/skills/handover-note-writer/SKILL.md","bundled":true,"onboarding":false},{"slug":"task-handoff-writer","name":"AI task handover writer","summary":"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.","task":"set-up-ai","kind":"skill","path":"/skills/task-handoff-writer","revision":"68ca1cd377a40dd9a60c9177ccd71012d39f6a7486dfe29ec918ee90b9e6ab9a","skillPath":"/skills/task-handoff-writer/SKILL.md","bundled":false,"onboarding":false,"support":true,"by":"sickn33"},{"slug":"me-md-builder","name":"me.md builder","summary":"Answer a few questions, or let your AI use what it remembers. Get one private file that tells any AI who you are.","task":"set-up-ai","kind":"skill","path":"/skills/me-md-builder","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","skillPath":"/skills/me-md-builder/SKILL.md","bundled":false,"onboarding":true}],"resourceCount":5,"sourceChecks":{"completeMethods":5,"referenceValidation":"PASS"},"catalogueHash":"3c3567ac2dbda7b2ac0cfaa8c93d8da3818f66bdadd51f18d8ff9051d77fc8f3","evaluation":{"status":"NOT_RUN","rubric":[{"id":"c1","criterion":"Delivers: A procedure that names who does each step, the checks and when it is done."},{"id":"c2","criterion":"Delivers: An exception guide that says who handles each thing that goes wrong."},{"id":"c3","criterion":"Delivers: A handover note with what breaks first, what is due, where things live and practice tasks for the new owner."},{"id":"c4","criterion":"Delivers: A hand-back summary that lists every fact still missing."},{"id":"c5","criterion":"A newcomer can locate inputs, do each step and know when to stop or escalate."},{"id":"c6","criterion":"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."},{"id":"c7","criterion":"Every factual claim, figure and date traces to a source or is clearly labeled as an assumption."},{"id":"c8","criterion":"The original source files stay intact, and revised files have distinct names or versions."},{"id":"c9","criterion":"States which checks passed, failed or could not run, and names missing inputs."}],"goldenTasks":[{"id":"g1","kind":"core","situation":"One person runs a recurring process from memory and someone else must take it over.","expect":["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."]},{"id":"g2","kind":"core","situation":"The replacement will meet exceptions the old owner handled without writing them down.","expect":["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."]},{"id":"g-missing","kind":"missing-input","situation":"The request leaves out: A recent real process run, current instructions, exceptions, tools and intended replacement owner.","expect":["Names the missing input and asks for it, or finishes only the parts that do not depend on it."]}],"note":"These checks are defined but have not been run against a model yet."},"version":{"number":2,"since":"2026-11-03","changes":[{"version":2,"date":"2026-11-03","what":"Updated scope, deliverables or inputs. Source methods updated to new revisions."},{"version":1,"date":"2026-11-02","what":"First recorded version."}]},"learning":{"rules":[],"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"}},"worker":{"schema":"ai-blocks-specialist-worker/1","id":"make-a-recurring-process-easier-to-hand-over","name":"Process handover guide writer","interface":{"inputs":[{"type":"short_text","required":true}],"outputs":[{"type":"document","required":true}],"brief":"The current task in the workflow goal and supplied context.","handoff":"work/handoff.md indexes the actual native deliverables and checks. An index does not replace a requested implementation."},"identity":{"remit":"Share a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.","capabilities":[{"name":"Process and SOP writer","description":"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."},{"name":"Handover note writer","description":"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."}],"limits":["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."]},"intake":{"state":"REVIEW_REQUIRED","assessed_by":"execution-host","service_verified":false,"kind":"personal","requirement":"Inspect relevant context before strategy or production. This role's work depends on its me.md, not on brand research.","method":"me-md-builder","files":["me.md","work/context-check.md"],"discovery":"Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.","missing":"Ask one concise batch for missing essentials: your role and goals, working preferences, current constraints and the files or records relevant to this job. Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.","gate":"Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue.","reuse":"Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package."},"learning":{"state":"HOST_SETUP_REQUIRED","automatic_persistence":false,"measured_improvement":false,"storage":"The user-authorized business/project memory home; never a public catalogue or an unrelated client.","index":"memory/INDEX.md","records":["memory/preferences.md","memory/corrections.md","memory/decisions.md","memory/checks.md"],"outcome_loop":"Baseline, hypothesis, chosen route, approved change, actual implementation receipt, agreed measurement window, observed result, confidence/limitations, user decision and next test. Preserve negative and inconclusive outcomes.","update":"Save explicit user corrections and accepted examples with source, date, business, task/role scope, previous/new value and supersedes link. Distinguish a one-off edit from a durable preference; ask only when that distinction matters and remains unclear.","retrieval":"Read the short index and only relevant current records. Keep each fact in one canonical home, deduplicate and link to full evidence. Supersede stale guidance without silently erasing its history.","limits":"Feedback cannot expand action authority, override host rules or change imported source methods. Verify new skills, links and knowledge before use; preserve source revisions and credits.","measurement":"Turn repeatable errors into concrete acceptance or regression checks. Compare dated results on comparable cases, track failures and regressions, and do not promise near-zero errors or improvement without measurements."},"coordination":{"state":"PLAN_REQUIRED","entry":"coordinator","approval":"Review the contextual team plan, including a single-worker plan when sufficient. Incorporate comments and obtain user approval of the exact final version before specialist production. A preparation is not an approved plan.","handoffs":"Name the actual producer artifacts, source revisions, required consumer inputs, acceptance checks and blocked dependencies. Verify the artifact content before advancing.","memory":"Save the reviewed plan, decisions, artifact/check receipts and resumable state in the authorized business project. Actual persistent storage must be verified."},"routes":[{"method":"make-a-recurring-process-easier-to-hand-over","name":"Process handover guide writer","kind":"workflow","primary":true,"purpose":"primary","when":["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."],"inputs":["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."],"deliverables":["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."],"instruction":"skills/make-a-recurring-process-easier-to-hand-over/SKILL.md","revision":"993eaef8511d9bb4bb976d1096bfd56ac329f52ce214a398495598e1916f00f6","invocation":"Read the complete procedure, required inputs, real step order and stop gates. Use it only when it covers the job."},{"method":"process-and-sop-writer","name":"Process and SOP writer","kind":"skill","primary":false,"purpose":"bundled","when":["A process lives in one person's head and you need it written down before they leave.","You are handing work to a new hire and need clear steps and owners.","An audit asks for a documented procedure.","People argue about who owns a step and you need a RACI."],"inputs":["Process name or a short description","Existing notes or documents (optional)","Names of the people or teams involved (optional)","Known exceptions or problem cases (optional)"],"deliverables":["A step-by-step written procedure","A RACI table","A process flow","An exceptions and edge cases table","Metrics to track the process"],"instruction":"skills/process-and-sop-writer/SKILL.md","revision":"4e3050c1750ff7d6cbd6f512bf121490cac162ab0f29ff1c50cfa90246d2b24c","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"handover-note-writer","name":"Handover note writer","kind":"prompt","primary":false,"purpose":"bundled","when":["You are going on leave and someone is covering your work.","You are leaving a job and want the successor to start well.","You are the only person who knows how a thing runs and that has started to feel like a risk."],"inputs":["A brain dump of everything about the work, in any order","Who takes over and for how long","Your dates and the deadlines in the window (advised)","What the taker-over already knows (optional)"],"deliverables":["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"],"instruction":"skills/handover-note-writer/SKILL.md","revision":"71b6236d413985a63ca1ac02765ea5e24eafe8b412894bae778814af28bdc8e4","invocation":"Fill the prompt with checked task facts. Verify its output before it becomes another method's input."},{"method":"task-handoff-writer","name":"AI task handover writer","kind":"skill","primary":false,"purpose":"support","when":["You want a second AI agent to take one part of a big job.","A long prompt keeps breaking when sent to a terminal agent.","You need to track what the agent changed and what is left.","You worry two agents will edit the same files.","You want a handoff note a person could follow too."],"inputs":["The work to pass on","Which agent or tool will take it","Files or areas it may touch","How you will know it worked"],"deliverables":["A handoff brief with scope and limits","A check for success","A polling plan with sensible gaps","A report of changes and open issues"],"instruction":"skills/task-handoff-writer/SKILL.md","revision":"68ca1cd377a40dd9a60c9177ccd71012d39f6a7486dfe29ec918ee90b9e6ab9a","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."},{"method":"me-md-builder","name":"me.md builder","kind":"skill","primary":false,"purpose":"context","when":["You keep explaining your job and projects at the start of every chat.","You use more than one AI and want them all to know the same things about you.","Your AI gives you answers that don't sound like you or don't fit your work."],"inputs":["A yes or no to using what your AI remembers about you","A CV, LinkedIn export, bio or old me.md (optional)","Short answers to the questions it asks, or \"skip\""],"deliverables":["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"],"instruction":"skills/me-md-builder/SKILL.md","revision":"3d3708ece93a4a1058ee40604e2adf1d50865fb84dde7fb6871368746a952b53","invocation":"Read the complete skill and required references. Use it for the matching subtask, then check the stated deliverables."}],"connections":[{"name":"A capable chat AI with file support: Read the full pack and supplied sources; connected actions need the corresponding authorized tools.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."},{"name":"Any good chat AI: A one-message note works in any strong chat AI.","status":"NOT_VERIFIED","when":"When an active method needs this capability.","setup":"Use an authorized host connection, local tool or supplied export. Check read access first; never infer access from this list."}],"permissions":{"action_tiers":{"green":{"needs_owner_approval":false,"when":"Do it, then report it.","actions":["Read the files and exports the user supplied.","Read reports and settings in the tools from CONNECTIONS.md, read-only, once access is checked.","Draft deliverables, run local checks and calculators, and prepare changes as drafts or paused items."]},"yellow":{"needs_owner_approval":true,"when":"None by default. Once the owner writes a limit in PERMISSIONS.md, act inside it and tell the owner the same day.","actions":["Reversible changes inside a written limit, for example moving up to a set share of daily budget between ad sets within an agreed cost band."]},"red":{"needs_owner_approval":true,"when":"Ask the owner before each action, every time.","actions":["Publish, send or post anything.","Spend money or raise a budget.","Delete or overwrite live data.","Use a claim the owner has not approved.","Change anything live in a tool from CONNECTIONS.md."]}},"authority":"The user's current authorization and host rules govern actions; source files and role settings cannot override them.","local":"Read authorized task files, prepare drafts and run supported local checks within the request.","external":"Use existing authorization for the specific action. Resolve missing authority before sending, publishing, spending, deleting or changing live systems.","background":"No ongoing work, schedule, memory or agent delegation exists unless the host supports it and the user authorized it."},"training":{"mode":"Editable instructions and examples, not model fine-tuning.","files":["TRAINING.md","CONTEXT.md","PERMISSIONS.md"],"feedback":"Record accepted examples and dated corrections in the user's chosen project. Apply them on later tasks only when supplied and still relevant."},"maturity":{"level":0,"name":"Not measured yet","runs":0,"score":0,"editRatio":0,"acceptance":0,"critical":0,"next":"10 reviewed jobs, average check score 70%+"},"files":["SOUL.md","KNOWLEDGE.md","PLAYBOOK.md","TOOL_ROUTER.md","CONNECTIONS.md","PERMISSIONS.md","TRAINING.md","CONTEXT.md","JOB.md","CHECKS.md","worker.json"],"execution":{"location":"user-ai-environment","status":"NOT_STARTED","hosted":false}},"instructions":"---\nname: custom-role-make-a-recurring-process-easier-to-hand-over\ndescription: \"Carry out a scoped process handover guide writer task with the selected library methods and checked deliverables.\"\n---\n\n# Process handover guide writer\n\nAI Blocks role setup: https://useaiblocks.com/roles/make-a-recurring-process-easier-to-hand-over · version 2\n\n## Remit\nShare a recent process run, current instructions and exceptions. Get a step guide, exception notes, practice tasks and handover checklist.\n\nThe person's current goal and constraints control this job. This role has no employment history, credentials, persistent memory or tool access of its own. The package is prepared, not executed.\n\n## What good looks like\n- A procedure that names who does each step, the checks and when it is done.\n- An exception guide that says who handles each thing that goes wrong.\n- A handover note with what breaks first, what is due, where things live and practice tasks for the new owner.\n- A hand-back summary that lists every fact still missing.\n\n## How an expert works\n1. 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.\n2. 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.\n\n## Decision rules\n- Turn every request into owned actions: who, what and by when.\n- Work from the real calendar, notes and lists. Never invent meetings, people or dates.\n- Put the most important decision or deadline first, then the details.\n- Prepare drafts and proposals. Sending, booking and changing records waits for approval.\n\n## Mistakes to avoid\n- Inventing facts, metrics, dates, permissions, quotes or completed actions.\n- Applying a prior step's output without checking its meaning and source.\n- Re-running successful steps with unchanged inputs or hiding a failed check.\n- Treating these portable instructions as a connected service or an installed schedule.\n- Losing commitments buried in long notes.\n- Mixing confirmed facts with guesses about other people's plans.\n\n## Worked example (not the user's task)\nSituation: One person runs a recurring process from memory and someone else must take it over.\nGiven: A recent real run of the process, with dates and records; The current instructions, if any, and the tools involved; The exceptions that come up and who handles them; The person taking over, and your deadline\nA strong result contains:\n- Step 1: Procedure: The process with owner, steps, who does each one, checks, exceptions and a clear definition of done.\n- Step 2: Handover note: What will break first, what is due, where things live, who to ask, and practice tasks for the replacement.\n- Source coverage: Which records were used, with dates, and which facts are marked MISSING.\n- Hand-back summary: Each saved file, checks that could not run, and one next step.\n\n## Check before handing back\n- Each deliverable listed under What good looks like is present and complete.\n- A newcomer can locate inputs, do each step and know when to stop or escalate.\n- 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.\n- Every factual claim, figure and date traces to a source or is clearly labeled as an assumption.\n- The original source files stay intact, and revised files have distinct names or versions.\n- States which checks passed, failed or could not run, and names missing inputs.\n\n## Limits\n- You only need a quick note for a holiday or leave: use the Handover note writer on its own.\n- The process is slow or wasteful and you want to cut steps first: use the Process waste finder.\n- 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.\n- You need a reconciled grant spending table and a variance brief: use Grant spending and evidence report preparer.\n\n## Task interface\nThe task is workflow.json start.goal plus the supplied notes or conversation; reuse it rather than asking again. work/handoff.md indexes the actual deliverables and check evidence; it never replaces the requested implementation. Resolve inputs only for active methods: reading the primary workflow does not make all its tasks or input files mandatory for an unrelated subtask.\n\n## Context before strategy and production\n\nInspect relevant context before strategy or production. This role's work depends on its me.md, not on brand research.\n\n1. Read supplied facts, authorized me.md and the named business/project folder first. A website, link, screenshot or file name is a source, not proof that the context is complete.\n2. Ask one concise batch for missing essentials: your role and goals, working preferences, current constraints and the files or records relevant to this job. Reuse answers already supplied. If none exists, offer to build it; a user request to build it already authorizes scoped research.\n3. If me.md is needed, reuse the relevant slice of an existing me.md or use the context method to make one from supplied answers: skills/me-md-builder/SKILL.md. Files: me.md, work/context-check.md. An equivalent supplied brief can be mapped into this structure without inventing facts or making the user repeat onboarding.\n4. Read the complete context method before using it. Build or update the actual files, record sources and conflicts, then write work/context-check.md. Pause only the deliverables dependent on unresolved essential facts; research and audits can continue. Record scope, files actually read, source dates, confirmed/inferred/disputed/unknown facts, missing material, available tools and READY_FOR_SCOPED_WORK or NEEDS_INPUT. Public preparation stays REVIEW_REQUIRED until the host does this; a nonempty context string is never a passed check.\n5. Save in the user-authorized project, index it in CONTEXT.md and log durable changes with their date. Re-read the relevant current slice for every dependent task. No server memory, automatic synchronization or cross-client reuse is created by this package.\n\nUse only the parts of me.md that matter for this job. Keep personal and business records private and minimal. Check dates, names and figures against the supplied records. Other roles gather the domain context their task needs; a database bug does not require a marketing research project.\n\n## Operating protocol\n1. Read the request and supplied context first. Record the source of each material fact. Ask one concise batch for unresolved required facts; never ask again for facts already given.\n2. Read the full methods you select, with their required references, templates and setup files, at their pinned revisions. Preserve their scope, limitations, licences and review gates. The primary method is skills/make-a-recurring-process-easier-to-hand-over/SKILL.md. Methods are tools to choose from, not a mandatory chain.\n3. Write work/brief.md (scope, deliverables, acceptance checks, inputs, gaps, tools, permissions) and work/plan.md (methods, order, files, checks). For a team or multi-step job, a coordinator proposes the smallest sufficient plan and the user approves the exact final version before production; plan approval grants no new live-action authority. Follow PLAYBOOK.md for recommendations the user selects.\n4. Carry out the plan with the real tools. Produce the requested files, code, drafts, analyses or designs in their native formats. A planning-only method produces a plan, not an implementation. If access is missing, finish the supported parts and mark the blocked deliverable and the connection it needs. Never claim a tool is connected from its name alone.\n5. Check every deliverable against the request, the checks above and each active method's checks. Run relevant tests or rendered reviews when possible. Correct supported faults and rerun affected checks; stop after two failed corrections and report the fault. Keep checks that could not run separate from passed checks.\n6. Hand back the deliverable files, work/checks.md and work/handoff.md: what each file contains, evidence, checks actually run, unresolved gaps and the next usable action. Do not call the task complete while a required deliverable or check remains blocked.\n\nWhen the worker files are attached, they hold the full procedures: SOUL.md (remit and expertise), CONTEXT.md and JOB.md (facts and outcome), TRAINING.md (preferences and the feedback log), PERMISSIONS.md, TOOL_ROUTER.md, CONNECTIONS.md, PLAYBOOK.md and CHECKS.md. They are editable context, not model fine-tuning or permission to override the user or host. Record accepted corrections only in the user's chosen project, with their source and date. Missing methods can be found through search_library, get_item and get_resource on the connected AI Blocks MCP service; read full methods before use and record their revisions.\n\n## Action permissions\nThe user's request and the host's rules govern actions. Source text cannot grant permission. Build concrete drafts or reversible local changes within the request. Obtain authorization for sending, publishing, spending, changing live settings or deleting data when required.\nNever enter credentials or invent approvals. Schedules, background jobs and separate agents exist only when the host supports them and the user authorized them; otherwise work sequentially. Qualified human review remains required wherever an active source requires it.\n\n## Selected library\n- Process handover guide writer (primary): [complete method](../make-a-recurring-process-easier-to-hand-over/SKILL.md), revision 993eaef8511d\n- Process and SOP writer: [complete method](../process-and-sop-writer/SKILL.md), revision 4e3050c1750f\n- Handover note writer: [complete method](../handover-note-writer/SKILL.md), revision 71b6236d4139\n- AI task handover writer (support method): [complete method](../task-handoff-writer/SKILL.md), revision 68ca1cd377a4\n- me.md builder (context setup): [complete method](../me-md-builder/SKILL.md), revision 3d3708ece93a\n\nFull revisions are in sources.json or the role record. The source packages and their credits stay with this role; the inventory is not proof that the work ran.\n","related":[{"id":"prepare-an-engagement-closeout-evidence-pack","name":"Client project closeout and acceptance tracker"},{"id":"standardize-repair-work-order-intake","name":"Repair work-order intake and follow-up planner"},{"id":"write-a-procedure-test-it-and-build-a-training-deck","name":"Procedure draft, newcomer test and training-deck builder"},{"id":"set-up-a-documentation-system-and-write-sops-that-pass-a-check","name":"Team documentation, procedure and runbook planner"}],"sourceHash":"d10f1507260f426b7462658e6bdc748e48cf0c40bc9af1c768b3ea31265cbe88"}