outreach-sequencelisted

# Design the sequence flow ## What this does Turns approved copy into a step tree: which channel touches the prospect, in which order, after how long, under which condition, and when the whole thing stops. It starts from one of Emelia's five campaign templates, chosen from what the enrichment actually found rather than from preference, then adapts it. It writes `outreach/campaign.json`, which is both the spec `outreach-campaign` consumes and the build sheet a human follows in the Emelia app. ## When to use it Use it after [outreach-write](../outreach-write/SKILL.md) has produced approved copy, and before anything is created in Emelia. Use it again when a campaign runs and one step is carrying it: cutting a step is a flow decision, not a copy decision. Use it as well when the only question is "which template do I pick", because the answer comes from the list and section 1 computes it in one command. Use a different skill when: you are writing the text of the steps ([outreach-write](../outreach-write/SKILL.md)), filling variables per contact ([outreach-personalize](../outreach-personalize/SKILL.md)), or checking whether the mailboxes can carry the volume this schedule implies (`outreach-deliverability`). ## Inputs | Input | Where it comes from | If it is missing | |---|---|---| | The copy, step by step | `outreach/sequence.md` | Stop, design a flow around copy that exists | | Contact count and segments | `outreach/leads.csv` | Ask, the count drives the A/B decision | | E