---
name: outreach-pipeline-planning
description: "Turn a qualified segment into a measurable outreach plan and review queue. Use when the user requests outreach pipeline planning. Select relevant methods for the requested outcome; unrelated tasks do not require this skill."
metadata:
  version: "1.0.0"
---

# Outreach Pipeline Planning

Turn a qualified segment into a measurable outreach plan and review queue.

## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts and required inputs. This generic package contains no client configuration. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for ownership, scheduling and completion. Preserve domain constraints; this Skill creates no competing execution path. Use one method, combine skills, or fill missing steps with authorized tools as the task requires.

External access uses the active Workspace’s approved Outloop capabilities. Never request, read, embed or expose credentials. A service named in a method is a possible dependency, not an access grant. Local file and application work uses the host’s authorized tools.

## Required inputs

- ICP and exclusions
- Verified prospects
- Suppression history
- Offer and channel constraints

## Methods

### Qualify the segment

Qualify the segment before writing a sequence. Separate sourced contacts, verified contacts, deliverable addresses and qualified replies in the funnel.

### Deduplicate next actions

Deduplicate against existing opportunities, suppression and recent activity. Assign one current next action per prospect and avoid concurrent channel collisions.

### Prepare the sequence

Write context-specific messages with supported claims and a clear low-friction next step. Check every personalization variable and fallback.

### Model capacity and measurement

Model capacity and follow-up cadence from approved limits. Report qualified response rate with a stated denominator; exporting a sequence is not evidence it was launched.

## Completion

Verify findings against source evidence and read back the resulting artifact or authorized change. Report inputs used, methods selected, output location, assumptions and unresolved dependencies. Do not report a plan, queue entry, draft, test fixture or accepted request as a completed external action. Use the task’s requested format; if a tool is unavailable, finish independent work and identify the exact unfulfilled deliverable.

## Test before relying on it

Read [the synthetic evaluation cases](references/evaluation.md) for activation, output and isolation checks. These cases are test instructions, not evidence that a host or provider test has passed.