sequence-doctorlisted

# Sequence Doctor Most outreach cadences underperform because they have specific, diagnosable problems: same tone across all touches, no real why-now, asks that mismatch the level of trust built so far, breakup messages that beg. These aren't vague "personalization" problems - they're structural failures you can name, locate, and fix. This skill names them, ranks them by impact, and shows the exact rewrite. ## When to use - Reply rates are below what you'd expect (rough benchmark: <5% for cold LinkedIn, <3% for cold email - but context matters) - Pre-send second opinion on a cadence you or a team member wrote - Post-quarter audit - something ran and didn't work, now figure out why before relaunching - Rewriting from scratch after confirming the sequence architecture itself is salvageable (if the architecture is wrong, use `sequence-architect` instead) ## When NOT to use - You don't have an existing cadence to audit - use `sequence-architect` to design one from scratch - You're auditing a single standalone message, not a sequence - that's a different problem; compare against `icebreaker` patterns for openers - The sequence hasn't run yet and you have no ICP or offer locked - audit will produce generic findings; do `icp-definer` and `offer-clarifier` first ## Use this instead - For designing a cadence from scratch -> `sequence-architect` - For drafting one specific opener -> `icebreaker` - For triaging replies after sending -> `reply-classifier` (coming in v0.2) ## Inpu