Email Copywriting
Draft subject lines and email body copy from a brief and deliver the finished copy as a file with a short summary.
When to use
- A teammate hands you a campaign brief and needs subject line options plus body copy.
- A prior draft needs revision or a fresh variant for A/B testing.
- Someone asks for ready-to-send email copy for a newsletter, product announcement, or nurture sequence.
Tools
read-file— pull the campaign brief, prior drafts, or brand voice notes before writing.write-file— save the finished subject lines and body copy as a deliverable file.complete-task— close out the task with a structured summary once the copy is saved.
Playbook
- Locate the brief. If it was attached as a prior artifact or referenced file, load it with
read-fileto get the offer, audience, tone, and call to action. - Identify the goal of the email (announcement, promotion, re-engagement, nurture step) and the single desired action from the reader.
- Draft 3-5 subject line options that vary in angle (curiosity, benefit-led, urgency, plain-language) and keep them under roughly 60 characters.
- Write the email body: a strong opening line, 2-4 short paragraphs or a scannable list of benefits, and one clear call to action.
- Match tone and terminology to any brand voice notes found via
read-file; do not introduce claims, numbers, or promises absent from the brief. - Add a preview text line (the snippet shown next to the subject line in most inboxes) that complements, not repeats, the subject line.
- Assemble subject lines, preview text, and body copy into a single clean markdown file and save it with
write-file. - If the brief is missing critical details (offer specifics, audience, deadline) that would force you to invent facts, note the gaps explicitly in the delivered file rather than guessing.
- Call
complete-taskwith a summary listing the number of subject line options drafted, the campaign goal, and the file path delivered.
Failure modes
- Missing or unreadable brief file -> stop and note in the
complete-tasksummary that the input could not be found; do not fabricate a brief. - Brief lacks essential facts (offer, audience, CTA) -> flag the gaps inline in the delivered copy instead of inventing details, and mention them in the summary.
- Conflicting instructions between the brief and brand voice notes -> default to the brief's explicit instructions and flag the conflict in the summary.
- Any request to also schedule, send, or push the email into an ESP (email service provider) -> out of scope for this skill; deliver the copy file and hand off scheduling/sending as a separate step.
Done when
- A markdown file containing subject line options, preview text, and full body copy has been saved via
write-file. complete-taskhas been called with a summary describing the campaign goal, number of subject line variants, and the delivered file path.- Any gaps in the source brief are explicitly noted rather than silently filled in.