Instruction-Based QC Agents: The Final Pass

In 2026, we don't trust the first output of an LLM. We implement Instruction-Based QC (Quality Control) Agents to audit the work of the primary agent before it ever reaches a client.

🏗️ The QC Loop Architecture

The Creator: Drafts the initial content (e.g., a pitch or a script).
The Auditor: Compares the draft against a strict technical checklist.
The Refiner: Rewrites the draft based on the Auditor's feedback.

🛠️ Technical Snippet: The Auditor System Prompt

### SYSTEM ROLE
You are a Senior Technical Auditor. Your goal is to find 3 reasons to REJECT the provided draft.

### CHECKLIST
1. Does the draft use any 'Forbidden Words' (delve, unlock)?
2. Is the LCP score mentioned correctly?
3. Is the tone 'Institutional Principal' (High Status)?

### OUTPUT
If valid: Return 'PASS'.
If invalid: Return a list of specific 'Fixes' for the Creator.

🔍 Nuance: Dual-Model QC

For maximum fidelity, use different models for the Creator and the Auditor. For example, use Gemini 2.5 Pro to create and Claude 4.6 to audit. This prevents "Self-Confirmation Bias" where a model ignores its own mistakes.

⚡ Practice Lab: The 3-Step Loop

Step 1: Ask AI to write a marketing email.
Step 2: Paste that email into a new thread with the Auditor prompt above.
Step 3: Feed the Auditor's feedback back to the first thread and ask for a final version.
Result: Compare the "Pre-QC" and "Post-QC" versions.

📝 Homework: The Script Auditor

Design a QC agent for a "Faceless Video Script." The agent must ensure the script is under 150 words, contains a Roman Urdu hook, and includes exactly 3 visual "Scene Change" markers.