# Agent SOP — [Agent Name]

> Duplicate this page for every new agent. All 12 fields are required.
> The SOP is the human-readable source of record — what the team sees.
> Part of the Dr Lead Flow AI Operations Playbook.

| Field | Value |
|---|---|
| **Agent Name** | Human-readable name (e.g., "Lead Auditor") |
| **Cron Name** | Technical cron identifier (e.g., `lead-auditor-daily`) |
| **Slack Channel** | Dedicated output channel (e.g., `#lead-auditor-agent`) |
| **What It Does** | One-sentence summary |
| **Why It Does This** | Business justification |
| **Frequency** | How often it runs (e.g., daily 7am ET) |
| **Output Destination** | Where results are posted |
| **Apps Needed** | Integrations required (CRM, calendar, ad platform, etc.) |

## Full SOP

Step-by-step process, written so a new team member could execute it manually:

1.
2.
3.

## Useful Links

- [Related dashboard]()
- [Source data]()

## Skills to Refer To

- `skills/[task-skill-name]/SKILL.md`
- Shared Source Skills used: [list connectors]

## Success Metrics

How output quality is measured (be specific — counts, accuracy thresholds, response times):

-

---

**Self-Contained SOP Rule:** This SOP must be self-contained for execution. It may reference an older SOP as source material, but it must not rely on old SOPs for runtime rules, scoring logic, or output requirements. Everything the agent needs to run must be in this SOP or its dedicated skill files.

**Change control:** Changes to this SOP require explicit approval before the agent's skill or cron is updated to match.