segmentation

Segmentation Skill

Write the audience description and segment-specific prompts for AI segmentation. These prompts feed any segmentation step that routes prospects into mutually exclusive audience segments.

Output Contract

segmentation.md must follow a fixed structure so downstream campaign tooling can parse it reliably. Hard rules this skill must honor:

• ## Default Segment H2 (or legacy ## General Audience) - its body is the general audience description for the Default / catch-all segment.
• ## Segments H2 wraps all audience-segment H3s.
• Each audience segment is ### Segment N: {Name} (or ### {Name}). Authors may write Segment N: prefix for organization; tooling strips it before slugifying.
• The canonical name slug (re.sub(r"[^a-z0-9]+", "-", name.lower()).strip("-")) MUST match the segment folder's slug. Mismatches warn and leave the segment with an empty description.
• Always create the 0 - default/ folder alongside the numbered segments. Audience segments are 1 - {slug}/, 2 - {slug}/, etc.
• Optional ## Segmentation Mode H2 selects ai (default) or percentage. In percentage mode each ### Segment N carries a - **Weight**: N line (int 1-100) instead of criteria, and so does ## Default Segment (the Default is one of the test arms - use it as the baseline/control); weights of ALL arms including the Default must sum to exactly 100, and tooling records a percentage weight per arm. See the Segmentation Modes section below.

Required Context

1. Read plan.md from the plan folder - Segment definitions and angles
2. Read qualification.md from the plan folder (if exists) - Audience description to reuse, criteria to NOT repeat
3. Read search-strategy.md from the plan folder - Search filters already applied. Never restate any of these dimensions in segment criteria.
4. Read {workspace}/research.md - Client overview, ICP details ({workspace} = the client campaign workspace, default ./cold-email/{slug}/ under the current directory)