{"id":"mkt2-breaking-change-notice-three-lines","audience":"product-managers","category":"writing-emails","track":"marketing","technique":"format","level":"intermediate","title":"Write a customer notice about a change with what to do and by when","free":false,"task":"The Lumen API is retiring version 1. Write a prompt for a customer email with a line starting \"Subject:\", then exactly three labeled lines \"What's changing:\", \"When:\" and \"What to do:\", each one sentence, and the sign-off \"Lumen Developer Team\". Use only the confirmed dates and facts, don't promise a migration tool that isn't released, and keep it under 90 words.","materialLabel":"Change notice facts (attached to your prompt automatically)","material":"LUMEN API - v1 retirement\n\nConfirmed:\n- API v1 will stop working on March 31, 2027. v2 is available today.\n- Customers must update their API calls to v2 and replace their v1 keys with v2 keys (created in Settings > API).\n- v2 docs: docs.lumen.example/v2\n- From Jan 15, 2027 requests to v1 will return a warning header (no failures yet).\n\nNot confirmed / not released:\n- A \"migration assistant\" tool (in development, no date)\n- An extension of the March 31 date (requested by some customers; not approved)\n- Pricing changes for v2 (none planned, but not yet announced)\n\nAudience: developers at customer companies. Tone: clear and direct, no apology, no hype.\nPrevious notice (do not reuse): \"We're excited to announce an upgrade...\".","rules":[{"type":"plainText"},{"type":"maxWords","max":90}],"mistakes":[{"title":"Promising a migration tool","why":"The AI offers the tool in development.","fix":"Say: \"Don't mention tools that aren't released.\"","checks":["r2"]},{"title":"Hinting at an extension","why":"The AI softens the deadline.","fix":"Say: \"Use only confirmed dates; no hint of extension.\"","checks":["r2"]},{"title":"Marketing tone","why":"The AI writes 'we're excited'.","fix":"Say: \"Clear and direct; no hype.\"","checks":["r0"]},{"title":"Missing the action","why":"The AI explains the change but not what to do.","fix":"Name the three labeled lines.","checks":["r1"]},{"title":"Letting markdown through","why":"AI adds bold text and headings by default.","fix":"Add: \"Plain text only, no bold, no headings.\"","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and often runs past a word limit.","fix":"Cap each part (for example \"each line under 15 words\") so the total lands well under the limit.","checks":["maxWords"]}],"promptHints":[{"label":"Gives the three labels","patterns":["what'?s changing:.*when:.*what to do:"]},{"label":"Uses confirmed dates","patterns":["march 31","confirmed","jan 15"]},{"label":"Bans unreleased items","patterns":["migration","not released","extension","pricing"]},{"label":"Gives sign-off","patterns":["lumen developer team"]},{"label":"Caps length","patterns":["90 words","one sentence"]}],"hint":"A change notice has to be clear about the date and the action. Give the labels, restrict it to confirmed facts and ban unreleased promises.","mission":"Tell customers the Lumen API v1 is retiring and what to do.","musts":["Confirmed dates only","No unreleased migration tool","Under 90 words"],"rubricLabels":["The email has a Subject: line, three lines starting What's changing:, When: and What to do:, each one sentence, and the signature Lumen Developer Team","It says v1 stops working on March 31, 2027, mentions the warning header from Jan 15, 2027, and tells customers to move to v2 with new v2 keys and gives docs.lumen.example/v2","It does not mention a migration assistant, a possible date extension or pricing, and does not use excited or upgrade language"]}