Conciseness

The body is efficient — tables and concrete ❌/✅ examples throughout, and it assumes Claude's competence (never explains what cold email or SPF is). Falls short of anchor 5 due to minor redundancy: the send cadence is stated twice ('Day 1, Day 4, Day 9, Day 16, Day 25' in Mode 2 and again in the Follow-Up Cadence table), and 'just checking in' guidance appears in three separate sections. Tighter than anchor 3 — there is little genuinely unnecessary explanation.

Actionability

Highly concrete: exact send-day gaps, word-count thresholds ('longer than 150 words'), a copy-paste tool invocation ('python3 scripts/email_sequence_analyzer.py sequence.json'), specific deliverability numbers (20/day warmup, 100-200/day limit, 5% bounce), and worked good/bad example lines. Minor gaps keep it from anchor 5: the 'Communication' section invokes 'the structured communication standard' and confidence-tag emojis without defining where that standard lives, and Mode 1 step 2 delegates framework choice entirely to references/frameworks.md without even naming the frameworks inline.

Workflow Clarity

Three modes each carry a clear numbered sequence, and the Tools section provides an explicit validation feedback loop for sequences: 'any email scoring below 70 gets rewritten against the flagged dimensions... then re-scored.' Not anchor 5 because validation is attached only to Mode 2 sequences — it is ambiguous whether a single Mode 1 email gets scored — and 'Before Starting' lists context to gather but no fallback when it is unavailable.

Progressive Disclosure

Well-executed structure: the body stays an overview, and three real one-level-deep references (references/frameworks.md, references/follow-up-playbook.md, references/deliverability-guide.md) are each signaled at the natural point of use ('See references/deliverability-guide.md for domain warmup schedule, SPF/DKIM setup, and spam trigger word list'). Verified against the bundle: all referenced files exist and contain no further nested references, so navigation is one hop deep.

Specificity

Names the domain ('B2B cold outreach emails to prospects who haven't asked to hear from them') and several concrete actions: 'write, improve, or build a sequence of' emails, plus 'needs to be humanized' for shared drafts. Falls short of anchor 5 because coverage has minor gaps — the performance-analysis/critique capability and follow-up writing are only implicit in 'build a sequence', not explicitly named.

Completeness

Explicitly answers both questions: what ('write, improve, or build a sequence of B2B cold outreach emails') and when ('Use when the user mentions' followed by concrete trigger phrases, plus the sales-y-draft case). This mirrors the anchor 5 example structure exactly.

Trigger Term Quality

Comprehensive synonym coverage: 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' 'email prospecting' — eight natural phrases a user would actually say, plus a behavioral trigger ('share an email draft that sounds too sales-y'). No natural variant is obviously missing; anchor 5 fits.

Distinctiveness Conflict Risk

Clear niche with explicit boundary against the closest sibling: 'Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).' Conflicts are pre-empted rather than left to inference; minimal conflict risk.