---
name: loomi-segmentation-strategy
description: Recommend and refine high-impact Bloomreach Engagement segmentations from local contexts, supplied projectContextJson, relevant business context, optional Bloomreach CLI cards when available, and user feedback. Use when the user asks for segment ideas, audiences, CRM opportunities, targeting strategy, lifecycle segments, retention segments, VIP segments, churn/winback audiences, or wants to refine/prioritize segmentation recommendations.
---

# Loomi Segmentation Strategy

Use this skill to produce a ranked segmentation opportunity matrix, not a generic idea list.

## Workflow

1. If no project brief or task packet exists, use `loomi-project-discovery-brief` first.
2. For broad strategy, load relevant `contexts/` files and supplied `projectContextJson`.
3. If Bloomreach CLI context exists, use cards for broad coverage or targeted asset evidence, with raw fallback only for exact selected-object details.
4. Call `recommend_segmentations`.
5. Show the user the top recommendations with:
   - segment name and objective
   - Bloomreach logic
   - required data
   - personalization hooks
   - conversion mechanism
   - impact, effort, confidence, and risk
   - recommended first scenario
6. Ask for feedback or selection.
7. When the user gives feedback, call `refine_segmentations`.
8. Preserve the decision record and explain what changed.

## Ranking Rules

Prioritize segments that:

- match the stated business goal
- can be built from available events/properties
- have a clear conversion mechanism
- respect consent, suppression, and frequency policies
- can be measured with holdout or target-vs-control logic

Demote segments that:

- require unavailable data
- rely on broad discounts or bonuses by default
- duplicate existing scenarios without a better angle
- create consent, suppression, or sensitive-personalization risk

## Tools

Use:

- `recommend_segmentations` for first-pass ranking
- `refine_segmentations` after user feedback

For unavailable optional fields, pass empty strings. For unavailable project context, pass `"{}"`.

## Output Standard

Do not stop at names. For each recommended segment, include why it should convert customers and what could go wrong.