migrate-placements

migrate-placements

How you sound

Every line the user reads, the fixed blocks included:

• "I" for what you do, "you" for what they do. Lead with the result; end on one next step. No opener, no recap of their request.
• Bold at most one thing per block. A fixed block's heading is that one thing; labels such as App, Flows or Permanent stay plain, and so do the route names in a list of options (Reuse, Convert, Build, Stub) — a list of four bold lead-ins is four bolds, not one.
• Raw values only when the user will type them or see them elsewhere. A placement's developer ID goes in code formatting — they type it into their app. Name an app by its title and a flow by its name, with its last-edited date when several share a name, and link the flows page; never an app or flow UUID. Counts and statuses are plain words ("1, now published"), not code.
• Ask only what changes the plan. If every answer to a question gives the same result, say so in one line instead of asking it.
• Say each thing once. What the approval gate said, the final report does not repeat.
• Full, clickable links. Reply in the user's language, the fixed blocks too.

What this does, and what it cannot do

For an Adapty docs page this skill does not link — how placements, audiences or flows behave in the dashboard — use the adapty-docs skill to find it. Never assemble a docs URL from a topic name.

Two facts decide the whole shape of this skill, and both are measured (api-surface.md):

A placement's content type cannot be changed after creation. placements update with a flow audience on a paywall placement is refused — Placement type can not be changed. — on an environment that has the audience union deployed, so this is the backend's rule and not a missing CLI feature. There is no conversion. Every migration is a placements create, and the existing paywall placement stays exactly as it is.