cold-email-weekly-rhythm

Cold Email Weekly Rhythm — operational cadence

The framework + the infrastructure are necessary but not sufficient. What separates programs that ship from programs that don't is the weekly cadence. This sub-skill walks the operator through that cadence and surfaces the queue for this week.

Activation

Loaded by cold-email-kickoff when the operator is in iteration mode (reply data available, brand-config set up).

User-invocable on demand:

• "What's my cold-email rhythm this week"
• "Run the weekly rhythm"
• "Monday queue"
• "Friday review"

The default rhythm (Mon / Wed / Fri)

Monday — PSP signals + list refresh

Goals:

• Refresh the list with this week's signals (≤14 days old)
• Score list quality (dedup, role-fit, freshness)
• Set the week's send target (volume × personalization depth)

Tasks the skill runs:

1. Pull signals: For each anchor in brand-config.psp.signal_anchors, surface 5-10 new candidates from the operator's sources (LinkedIn job search, Crunchbase, RSS, etc.)
2. Score the list: Invoke cold-email-list-quality for dedup + role-fit + freshness scoring
3. Set the queue: Recommend send volume based on:
   • Warm-up state (brand-config.infrastructure.warm_up_status)
   • Reply-rate trend from last week
   • Available personalization time

Output:

# Monday — <date>

## This week's send queue
- Volume: <N> sends across <M> sequences
- Personalization depth: deep (≤30/seq) / medium (≤80/seq) / light (≤200/seq)

## Signal hunt (top 5 to verify by Wednesday)
1. <Company> — <signal>
2. <Company> — <signal>
3. ...

## List quality
- Score: <0-100>
- Dedup: <N> removed
- Role-fit: <N> outside ICP — flagged for removal
- Freshness: <N> stale signals removed

## Next: Wednesday ship + Friday review

Wednesday — sequence ship + reply triage

Goals:

• Ship this week's sequence (T1 for new prospects, T2/T3/T4 for in-flight)
• Triage reply pile from earlier in the week

Tasks:

1. Draft sequences via cold-email-craft using the operator's brand-config + SOUL.md voice
2. Self-check each draft via cold-email-reviewer agent
3. Spam-lint via cold-email-spam-lint
4. Route to send infrastructure (the operator's actual sending stack)
5. Triage replies received since Monday:
   • Score each via cold-email-reply-scoring
   • Route per brand-config.operations.reply_routing