Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for proofreaders

Book Production Specification Agent

A production-ready proof with an exception log.

Book Production Specification Agent: what goes in, what the agent does and what you get

What it does

Manuscripts often fail production checks after layout changes, with broken cross-references, wrong contents entries or style sheet violations. This agent runs when production starts. It checks structural and production requirements against the publisher's style sheet, such as heading levels, figure numbering and front matter. It applies only pre-approved mechanical fixes in a working copy, then renders a proof and checks cross-references and contents after each group of corrections. When pagination changes, it regenerates the contents and affected references. Any fix that would change meaning is reverted and logged for the editor. The production editor approves print. Edge case: a cross-reference to a figure that was deleted is logged as an exception, not pointed at the nearest figure.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Production starts 2 USES A TOOL Check production requirements 3 USES A TOOL Apply mechanical fixes in a working copy 4 USES A TOOL Render the proof 5 CHECKS THE RESULT Are cross-references and contents correct? If not: regenerate affected entries and re-render. Backto step 3. 6 YOU APPROVE Production editor approves print 7 RESULT Production-ready proof and exception log
Read the steps as a list
  1. Production starts
  2. Check production requirements
  3. Apply mechanical fixes in a working copy
  4. Render the proof
  5. Are cross-references and contents correct?If not: regenerate affected entries and re-render. Back to step 3.
  6. Production editor approves printThe agent waits here for your OK.
  7. Production-ready proof and exception log

How it decides

Mechanical corrections only, verified by rendering.

  • Only pre-approved mechanical fixes are applied.
  • Fixes that change meaning are reverted.
  • Contents are regenerated after pagination changes.
  • References to deleted items are logged, not guessed.

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Publisher style sheet
  • List of pre-approved mechanical fixes
  • Proof rendering tool
  • Who approves print (default: production editor)
  • Exception log format

What keeps you in control

It always asks you first

  • Final print approval
  • Content changes
  • Vendor submission

Hard limits

  • No content changes.

It stops when

  • Done: proof passes.

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensFor a 320-page title, the agent finds 44 style issues and applies 41 approved fixes. After rendering, the contents still lists 'Chapter 6: Markets' though chapter 6 was split into two. The check fails, so it regenerates the contents and re-renders. A reference to Figure 9.3, which was cut, goes to the exception log. The production editor approves print.

More agents for proofreaders