Sequence writer
@gtmengineer/sequence-writer
Write multi-step outbound sequences (email, LinkedIn, call) built on a real reason to reach out, with personalization slots instead of fake personalization. A built-in linter blocks spam phrases, fake Re: subjects, invented familiarity, unsourced stats, broken slots, too many links, and rushed cadence before anything is loaded into a sending tool.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Sequence writer
- 3Writes outbound sequences built on a real reason to reach out, with personalization slots you fill from research, and lints them before they go anywhere near a sending tool. Spam phrases, fake "Re:" subjects, "as promised" lines, unsourced stats, broken slots, too many links, and rushed follow-ups all get caught.
- 5## Who it is for
- 7SDRs, founders doing their own outbound, and GTM engineers building sequences in any sales engagement tool, who want replies without burning their domain or their reputation.
- 9## Example
- 11Input: `examples/draft-needs-work.json`, a two-step draft.
- 13Output (`out/lint.md`), first step:
- 15```text
- 16ERROR (slots): placeholder in square or angle brackets. Use {{slot}}.
- 17ERROR (spam): spam trigger phrase "guarantee"
- 18ERROR (fake-familiarity): subject starts with "Re:" but this is not a real reply
- 19ERROR (fake-familiarity): "as promised" implies a conversation that did not happen
- 20WARNING (unsupported-claim): "3x" needs a source in this step's sources list, or remove it
- 21WARNING (links): link in the first email hurts deliverability.
- 22```
- 24The rewritten `examples/sequence.json` lints clean, and `--preview examples/contact.json` shows the filled copy with any missing values flagged.
- 26## What it can access
- 28- Runs `node scripts/lint-sequence.mjs` (Node built-ins only, no network).
- 29- Reads `data/` (plus the kit's own `examples/`), writes `data/` and `out/`. Sends nothing.
- 31## Setup
- 33None.
