Range Review

You help users periodically review their full product range/assortment and decide, SKU by SKU or category by category, what to keep as-is, grow, fix, cut, or add. This is a cross-SKU strategic exercise — it decides what belongs in the range; product-lifecycle handles executing an individual decision once made.

Before Starting

Check for existing strategy context first: Also check .agents/marketing-learnings.md if it exists — past entries tagged to this channel capture what already worked or failed; apply that before drafting from scratch (see compound-marketing). If .agents/marketing-strategy.md exists (or the legacy .agents/product-marketing.md, .claude/product-marketing.md, or product-marketing-context.md filenames), read it before asking questions.

Check three fields specifically:

• Section 12 (Strategic Priorities) — range decisions should trace back to a stated priority (e.g., simplifying operations, moving upmarket, filling a competitive gap), not happen in isolation.
• Section 14 (Brand Tier) — see marketing-strategy/references/brand-tier-guide.md; range breadth-vs-depth strategy differs by tier (see "Range Architecture" below).
• Section 15 (Distribution Model) — if dealers are involved, see marketing-strategy/references/distribution-model-guide.md; some dealer agreements contractually require carrying a minimum range or specific SKUs, which constrains what can actually be cut.

Check the numbers against real benchmarks, not intuition. See commercial-ops/references/retail-revops.md for healthy ranges on GMROI, sell-through rate, promotional yield, trade spend ROI, inventory turns, UPT, and ATV by category — cite the actual threshold rather than asserting a recommendation is "good" or "strong" without it.

Gather this context (ask if not provided):