Hire an AI process guide revision reviewer

Everything it can hand back

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

• A register of your processes, with an owner and a review date for each
• The top five docs to fix this month, with the problem in each
• Rewrite drafts, each re-checked, marked for the owner to confirm
• A list of docs that need an owner, or that may no longer be needed
• A comparison with last month

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

• Rewriting many docs at once. Five a month is enough for owners to review.
• Treating an old review date as proof a doc is wrong. It is a reason to ask the owner.
• Filling gaps in a procedure with your own guess about how the work is done.
• Looping more than two rounds on one draft.
• 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: Your team has SOPs or runbooks that nobody has reviewed in a year.

• This month in one line. How many docs were checked and how many failed, compared with last month.
• Fix list for approval. The top five docs, each with its problem, the path taken, the draft file and the check result.
• Questions for owners. Docs that need a name, a check that steps are still true, or a qualified person's look.
• Proposed archives. Docs for processes that no longer run, with the reason.
• Left for later. The docs that did not make the top five.
• register.md and report.md. Each process with its owner and review date, and this month's findings for next time.

How the work is checked

• Each rewrite draft was re-checked and the result is shown, with the number of rounds.
• No draft claims a step, tool or name that is not in the original doc or from the person. Anything added is marked "to confirm".
• No doc on pay, leave, discipline, safety or legal matters was rewritten without a flag for a qualified person.
• Nothing was replaced, archived or published 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

• Get the register. Builds a list of the processes you run, who owns each and how often to review, once, then reuses it.
• Check the docs. Finds docs with no owner, an old review date, vague steps, no way to undo, or no links in. Marks each finding new, open or fixed.
• Rank and pick five. Puts risky and often-used processes first and keeps the top five for the month.
• Choose the path for each. A missing owner gets a question. A short task gets exact steps. A longer process gets owners and edge cases. A rule about people, money or safety goes to a qualified person.
• Loop until the draft passes. Re-checks each draft, fixes only what fails, and stops after two rounds. A draft that still fails goes to its owner as is.
• Hand back a fix list. Lists the five fixes, questions for owners and any docs to archive. You approve before anything changes.

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 process-doc-freshness-keeper 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/process-doc-freshness-keeper/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

• An export or folder of your process docs, SOPs or runbooks
• A short description of the business, the first time, so it can build the register
• What changed since last month, such as new tools, new rules or people who left (optional)

Helpful context (optional)

• A list of the five processes that hurt most when they go wrong
• The names of the people who actually do each process

Tools and access

• Claude Code: It can read a whole folder of docs, keep the register and report. You start each run. A timer is possible only if you set one up yourself.
• Notion: Export your SOP pages as Markdown. Publishing the rewrites stays with you.

Functions and deliverables

• Process guide revision reviewer: Find stale, unclear or ownerless process guides. Get a few draft fixes, recheck results and questions for the people doing the work.
  • A register of your processes, with an owner and a review date for each
  • The top five docs to fix this month, with the problem in each
  • Rewrite drafts, each re-checked, marked for the owner to confirm
  • A list of docs that need an owner, or that may no longer be needed
  • A comparison with last month
• Company wiki planner: Describe your business. Get the smallest useful process wiki set-up, with a register of each process.
  • A short wiki setup recommendation
  • A process register
  • Blank step-by-step guide templates
  • Export files if you ask
  Source: sickn33.
• SOP and runbook checker: Check your SOPs and runbooks for missing owners, stale pages and gaps. Get a ranked cleanup list and draft SOPs to fill what's missing.
  • Completeness scores for each SOP
  • A list of missing owners and stale pages
  • Orphan page and glossary problems
  • A prioritised cleanup list
  • Draft SOPs for the gaps
  Source: Alireza Rezvani.
• Recurring task procedure writer: Turn a task you repeat into a step-by-step guide anyone can follow, with fixes, rollback and who to call. Built for on-call staff.
  • Step-by-step guide with expected results
  • Fix steps for each failure
  • Rollback and check steps
  • Escalation contacts section
  Source: Anthropic.
• 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.
• 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

• Your team has SOPs or runbooks that nobody has reviewed in a year.
• New hires keep asking questions the docs should answer.
• You want a short, ranked fix list each month, not a long audit.

Limits to check before starting

• You want one SOP checked once: use the SOP and runbook checker.
• You want a new process written from scratch: use the Process and SOP writer.
• Your doc covers pay, leave, discipline or safety: ask a qualified person, such as an HR adviser or a lawyer.

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.

• Open Claude Code and add the agent as a skill, or save it in .claude/agents. Claude Code needs a paid plan.
• Put your docs in one folder. The first time, add a short note about your business.
• Ask the agent to run. It reads your folder, so your AI must be able to open files.
• Read the fix list. Ask each owner to confirm the drafts that touch their work.
• Say yes to one named action if you want it done, such as saving a draft. Replacing, archiving and publishing stay with you.
• Run it again on the first working day of each month. You can start it by hand, or set a timer such as a Claude Code routine or cron. It reads last month's report.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/process-doc-freshness-keeper 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.