Hire an AI family care visit coordinator

Everything it can hand back

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

• A short card of facts, with who reported each one and what is still unconfirmed
• A dated list of questions for the care team, grouped by priority
• Visit notes that keep the care team's words apart from your own summary
• A handoff draft for each person, with owners and open follow-ups
• A list of unclear points to take back to the care team

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

• Losing commitments buried in long notes.
• Mixing confirmed facts with guesses about other people's plans.
• Adding process when a short checklist would do.

What a good result looks like

An example, not your task: You have a doctor or care visit coming up for a parent or relative and want your questions ready.

• Care card. A short list of facts with who reported each, the changes you have seen and what is still unconfirmed.
• Visit questions. Questions for the care team, grouped by priority, with your original doubts kept.
• Visit notes. What the care team said in their own words, with who said it and when, apart from your summary.
• Handoff drafts. One short note per person with only the facts they need, plus an owner for each follow-up.
• Open-items register. Every unclear instruction or question still to take back to the care team.

How the work is checked

• Every action has an owner and a date, or is marked as missing one.
• Each item points to the note or message it came from.
• The output fits where it will be used, such as one screen or one page.
• 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.

A second opinion

Before it hands back, your AI reviews the draft the way Jeff Bezos and William Zinsser would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Reconcile the supplied care card. Makes a short card of facts, with who reported each one. Unknowns and conflicts stay marked. It hands the card to the question step.
• Prepare the visit questions. Turns your worries into questions for the care team, grouped by priority. It keeps your original doubts. It hands the agenda to the notes step.
• Record the reported visit outcome. Records what was said, with who said it and when. It stops until you bring real notes and never invents an answer from the care team.
• Draft the minimum necessary handoff. Writes one note per person with only what they need, owners for each open item and a list of what is still unclear.

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 family-care-visit-handoff 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/family-care-visit-handoff/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

• The purpose and date of the visit, and what you want from it
• A short summary of the facts that matter, using first names or initials
• Changes you have seen and instructions the care team gave before, with who said them
• Who needs a handoff and how much each may know
• Your notes from the visit, once it has happened (optional until then)

Helpful context (optional)

• A list of the people who need updates and what each may know.

Tools and access

• Claude, ChatGPT or Gemini: Any of them can follow the four stages. Pick one whose data handling you have read, since you share health details.

Functions and deliverables

• Family care visit coordinator: Prepare questions for a relative's care visit, record what the care team said and draft a short family handoff. You review it; nothing is sent.
  • A short card of facts, with who reported each one and what is still unconfirmed
  • A dated list of questions for the care team, grouped by priority
  • Visit notes that keep the care team's words apart from your own summary
  • A handoff draft for each person, with owners and open follow-ups
  • A list of unclear points to take back to the care team
  Source: Michael Sitarzewski and Agency Agents contributors.
• On-call handoff writer: Share verified shift alerts, open incidents and recent changes. Draft a handoff with next actions, owners and access checks.
  • A one-page handoff note
  • A list of open items with owners and next steps
  • Things to watch in the next shift
  • A reusable handoff template
  Source: sickn33.
• Team decision and dissent note writer: Share a decision and each person’s reasons. Record doubts fairly, name the decision owner and draft actions, signals and a review date.
  • One fair line of dissent per person, including the boss if they disagree
  • Each dissent sorted as a difference of view or a clash of aims
  • A named decider, a time limit and what each side brings, if the aims clash
  • A commit line each person says back, with an action in it
  • A signal that would show the decision is wrong, and a review date
  • A short note for the team
• Short article reporter: Plan one day of reporting, then write a short piece of 150 to 400 words about a place or person, built from your own notes.
  • A plan for one day of reporting, with questions to ask
  • A paragraph map with one job per paragraph
  • A tight draft within your word limit, from your notes only
• 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
• Jeff Bezos: Review a product or stuck decision through Jeff Bezos’s recorded approach. Start with the customer, test what can be undone and write the reasoning.
  • Your problem worked on the way Jeff Bezos would: their questions, their method, their push-back
  • The answer or the work, in Jeff Bezos's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• William Zinsser: Edit nonfiction using William Zinsser’s recorded approach. Find the point, order what readers need and cut words that add no meaning.
  • Your problem worked on the way William Zinsser would: their questions, their method, their push-back
  • The answer or the work, in William Zinsser's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You have a doctor or care visit coming up for a parent or relative and want your questions ready.
• You went to the visit and need to write down what was said before it blurs.
• Several family members need an update, but each should only see what they need.
• Notes from past visits disagree and you want the open questions in one list.

Limits to check before starting

• You need medical advice, a dose or a medicine check. Ask the care team or a pharmacist.
• Your relative has urgent symptoms. Call the care team or emergency services now.
• You want a full care plan with medicines and appointments tracked over time. Use the Aging parent care coordinator.

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.

• Before you paste anything, use first names or initials, share only what the plan needs and check your AI tool's data handling. Health details are private.
• Download the workflow and give all its files to Claude, ChatGPT or Gemini. Say "Read SKILL.md and workflow-state.json, then start with the first stage."
• Share the visit purpose, date and a short care summary. Check the fact card it writes before moving on.
• Take the question list to the visit. Come back with your notes and the AI will record them in the care team's own words.
• Read each handoff draft, cut anything the person does not need, then send it yourself. Nothing is sent for you.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/family-care-visit-handoff 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.