This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI workflow improvement reviewer

Improve one work process. Get a step map, ranked bottlenecks, what to automate and small tests to try, from your numbers.

What you give

  • One process, in plain words, with the steps in order and who does each one
  • Time per step, split into work time and waiting time (rough numbers are fine)
  • How often the process runs, and what goes wrong, such as errors or redo

What you get

  • A step map of the process as it runs today, with times and who does what
  • A ranked list of bottlenecks, each with evidence, effect and effort to fix
  • A short list of steps that suit automation, and ones that should stay with a person
  • A set of small tests to run, each with one change, an owner, a measure and a trial length

An example

Work moves slowly between steps or people, such as approvals, handoffs or review queues.

You ask: “Improve one work process. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Workflow review. The process, your goal, how often it runs and how many steps it has.
  • Current flow. Each step with who does it, work time, wait time, errors and the tool used.
  • Bottlenecks. Steps that hold up the flow, ranked by effect and effort, with your numbers as evidence.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Run meetings, notes and plans

Details

Everything it can hand back

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

  • A step map of the process as it runs today, with times and who does what
  • A ranked list of bottlenecks, each with evidence, effect and effort to fix
  • A short list of steps that suit automation, and ones that should stay with a person
  • A set of small tests to run, each with one change, an owner, a measure and a trial length
  • Savings worked out from your numbers, with the sums shown
  • Facts still missing and what to time first

How it does the job well

  • Calculate a saving only from the user's numbers. Show the sum. If the numbers are missing, write "not enough data" and say what to time first. Never apply a made-up percent cut.
  • Keep what the user told you apart from what you assume. Label each assumption.
  • Rank bottlenecks by effect on the end-to-end result, not by how annoying a step is.
  • Name a kind of tool for automation (for example "a rule in your form tool" or "a scheduled export"). Do not claim a specific price, a saving or that a product does a thing unless the user supplied it.
  • Keep a person in the loop for judgment, sign-off, money and anything that touches customers.
  • 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.

Mistakes it avoids

  • Recommending a tool before the bottleneck is clear.
  • Quoting cycle-time cuts, savings or satisfaction scores from the profile as results.
  • Reviewing a whole department at once. Ask the user to pick one process.
  • 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: Work moves slowly between steps or people, such as approvals, handoffs or review queues.

  • Workflow review. The process, your goal, how often it runs and how many steps it has.
  • Current flow. Each step with who does it, work time, wait time, errors and the tool used.
  • Bottlenecks. Steps that hold up the flow, ranked by effect and effort, with your numbers as evidence.
  • Automation candidates. Rule-based steps that suit a tool, and judgment steps that should stay with a person.
  • Tests to run. Each fix as one change, owner, measure, trial length and the result that counts as success.
  • Savings from your numbers. Time or cost saved, with the sum shown, or "not enough data" if numbers are missing.

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.

Capabilities

  • Map the current flow. It lists each step with who does it, work time, wait time and error points. Gaps are asked once, then marked MISSING.
  • Set the baseline. It records today's time, volume and error figures from you, and lists the numbers it still lacks.
  • Rank the bottlenecks. It finds the steps that hold up the whole flow, and sorts them by effect on the end result and effort to fix.
  • Pick what to automate. It marks rule-based, repeated steps as candidates and keeps judgment calls with people. It names the kind of tool, not a bought plan.
  • Design the tests. For each fix it writes one change, one owner, one measure and a trial length, with what would count as a success.
  • Check the people side. It notes who is affected, what training or notice they need, and what could go wrong in the rollout.

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 testing-workflow-optimizer 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/testing-workflow-optimizer/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

  • One process, in plain words, with the steps in order and who does each one
  • Time per step, split into work time and waiting time (rough numbers are fine)
  • How often the process runs, and what goes wrong, such as errors or redo
  • The tools used at each step, such as email, a spreadsheet or a ticket system
  • Your goal, such as faster turnaround, fewer errors or less manual work
  • An export with real times, such as ticket dates (optional)

Helpful context (optional)

  • An export of tasks or tickets with start and end dates.
  • The written procedure for the process, if one exists.
  • A note from the people who do the work on where they get stuck.

Tools and access

  • Claude, ChatGPT or Gemini with file upload: It can read a spreadsheet of ticket dates or task times and work out wait times from your real data.

Functions and deliverables

  • Workflow improvement reviewer: Improve one work process. Get a step map, ranked bottlenecks, what to automate and small tests to try, from your numbers.
    • A step map of the process as it runs today, with times and who does what
    • A ranked list of bottlenecks, each with evidence, effect and effort to fix
    • A short list of steps that suit automation, and ones that should stay with a person
    • A set of small tests to run, each with one change, an owner, a measure and a trial length
    • Savings worked out from your numbers, with the sums shown
    • Facts still missing and what to time first
    Source: Michael Sitarzewski and Agency Agents contributors.
  • Process bottleneck finder: Describe the process and any timing data. Get a swim-lane map, cycle-time estimates and likely bottlenecks ranked.
    • A swim-lane process map
    • A ranked list of bottlenecks
    • Cycle time figures per stage
    • A root-cause guess for each bottleneck
    • The share of time spent on real work
    Source: Alireza Rezvani.
  • Queue and process simulator: Test a queue or process before you change it. Get a simulation of waits and busy staff or machines, run many times, with a plain summary.
    • A short model plan with the question, assumptions and what is left out
    • The simulation code, ready to rerun
    • Results for waits, queue length, how busy each resource is and jobs turned away
    • A range for every result, from many repeated runs
    • A plain summary and the next numbers to test
    Source: K-Dense.
  • HR process automation designer: Name your HR processes, like onboarding. Get which to automate, which tool fits each and a build order.
    • A ranked list of tasks to automate
    • Workflow designs for key processes
    • Tool suggestions for each flow
    • A business case and build order
    Source: Tuan Duc Tran.
  • 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

  • Work moves slowly between steps or people, such as approvals, handoffs or review queues.
  • Your team does the same manual task every week, and you want to know what is worth automating.
  • You have a quality problem, such as rework or errors at one step, and want a short list of fixes to test.
  • You must explain to a boss or client why a process is slow and what you plan to change.

Limits to check before starting

  • You want the root cause of a slow process, with baseline numbers measured first. Use the Operations Manager agent.
  • You only want each step marked as value or waste, fast. Use the Process waste finder.
  • You want to see why deadlines slip, week after week. Use the Project delay test reviewer.
  • You want the automation itself set up in Zapier or Make. Use the Automation flow sketcher after this review.

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 pack and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then paste references/source-agent.md.
  • Describe one process, step by step, as it runs now, not as it should run. Add who does each step and the time it takes, even if rough.
  • Say your goal and how often the process runs. Attach a ticket or task export if you have one. No code is needed.
  • Read the bottleneck list first. Check each one with the people who do the work, and fix the map if it is wrong.
  • Pick one or two tests, not all. Run them for the trial length and measure the same number before and after.
  • Ask the Automation flow sketcher to lay out any step you decide to automate.

Read it as data

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