Clean up an old help center

Prompt pack · 38 pages · 13 prompts + house style

Write release notes people and AI can use

Turn a messy list of what shipped into notes people read, then find the help articles the release just broke.

After using this: You'll have release notes that answer the questions people actually ask when something changes, and a habit that keeps your articles up to date with each release.

Who this is for

You have to tell customers what changed, and right now it's either a list of ticket numbers or nothing at all.

Not for you if

You want something that writes the notes for you off the back of your commits. A person still has to decide what mattered.

$59

One-time purchase · HTML and PDF

License

Instant delivery after payment.

Also in a bundleSave $87Clean up an old help center

How it works

Your changelog is the only record of when your product changed. This pack covers sorting what shipped into news and noise, writing the entry, announcing a breaking change or a rename, and the chapter nobody expects: why an AI needs your changelog to know what's current.

What's inside

  1. 01The 5 rules behind every prompt
  2. 02Setting up your changelog: where it lives, who owns it, how loudly to announce
  3. 03Making your changelog AI-ready
  4. 0413 prompts, from sorting what shipped into news and noise to a monthly "what's new" roundup, including breaking changes, renames and the announcement email
  5. 05Finding the help articles a release just broke, with a finished example of what prompt 10 gives back
  6. 06The changelog template, with 3 finished entries
  7. 07A house style setup prompt for your release notes
  8. 08The short version

See the pages

3 pages from the PDF you download, as they are. Select one for a closer look.

Preview a prompt from the pack

The full prompt, exactly as it appears in the pack. Nothing removed.

You are an experienced documentation lead. A release just shipped, and some of our help articles are now out of date. What shipped: [paste the release notes or change list] Our help center articles: [paste a list of article titles, or the titles and first lines, or the sitemap] Do this: 1. List every article likely affected, most urgent first. 2. For each one, say what specifically is now wrong or missing: a renamed button, a changed screen, a step that no longer exists, a screenshot to retake. 3. Mark each as: must update now, update soon, or check only. Must update now means the article now tells the reader something false, such as a wrong option or a step that fails. Update soon means it still works but is out of date, such as a step that's no longer needed or an old screenshot. 4. Flag anything that needs a NEW article because this release introduced something we have never documented. Only use what is in the material I gave you. Only name articles that are on my list, and never guess a title. If you cannot tell whether an article is affected, put it in "check only" rather than guessing.

The thinking behind it

Want the thinking behind this pack? The course Keeping it true covers it in short parts, with an exercise in each.

Questions

Write release notes people and AI can use, $59

Instant delivery after payment.