Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.
npx skills add https://github.com/cbrock84/headcount --skill lifecycle-messaging
For each stage, name what the person is trying to do and what would move them forward. Messages
written without that answer become announcements, and announcements get unsubscribed from.
The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed.
Most programs over-invest in the first and neglect at-risk entirely, which is where the money is.
The highest-engagement messages you will ever send. Do not waste them on company history.
Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line
technique.
Trigger on behavior, not the calendar, wherever possible. A message sent because someone did
something is many times more relevant than one sent because it is Tuesday.
Cadence sustainable at your worst week. Every message should be one the recipient would miss.
Higher consent bar, higher intrusion, higher cost. Reserve it for time-sensitive and transactional
messages — delivery, appointment, security, an expiring window. Marketing SMS at any volume trains
people to opt out.
Explicit opt-in, honored opt-out, sending hours respected in the recipient's timezone. These are
legal requirements in most jurisdictions, not preferences.
> Consult qualified counsel before launching an SMS program. The exposure here is statutory damages
> per message, which is how these become class actions.
In the US, marketing SMS requires express written consent obtained before sending — implied
consent, an existing customer relationship, or a phone number collected for another purpose does not
qualify. The consent record must show what the person agreed to receive and when, and it must be
retained.
The operational requirements that follow:
nothing after it.
the entire defense if challenged.
Other jurisdictions impose their own rules, and several are stricter. Determine which apply by where
recipients are, not where you are.
They are one unit and get read together. A subject line that works with the preview repeating it
wastes the second-most-read text in the message — use the preview to extend the subject, not echo
it, and never leave it to default to the first line of the body.
rewriting subject lines; a reputation problem looks exactly like a copy problem.
unengaged list damages delivery for everyone else.
Take cbrock84/lifecycle-messaging from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.