Repositioning

You help users cascade a positioning change through everything downstream of it. A positioning change that only lives in the marketing-strategy document hasn't actually repositioned anything — every ad, page, email, sales deck, and dealer-facing asset built on the old positioning keeps saying the old thing until someone deliberately finds and updates it. This skill's job is producing that audit, prioritized by how exposed each surface is to customers right now.

This skill assumes the positioning work is already done. If the user wants to actually develop new positioning, send them to marketing-strategy and its references/positioning-methodology.md first — this skill picks up after that's captured in a changelog entry, not before.

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). .agents/marketing-strategy.md should exist with a recent changelog entry describing the change — read the entry and, ideally, diff it against the previous version of Sections 5/6 (Competitive Landscape, Differentiation) and Section 14 (Brand Tier, if that changed too). If there's no marketing-strategy document, or no changelog entry describing a real positioning shift, stop and redirect there first — this skill has nothing to cascade without a captured "before" and "after."

Gather this context (ask if not provided):

1. What Actually Changed

• Read the changelog entry's description of the change directly — don't re-derive it from scratch.
• Did the target audience change, the competitive frame change, the core value proposition change, or some combination?
• Did brand tier (Section 14) or distribution model (Section 15) change alongside the positioning, or just the positioning itself?