Hire an AI meeting action follow-up writer

Everything it can hand back

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

• An action list with owner, date, status and source for each action
• A list of owner and date gaps, and a draft of task changes
• One follow-up draft per due task, with what is still missing
• A note of every owner, date and recipient it could not confirm

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 just had one meeting and need each action tied to an owner and a date.

• action-register.csv. One row per action with id, task, owner, due date, timezone, status, dependency and source.
• clarifications.md. Owner and deadline gaps, plus overdue, due soon, blocked and undated work.
• proposed-task-changes.md. Task creates and updates for your task system, as a draft nothing has applied.
• follow-up-drafts.md. One draft per due task with recipients, subject, body and the facts still missing.
• draft-ledger.csv. Each draft's version and state, so nothing counts as sent until you send it.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is marked unconfirmed.
• Nothing was sent, published, created or changed without a clear yes.
• 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

• Executive action register keeper. Reads your notes or threads and builds one action list. Each action has an owner, a deadline and a source. Gaps go on a short list to settle.
• Due task follow up drafter. Takes the action list from step 1 and the related threads. Writes one follow-up draft per due task, with the missing facts and its send status.

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 turn-meetings-into-owned-actions 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/turn-meetings-into-owned-actions/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

• Meeting notes, a transcript or email threads
• The date window and your timezone
• Who attended, so owners can be matched to names (optional)
• Your current task list (optional)

Functions and deliverables

• Meeting action follow-up writer: Share meeting notes and related task threads. Get a sourced action list, clear owners and dates, and follow-up drafts for open items.
  • An action list with owner, date, status and source for each action
  • A list of owner and date gaps, and a draft of task changes
  • One follow-up draft per due task, with what is still missing
  • A note of every owner, date and recipient it could not confirm
• Action item tracker: Share meeting notes or email threads. Get action items with owners, deadlines and unresolved commitments.
  • action-register.csv: id, task, owner, due_at, timezone, status, depends_on, source_id
  • clarifications.md
  • proposed-task-changes.md
• Task follow-up writer: Share dated tasks and their message threads. Get recipient-specific follow-up drafts, missing facts and a clear draft/sent status.
  • follow-up-drafts.md with task ID, thread ID, recipients, subject and body for each draft
  • draft-ledger.csv with the version, state and message ID of each draft
  • A list of missing facts and approvals you still need to give
  • A short close with source coverage and one next step
• Internal meeting minutes writer: Turn your meeting notes or transcript into clear meeting minutes. You get decisions, action items with owners and due dates, and open questions.
  • A record with decisions, each with who approved it and why
  • Action items with an owner, a due date and what counts as done
  • Notes for each agenda item, with open questions
  • A parking lot for topics that need another meeting
  • TBD marks where your notes leave out an owner or date
  Source: GitHub Copilot community.
• 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

• You have just had one meeting and need each action tied to an owner and a date.
• The actions for one project are spread across a few notes and email threads, and you need one list.
• Some of those tasks are due and you want a follow-up drafted for each.

Limits to check before starting

• You only need tidy minutes to circulate: use Rough-note meeting minutes writer.
• You want a short written update from one meeting: use Meeting and written update planner.
• You want the same action list kept up to date every week: use Meeting minutes and action tracker.
• You want a weekly review of commitments and next week's priorities: use Executive priorities and commitment reviewer.
• You already have due tasks and only need follow-up drafts in your voice: use Task follow-up and voice editor.

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 handoff pack. It's a zip with HANDOFF.md, the Executive action register keeper skill and the Due task follow up drafter skill, in that order.
• Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
• Paste your notes or threads, the date window and your timezone.
• Check the action list and the gaps before you read the drafts.
• Send nothing until you have read each draft and said yes.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/turn-meetings-into-owned-actions 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.