Write a what-to-do card for every common machine stoppage
Claude reads your stoppage log, the machine manuals and your technicians' notes, finds the stoppages that cost the most time, and writes a one-page card for each: what the operator checks, what only maintenance may do, who to call and how to restart.
FullProductionWhen you need it
Set it up5 steps
Open the Claude desktop app and sign in with the Claude account you use for work. On a personal Free, Pro or Max plan, chats can be used for training unless you switch off SettingsPrivacyHelp improve Claude.
No account yet? Ask your manager.
Where things are in Claude
- CustomizeConnectors In Claude's left sidebar: connect your email and files.
- /schedule Type it in a new Cowork task to run a prompt on a schedule.
- Scheduled In Claude's left sidebar: what runs, to pause or change it.
- No stoppage log? Ask your technicians to list the 10 stoppages they fix most often on each machine, with what they do, and put the list in your Production folder.
- Put the machine manuals and your technicians' notes on past repairs in a Fault cards folder inside your Production folder, with a short list of who to call for each machine, by role and shift.
- Connect Google Drive under CustomizeConnectors. Keep this workflow's files in one Drive folder called Production.
- Open Cowork, paste the prompt and name the machine, or leave it out to cover every machine.
- Have your maintenance lead check every card before it goes up at the machine. Run it again after a new kind of stoppage.
Set this up on your computer: the Claude desktop app runs it.
The prompt
- Read the list of common stoppages in my Production folder, and the manuals, technicians' notes and call list in the Fault cards folder inside my Production folder. Work on the machine I name below, or on every machine if I name none.
- 1. Find the 10 stoppages that cost the most time: how often each happened and the hours lost.
- 2. For each, write a one-page card as a Google Doc in the Fault cards folder. Start with what it looks like: the alarm code, or what the operator sees and hears.
- 3. Then what the operator may check, in order, with what each check should show. Any step that opens a guard or a panel, or touches power, air, hydraulics or a moving part, goes under "maintenance only, after lockout". Never write a step that bypasses a guard, a safety device or an interlock.
- 4. Then who to call, by role and shift, and when: straight away, or after which check. Add the spare parts and tools it usually needs, how to restart, and the first-part check before production goes on.
- 5. Take every setting, pressure, temperature or torque from the manual or the notes, and name the page. Use the manual's diagrams and part drawings to name the right part and where it sits. If nothing gives a value, write [CHECK: value].
- 6. Add an index sheet in the same folder: card, machine, stoppage, how often, hours lost, the costliest first.
- Write short, plain sentences an operator can follow standing at the machine.
If your company keeps technical drawings out of AISafe version
Reads the manuals' text, your notes and the stoppage log only. Schematics, wiring diagrams and part drawings stay shut and are named by their number.
What you get
One printable card per common stoppage, the costliest first, with every value taken from the manual or your notes and every gap marked [CHECK] for maintenance.
Learn how
Get this workflow for your team
Two minutes each: everyone gets a plan of ready workflows like this one, inside your company's rules.
Your manager sees progress and hours. Never what Claude reads or writes.
FirstPrompt's workflow library adapts parts of Anthropic's knowledge-work-plugins (Apache-2.0), rewritten by FirstPrompt. Source and licence