Hire an AI production shift staffing reviewer

Everything it can hand back

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

• A staffing comparison: hours needed against qualified hours available, by role and line
• A list of dependency gaps, such as a missing qualification or equipment that is down
• Handover options for the shift lead, each with what it needs and what blocks it
• A list of decisions the production owner must make
• Missing facts marked, so nothing is guessed

How it does the job well

• Count qualified hours, not paid hours. Remove maintenance, setup, changeovers, breaks and leave before comparing.
• Never calculate machine throughput or promise output.
• A proposed reassignment is a suggestion for the production owner. It is never permission to operate a line. Never suggest putting an unqualified person on a line.
• 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 are planning a shift and want to know if the work orders can be covered by qualified people.

• Staffing comparison. Hours needed against qualified hours available for each line or role, with the gap.
• Dependency gaps. Missing qualifications, equipment that is down, maintenance clashes and changeover time that cut the hours.
• Handover options. The options your numbers support, each with what it needs, what blocks it and who decides.
• Decisions for the production owner. Every move or priority change that needs the owner's yes before it happens.
• Hand-back summary. Files saved, facts that could not be checked and the single next step.

How the work is checked

• Capacity uses qualified people and equipment limits, not paid hours.
• Maintenance, setup, changeovers and leave were removed before hours were compared.
• No machine throughput was calculated and no move is called authorised.
• Every figure traces to a source or is labelled as an assumption.
• 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

• Team capacity planner. Compares work order hours with the qualified hours really available, after maintenance, setup, changeovers and leave. It hands the comparison and the gaps to the handover step.
• Handover note writer. Writes the shift lead handover with the options your numbers support, the blockers, the priorities you set and the decisions that need the production owner.

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 check-production-shift-staffing-commitments 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/check-production-shift-staffing-commitments/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 confirmed work orders for the shift, with the hours or quantity each needs
• The operators available, with the lines or machines each is qualified for
• Approved equipment capacity and any machine that is down
• Maintenance windows, setup times and changeovers
• The planned shift hours, breaks and known leave
• Who decides on moves, such as the production owner (optional)

Helpful context (optional)

• Your qualification or training matrix, so the AI never assumes who can run what.
• A named production owner who decides on moves.

Tools and access

• Claude, ChatGPT or Gemini with file support: They can read a spreadsheet of work orders and operators and show every sum. No code or web access is needed.
• Any good chat AI: It needs your numbers pasted in. A tracker or calendar connection saves typing.
• Any good chat AI: A one-message note works in any strong chat AI.

Functions and deliverables

• Production shift staffing reviewer: Compare qualified staff time with committed shift work. Keep setup and maintenance limits visible and prepare options for the shift lead.
  • A staffing comparison: hours needed against qualified hours available, by role and line
  • A list of dependency gaps, such as a missing qualification or equipment that is down
  • Handover options for the shift lead, each with what it needs and what blocks it
  • A list of decisions the production owner must make
  • Missing facts marked, so nothing is guessed
• Team capacity planner: Give it your team and projects. Get workload against people, who is overloaded, and whether you can take on more.
  • A table of hours available, hours used and percent full for each person
  • A list of who is over or under their target
  • Which coming projects fit and which leave a gap
  • Three to five options with the hours each one frees up
  • One recommendation, and what would change it
  • A list of assumptions and missing facts
  Source: Anthropic.
• Handover note writer: 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.
  • 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
• Equipment maintenance planner: Plan equipment maintenance that cuts breakdowns. Give it your machines and repair history. You get a service plan, a risk ranking and a spare parts list.
  • Service plan per machine
  • Ranked list of risky equipment
  • Spare parts list
  • Failure and repair time figures
  • Simple goals to track
  Source: Kishor Kukreja.
• 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 are planning a shift and want to know if the work orders can be covered by qualified people.
• Someone is off or a machine is down and the plan no longer adds up.
• A customer date depends on this shift and you need to know where it is at risk.
• You hand the shift to another lead and want the blockers and decisions in writing.

Limits to check before starting

• You run a restaurant or kitchen shift. Use the Restaurant shift handover and issue tracker workflow.
• A team member is away for days or weeks. Use the Team absence handover planner workflow.
• A disruption, such as a storm or strike, hits the whole site. Use the Plan staff coverage during a disruption workflow.
• You need machine speed or output worked out. Use your planning system, because this does not calculate throughput.

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 is a zip with HANDOFF.md and every skill file this workflow uses.
• Give the folder to Claude, ChatGPT or Gemini and say "Follow HANDOFF.md".
• Paste the work orders, the operator list with qualifications, equipment limits and shift hours. A spreadsheet export works.
• Check the staffing comparison first. If a qualification or a machine status is wrong, fix it before the handover is written.
• Read the handover, then give it to the shift lead yourself. Nothing is sent.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/check-production-shift-staffing-commitments 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.