← Back to library

Write an NCR that scopes and locates every suspect part

Anthropic's Claude for Manufacturing plugin, added to its official plugin repository on November 12, 2026, includes a skill for nonconformance reports. It answers four questions in order: what was found, against which requirement, how many parts and where they are. It flags the report as blocked rather than inventing a requirement it cannot find.

  • OutcomeUse the ncr-writeup skill from Anthropic's Claude for Manufacturing plugin to turn an inspector's finding or a customer complaint into a nonconformance report that records the measured condition, cites the exact requirement at the revision the part was built to, works out how many parts are suspect and why, checks all five places they could be, searches earlier reports for the same problem and drafts a customer notice when bad parts may have shipped.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditanthropics
View original
Works with
ClaudeClaude CoworkClaude Code

Published Nov 12, 2026Updated Nov 12, 2026AI dry run on sample input: passed Nov 12, 2026Source verified Nov 12, 2026

When should you use it?

  • An inspector rejects a lot or an operator finds parts out of tolerance
  • A customer complaint about a part needs a formal record and a containment plan
  • Your quality team wants every report to show its scope reasoning and to check whether an earlier fix held

Not for: Root cause analysis and corrective action plans, which the plugin handles in a separate 8D skill; Plants that cannot share drawings, specs or inventory locations with the assistant; Replacing the quality engineer's sign-off on containment and disposition

What do you need, and what do you get?

You need

  • The finding: part and revision, work order, lot, operation, measured value, gage, who found it and when
  • The drawing, spec or customer requirement the part was built to
  • Inventory by location and shipment records, from exports or a connected ERP
  • Earlier nonconformance and corrective action files, and your plant's report template

You get

  • A nonconformance report in your plant's template with the requirement cited to document and location
  • A suspect quantity with the stated reasoning, marked as a minimum when traceability is incomplete
  • A containment table covering every location, showing which were checked and which were not
  • A note on related past reports and whether their fixes held
  • A draft escape notice for the customer when affected parts may have shipped

How does it work, step by step?

  1. Set up onceInstall Claude for Manufacturing, run onboarding and point it at your report template, quality document library and inventory exports.
  2. Describe the findingSay 'raise an NCR' and give the measured condition, the gage and the lot details, or paste the inspector's notes.
  3. Confirm the requirementCheck the cited drawing or clause. If the skill marks the report as blocked, find the requirement before going further.
  4. Review scope and containmentRead the suspect quantity reasoning and the location table, and act first on locations marked as urgent or not checked.
  5. Send or hold the customer noticeReview any drafted escape notice against the contract deadline before it goes out, and close the report only when you decide to.

The prompt

Our adapted version, written to work in Claude, Claude Cowork and Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt5 variables
Raise a nonconformance report for this finding: {finding}, measured with {gage}, on part {part_and_revision}, work order {work_order}, lot {lot}.
Cite the requirement it breaks from the drawing or spec at the revision the parts were built to. If you cannot find it, mark the report as blocked and say what you searched.
Work out how many parts are suspect, explain the reasoning, and label the number as a minimum if traceability is incomplete.
Fill a containment table for every location, showing checked locations with counts and unchecked ones as not checked.
Search earlier reports for the same problem and say whether the fix held. If parts may be at a customer, draft the notice but do not send it.

The original skill is published by anthropics on GitHub (anthropics/claude-plugins-official). Open it there to install or import it; the prompt above is our own adaptation.

What can go wrong?

  • A location left out of the table can be read as none there. Insist on all five locations, with unchecked ones labeled as such.
  • Citing the current drawing instead of the revision the parts were made to can point to the wrong requirement.
  • Shrinking the suspect quantity so the report looks better defeats the purpose of containment.
  • Anthropic publishes the plugin as a reference implementation without active maintenance, so try it on closed reports before live use.

Our take

Nonconformance reports often go wrong in predictable ways: the requirement is paraphrased instead of cited, the suspect quantity is just the parts someone happened to find, and nobody checks whether the same problem was fixed last quarter. This skill is built around exactly those failures, which is why we rate it highly for small and mid-sized plants. The best idea is the difference between a location that was checked and found empty and one that was never checked. Treating those as the same is how bad parts reach customers. We also like that a missing requirement blocks the report instead of being filled in, and that history is searched while the report is written, not weeks later. The limits are worth stating plainly. The output can only be as good as the drawings, inventory and shipment data it can see, and Anthropic says the plugin is not actively maintained. In our dry run on a fictional oversize-hole finding, it cited the drawing at the built revision, widened the scope to the full lot and listed the installed-at-customer location as not checked rather than zero.

Where the time goes back: Quality staff get a complete first draft with the requirement, scope reasoning, locations and history already gathered, so they spend their time on decisions and containment rather than on hunting through records.

FAQ

Who made it and what license does it use?
Anthropic released it in the anthropics/claude-plugins-official repository on GitHub under the Apache 2.0 license.
Can it work without connected systems?
Yes. You can paste in the inspector's notes and upload the drawing and an inspection file. Connected systems make the inventory and shipment checks faster.
Does it send notices to customers by itself?
No. It drafts the notice against the contractual deadline, and every step that would send or change something waits for a person.

Source and credit

This playbook is based on work by anthropics. We summarize it and link to it and write our own adapted prompt.

Original
ncr-writeup skill (anthropics/claude-plugins-official, Claude for Manufacturing)
Creator
anthropics
Published on
GitHub (anthropics/claude-plugins-official)
Original date
Nov 12, 2026
License
Apache-2.0
Originally for
Claude
AI dry run
Nov 12, 2026: passed. Dry-run tested by our AI test agent on sample input. Built-revision citation, reasoned scope, five locations with not-checked distinct from zero, history checked, notice held.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Nov 12, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

The original is licensed under Apache-2.0 by anthropics. Modified: our adapted prompt and summary are our own wording; the original skill {"was unchanged at the source when we snapshotted it (live source later removed)" if src_removed(s) else "is unchanged at the source link"}.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Pick the nearest eligible tech for a recall or callback

From a recall or callback record and a roster that includes skills, certifications, service areas, availability and drive-time estimates, get one recommended technician and one backup, with ineligible people excluded and reasons given, ranked by drive time rather than straight-line distance, plus a booking draft for the office to confirm. Nothing is booked and no one is contacted until a dispatch lead approves it.

Credit: Tyler Griffin (@TylerGriffin)

Under an hour
Operations & AdminPrompt✓ AI dry run

Set your agent's autonomy from your last ten approvals

Have your agent review the last ten times it handled a job you approve, sort what you accepted as written, edited or turned down, recommend one of four delegation levels (find out, draft, send after approval, or act within a rule), write the exact standing instruction, and replay it against those same cases before anything changes.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Confirm padel court times from a chat channel

Customers book, change or cancel courts by chatting, while a deterministic workflow assigns courts and prevents clashes.

Credit: u/PriceNew5674 on r/n8n

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Test a phone agent on one scripted call before rollout

Run every phone agent through the same awkward booking call with fixed traps before you let it dial real businesses.

Credit: u/Evening_Hawk_7470 on r/AI_Agents

Under an hour