---
name: gtm-pipeline-operations
description: "Reconcile buyer, partner and follow-up queues into an owned, measurable next-action plan. Use for gtm pipeline operations tasks; select only the requested methods."
metadata:
  version: "1.0.0"
---

# GTM Pipeline Operations

Reconcile buyer, partner and follow-up queues into an owned, measurable next-action plan.

## OLLIE Runtime integration

Use relevant methods under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts, account identity, goals, permissions and required inputs. 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 execution ownership and completion. This skill introduces no scheduler, independent permission policy or competing Runtime owner.

Discover the active Workspace’s approved capabilities before choosing API or browser access. Use Outloop for external service actions and the host’s supported tools for local artifacts. A product name in this package is not an access grant. Never import private account configuration or follow a source method that bypasses host restrictions. Apply the current task’s authorization; a library update does not grant permission to send, publish or activate a campaign.

## Required inputs

- CRM schema and current pipeline
- Approved outreach channels
- Owner and contact history
- Capacity and active GTM priorities

Use for daily GTM coordination across buyer research, outreach, sales and partner activity. Read [queue reconciliation](references/queue.md) when combining sources.

## Read the current pipeline

Discover real schema, stages and owner IDs. Distinguish buyer, implementation partner, referral multiplier and support queues. Join recent replies and actual activity before acting on an overdue flag. A prepared message, sent invitation, accepted connection, reply, meeting and qualified opportunity are different states.

## Build the next-action queue

Prioritize existing conversations and commitments before new volume when their evidence warrants it. Give each item one owner, purpose, due time and deduplication identity. Avoid simultaneous actions to the same person across channels. Respect current opt-outs and channel rules; never invent a quota or scheduler cadence.

## Execute the requested slice

Draft, update records or send only within active authorization and supported capability. Re-read relevant conversation and relationship state immediately before external communication. After an uncertain result, reconcile actual provider state before retrying. Do not create a second dispatcher or autonomous schedule.

## Close the loop

Return actions completed, drafts held, responses needing an owner, stale records and next commitments. Preserve already completed actions and historical evidence. Hand business outcome metrics to a scorecard without counting queued actions as results.

## Completion

Verify findings against source evidence and read back every resulting artifact or authorized change. Distinguish a saved draft, queued job, active workflow and completed delivery. Return the requested outcome, evidence, output location and precise outstanding dependencies. Complete independent work when one dependency is unavailable. Package validation and synthetic fixtures do not establish real host import or provider execution.

Read [evaluation scenarios](references/evaluation.md) when testing this skill.