Product-org-os subject-line

Document Intelligence

This skill supports three modes: Create, Update, and Find.

Mode Detection

@path/to/subject-lines.md

Threshold: >=85% auto-proceed | 70-84% state assumption | <70% ask user

Mode Behaviors

CREATE: Generate subject line options using methodology below, tailored to context inputs.

UPDATE:

1. Read existing subject lines (search if path not provided)
2. Preserve context and rationale
3. Generate improved alternatives based on feedback or new context
4. Show comparison: "Previous: [old]. New options: [new]. Rationale: [why better]."

FIND:

1. Search paths below for subject line documents
2. Present results: campaign/recipient, subject lines used, open rate if tracked, path
3. Ask: "Update one of these, or create new?"

Search Locations for Subject Lines

• outreach/

• campaigns/

• marketing/

• emails/

Gotchas

• Shorter wins in cold outreach — 1-5 words outperform 6+ words; resist the urge to over-explain in the subject
• Personalization means company/name in the subject, not just the body — but avoid being creepy or over-researched
• Never fake "Re:" or "Fwd:" to imply an existing thread — it damages trust and triggers spam filters
• A/B test results require minimum 100 sends per variant — do not draw conclusions from small samples

Generate email subject lines optimized for open rates, using research-backed patterns tailored to the recipient, company, purpose, and relationship warmth.

Vision to Value Phase

Phase 4: Coordinated Execution - Subject lines are part of campaign execution, enabling effective outreach for launches, sales, and customer communication.

Prerequisites: Phase 3 complete (target audience defined, messaging and positioning established) Outputs used by: Phase 4 (campaign execution, outreach sequences, sales enablement), Phase 5 (measuring campaign effectiveness via open rates)

Methodology

Research Findings (52,457 Cold Emails)

Subject Line Patterns

Pattern Selection by Relationship Warmth

Pattern Selection by Email Type

Spam Triggers to Avoid

Output Structure

# Subject Lines: [Recipient/Company/Campaign]

**Date**: [YYYY-MM-DD]
**Recipient**: [Name, role, company]
**Email Type**: Cold outreach / Follow-up / Newsletter / Transactional / Product launch
**Relationship**: Cold / Warm / Existing
**Purpose**: [What this email aims to achieve]

## Context Inputs

| Input | Value |
|-------|-------|
| Recipient name | [Name] |
| Company | [Company] |
| Role | [Title] |
| Purpose | [What you want] |
| Relationship warmth | [Cold/Warm/Existing] |
| Personalization hook | [Something specific you know about them/company] |
| Email type | [Cold outreach/Follow-up/Newsletter/Transactional/Launch] |

## Recommended Subject Lines

### Primary (Top Pick)

**Subject**: [subject line]
**Pattern**: [Which pattern from methodology]
**Why**: [1-2 sentences on why this works for this context]

### Alternatives

| # | Subject Line | Pattern | Rationale |
|---|-------------|---------|-----------|
| 1 | [option] | [pattern name] | [Why it works] |
| 2 | [option] | [pattern name] | [Why it works] |
| 3 | [option] | [pattern name] | [Why it works] |
| 4 | [option] | [pattern name] | [Why it works] |

## A/B Test Recommendation

**Variant A**: [subject line]
**Variant B**: [subject line]
**Hypothesis**: [What you expect to learn]
**Minimum sample**: 100 sends per variant
**Success metric**: Open rate (primary), reply rate (secondary)

## Anti-Patterns Avoided

| Avoided | Why |
|---------|-----|
| [Thing you deliberately did not do] | [Why it would have hurt performance] |

Instructions

1. Gather context inputs: recipient, company, purpose, relationship warmth, email type — ask if not provided
2. Check prior context: Run

   /context-recall [company or campaign]

   to find related positioning, messaging, or prior outreach
3. Check feedback: Run

   /feedback-recall [outreach/email/open rates]

   for signals on what has worked before
4. Reference any buyer research, prospect data, or campaign briefs provided via @file syntax
5. Generate 5-6 options across different patterns, selecting patterns appropriate to warmth and email type
6. Recommend a primary pick with rationale and an A/B test pair
7. Validate every option against the spam trigger checklist — reject any that fail
8. Save in outreach/ or campaigns/ folder when part of a campaign
9. Offer to integrate with

   /email-sequence

   or

   /campaign-brief

   if part of a larger flow

Integration

• Inputs from:

  /positioning-statement

  (messaging informs subject line angles),

  /campaign-brief

  (campaign objectives guide tone), buyer research files (personalization hooks)
• Outputs to:

  /email-sequence

  (subject lines feed into sequence steps),

  /campaign-brief

  (subject line strategy informs campaign planning),

  /sales-enablement

  (outreach subject lines for sales team)
• Related:

  /copywriting

  (full email body copy),

  /email-sequence

  (multi-step sequences),

  /campaign-brief

  (campaign-level planning)

Context Integration

After generating subject lines:

1. Offer to save: Ask "Should I save this to the context registry? (

   /context-save

   )" — especially if patterns are established for a specific audience
2. If yes, extract and save:
   • Winning patterns and context to inform future outreach
   • Link to related campaigns, positioning statements, and buyer personas
3. Suggest tracking open rates to validate pattern selection over time