Task

Generate outreach copy for qualified Meta leads

created 3/18/2026, 12:23:27 AM • updated 3/18/2026, 12:23:29 AM

project: Meta Outreach Agent System

Adaptive Task Framework

Expected Output

First reviewable lead-list batch with exact URLs, source query, context, qualification notes

Review Owner

Destination Surface

Campaign Assets (linked Brief)

Fallback If Blocked

If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective

researchbuildreview

Research

active

Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria

Done when

Evidence-backed findings and a recommendation are attached.

Bound artifacts

No research artifact bound yet.

Build

ready

Turn the criteria into a clean, deduplicated, reviewable lead batch

Done when

First reviewable lead-list batch with exact URLs, source query, context, qualification notes is attached with verification notes.

Bound artifacts

No build artifact bound yet.

Review

active

Check fit, quality threshold, duplication, and whether the batch is approval-ready

Done when

A clear pass/fail decision with exact fixes or approval conditions exists.

Bound artifacts

No review artifact bound yet.

New and updated tasks automatically carry the research → build → review framework, and this task now stores structured phase state so sub-agents inherit a consistent quality bar.

Title

Description

Outreach copy drafted for 5 qualified Meta leads:

1. **Your Meta Ad Account is a Mess** (LinkedIn)
   - *Copy*: "Hi [Name], I noticed your post about Meta ad struggles. Let's chat about how to fix your ad account and boost performance. Ready for a quick call?"

2. **The most common reason Meta ads don't scale?** (LinkedIn)
   - *Copy*: "Hi [Name], I saw your post on Meta ad scaling. Let's discuss how to overcome bottlenecks and lift conversions. Interested in a strategy call?"

3. **What's the hardest part of running meta ads?** (Facebook)
   - *Copy*: "Hi [Name], I read your post about Meta ad challenges. Let's review your ads and optimize for better results. Want to schedule a call?"

4. **Read more** (Facebook)
   - *Copy*: "Hi [Name], I saw your post about Meta ad pain. Let's talk about how to improve your campaign performance. Ready for a call?"

5. **Candidate result** (Facebook)
   - *Copy*: "Hi [Name], I noticed your post about Meta ad struggles. Let's chat about how to fix your ad account and boost performance. Ready for a quick call?"

All copies are now ready for review.
Workflow Contract:
EXPECTED OUTPUT: First reviewable lead-list batch with exact URLs, source query, context, qualification notes
DESTINATION SURFACE: Campaign Assets (linked Brief)
REVIEW OWNER: TC
FALLBACK IF BLOCKED: If blocked, attach the best partial artifact plus blocker note and create/trigger one recovery objective
Adaptive Three-Phase Framework:
PHASE 1 — RESEARCH
Objective: Qualification rules, market fit, source quality, and exact inclusion/exclusion criteria.
Required output: Evidence-backed findings, key constraints, and the best recommendation for the task.
Sub-agent standard: Research runs must return sources/evidence, uncertainty notes, and a recommendation.
PHASE 2 — BUILD
Objective: Turn the criteria into a clean, deduplicated, reviewable lead batch.
Required output: First reviewable lead-list batch with exact URLs, source query, context, qualification notes.
Sub-agent standard: Build runs must return the actual artifact/change plus verification notes.
PHASE 3 — REVIEW
Objective: Check fit, quality threshold, duplication, and whether the batch is approval-ready.
Required output: Clear pass/fail decision, exact fixes if not ready, and approval conditions if partially ready.
Sub-agent standard: Review runs must judge readiness independently instead of redoing the whole task vaguely.
Cross-Phase Delegation Rule:
- Any spawned sub-agent should stay inside one phase unless the requester explicitly asks for multi-phase work.
- If a sub-agent crosses phases, it must separate its output by phase so quality can be audited cleanly.
Definition of Done:
- Complete the work through Research, Build, and Review unless the task clearly does not need one of those phases
- Produce the named output
- Link or attach the artifact where stated
- Add EVIDENCE and VERIFICATION before REVIEW/DONE
- Urgent rule: one owner, helpers optional, no silent drift
EVIDENCE: (fill)
VERIFICATION: (fill)

Status

Priority

Owner

Tasks now carry an adaptive framework by default. Next: phase-aware UI controls and artifact-linked completion checks.