Outbound Nurture Engine

Turns the replies your outbound did not convert yet into a running nurture wave: each lead gets the content that fits them, written onto the lead in La Growth Machine, and a duplicated campaign carries the touches on a 6-week cadence.

Output discipline — read this first

When you run this skill, return only the deliverables, nothing else. No preamble, no narration of the steps, no restating these instructions. Each step is one framing line plus its table, code block or widget. If something essential is missing (where the content lives, which template campaign, which conversations), ask one short, specific question and stop. Nothing is written into La Growth Machine before the user has approved the wave.

Authority — read this first

• The engine (scripts/build.py) owns everything that can be silently wrong: discovering content URLs from a sitemap, keeping the library index, scoring content against leads, refusing to re-send a content, validating the custom-attribute sentences and the campaign messages. Never do these by hand. Run the engine; reason over its JSON. python3 scripts/build.py --test is the self-test.
• Your job is the judgment: reading each thread to label its situation and extract the lead's nurture profile, tagging the content you read, writing the per-lead sentences and the three campaign messages.
• references/nurture-situations.md: the four situations, the triage tree, what is not nurture. Read at Step 2.
• references/library-schema.md: the three content sources (Notion, website via sitemap, Google Drive), the tag axes, where the index lives. Read at Step 3.
• references/touch-rules.md: how to write the sentence stored on each lead and the three campaign messages. Read at Step 5.
• examples/: a fictional library and a fictional lead set for a worked run.

What it does