---
name: skill-outreach-draft
type: skill
description: Draft personalised outreach and follow-up messages in Aled's voice for a Network contact or a Pipeline opportunity, from the context skill-pipeline-sweep already captured. Use this whenever asked to draft a reach-out, a follow-up, or a reconnect note for someone in Network or an opportunity in Roles — write a short, specific draft tied to the relationship and the angle, and save it as a comment on the Linear issue (or a Gmail draft). Drafts only; never sends. Linear (and optionally Gmail) connector; never touches the delivery teams or a repo. Trigger it even when "draft" isn't said explicitly — any time the task is to prepare a message to a pipeline contact for Aled to review and send.
license: Proprietary — Aled Pritchard workspace use.
---

# outreach-draft

Drafts the message, never sends it. Given a Network contact or a Pipeline opportunity, this writes a short, specific outreach or follow-up note in Aled's voice, grounded in the context skill-pipeline-sweep captured (the Summary and Detail on the issue), and leaves it as a draft for Aled to review, edit, and send. Follows convention-linear and the human-action boundary: anything that sends or publishes is Aled's.

## Trigger

A request to draft outreach or a follow-up for a person in **Network** or an opportunity in **Roles** (Pipeline team, key PIPE) — a first reach-out, a follow-up after silence, a reconnect, or a reply angle. Trigger on the intent even when "draft" is not said. If no contact or opportunity is named, ask which issue. Pipeline only; never the delivery teams.

## Behaviour

1. **Read the issue.** Pull the contact or opportunity from Network or Roles and read its Summary and Detail — the Mode, the angle, who surfaced it, how Aled knows them, why-now, the links, and any quoted snippet skill-pipeline-sweep stored. This is the source material; do not invent a relationship the issue does not record.

2. **Read the thread for context where useful.** If the issue points to a Gmail thread and the Gmail connector is available, read it to ground the draft in what was actually said. Do not reply to it.

3. **Write in Aled's voice.** Calm, precise, sentence case, British spelling, no marketing-speak, no exclamation marks — the same register as the rest of the operating system. Short and specific beats long and generic.
   - Lead with the genuine connection or reason for writing, tied to this relationship and this angle.
   - Make one clear ask or next step.
   - Keep it to a few sentences — a message Aled can send with a light edit, not a wall of text.
   - Match the channel: a Gmail draft reads as email; a note for a LinkedIn message reads shorter.

4. **Save the draft — never send.**
   - **Default:** save the draft as a **comment on the Linear issue**, labelled plainly as a draft (for example, lead the comment with `Outreach draft —`), so it sits with the contact's record for Aled to use.
   - **Optional:** if a Gmail draft is wanted and the Gmail connector is available, create it as a **Gmail draft** (never send) and note in a Linear comment that the draft is in Gmail.
   - Where it helps, offer a short and a slightly longer variant so Aled can pick.

5. **Report:** which issue, the angle the draft takes, where the draft was saved (Linear comment and/or Gmail draft), and anything the issue left thin that Aled may want to fill before sending.

## Guardrails

- **Drafts only — never sends, never publishes.** Sending an email, a message, or any outbound contact is Aled's action, always. Respect the human-action boundary.
- **Grounded, not invented.** Write from what the issue and thread actually record. If the relationship or angle is unclear, draft conservatively and flag the gap rather than inventing warmth or history.
- **No state changes to the opportunity.** This does not advance funnel stage, change priority, or move the issue — drafting a message is not the same as acting on it. Stage moves follow the pipeline conventions, on Aled's signal.
- **Scope.** Pipeline only — Network and Roles. Never touches the delivery teams, a repo, or the Relay / exec / qa loop.
- **Add-only in Gmail.** If a Gmail draft is created, it is a draft and nothing more — never label, archive, or send mail.

## Setup

- Runs on the **Linear** connector (and optionally **Gmail** for reading the thread and creating a draft). No repo, no code.
- Routine prompt or ad hoc: "Draft outreach for [the contact or opportunity]."

Owned by **Scout** (`SC-0UT`) — the pipeline role that captures and qualifies people and opportunities.

On finish, run skill-ops-retro capture on this run's friction: file a FRICTION note to the Pulse queue for the drain pass to assess.