email-copywriting

How to write copy

Write the cold email sequence for one campaign segment: 2-6 steps (default 3), following the segment's angle, each step's purpose and its wait days. The copy must pass the lint contract below and the email-review checklist. In a conversation, draft in chat, get approval, then write it to the segment's emails.md. When a caller (the create-campaign workflow) hands you the plan and segment and saves the result itself, write the copy and return it.

You only write files. Sending, test sends and launch happen in the user's own sending tool (Instantly, Smartlead, Outreach, Apollo or any other), after a person approves the reviewed copy.

Where this fits

This skill runs once per segment, 0 - default included, inside the create-campaign workflow:

1. campaign-strategy - sequence blueprint and AI-variable definitions in the segment's strategy.md.
2. email-copywriting (this skill) - writes the sequence to the segment's emails.md.
3. email-review - scores the copy against the same rules and the lint; on pass, writes the fixed copy to emails_v2.md.
4. prompt-writer - writes the AI-variable prompts and the rewriting prompt to prompts.md and tests them on sample prospects.

On an email-review fail, leave emails_v2.md unwritten and rewrite emails.md with the review's instructions.

The campaign folder:

./cold-email/{slug}/
├── research.md          # client research: ICP, value prop, proof, voice
├── notes.md             # optional client preferences (they win over generic rules)
├── plan.md              # H1 = campaign name; 1 ICP + 1 offer + N segments
├── segmentation.md
├── 0 - default/
│   ├── strategy.md      # from campaign-strategy
│   ├── emails.md        # THIS skill's draft
│   ├── emails_v2.md     # reviewed copy from email-review
│   └── prompts.md       # from prompt-writer
└── 1 - {segment-slug}/

Inputs

• Campaign folder: ./cold-email/{slug}/ and the segment's folder in it (1 - {segment-slug}/, or 0 - default/). Ask when the user has more than one campaign.
• Offer, ICP, proof, voice: research.md in the campaign folder, notes.md when it exists, and the company files from knowledge-setup when the user keeps them, plus any research the user provides. Every claim must be checkable against it.
• Segment: name, angle, step purposes and wait days, from plan.md and the segment's strategy.md.
• Strategy: the segment's strategy.md (the ## Strategy - <segment name> section from campaign-strategy). Without one, run campaign-strategy first. A Voice Card from an earlier draft sits in the ## Notes section of the segment's emails.md.
• AI-variable names: if the segment already has a prompts.md, use its ### headings exactly. Otherwise the strategy's AI-variable list is authoritative.
• Priority: feedback in this conversation > client notes > campaign strategy > the generic rules below.