Deprecation Notice Drafter
API change in — deprecation notice with migration path out.
role devdraftingfollow-upreportingintermediatefree planorigin selfupdated 2026-10-24
01Requires
what are these? skills vs memories vs plugins →
notice format — your deprecation notice sections (what/why/when/migration) memoriestone rules — direct, no apology-theater, dates always explicit memoriesthe change details pasted in — PR description, changelog entry, or API diff permissions
02Setup — 5 steps
- 01Create the agent. Open Grok Bot → Agents → New Agent, name it
deprecation-drafter. - 02Paste the prompt. Copy the prompt below into the system field.
- 03Set two memories. Memory one: your notice format. Memory two: tone rules and your deprecation policy defaults.
- 04Paste the change. Give it the PR/changelog/API diff describing what's going away.
- 05Fill the dates. It drafts the structure — you fill sunset date and migration deadline. Never let it invent them.
03Prompt
agent prompt · system field
You draft API deprecation notices. From the change details below output:
- What is changing: the endpoint/field/behavior, one line
- Why: the honest reason in plain words — 'cleaner API' is not a reason, cite the real one
- Timeline: sunset and migration-deadline placeholders [DATE] — never invent dates
- Migration: concrete before/after steps from the diff, code-shape included if visible
- Who's affected: which integrators if determinable, else 'anyone calling X'
Tone per memory: direct, no apology-theater, one channel for questions.
04Config
| name | example | description |
|---|---|---|
format memory | "what / why / timeline / migration / affected" | Your deprecation notice section order |
policy defaults | "90-day minimum notice, changelog + email" | House rules the draft should encode |
05Sample output
Example output shape: 5-section notice with [DATE] placeholders, 3-step migration, affected-scope line.
06Pitfalls
It invents dates. Dates are [DATE] placeholders by prompt design — a draft with real-looking dates you didn't set is a failure, regenerate.
Migration glosses breaking details. If the diff shows a renamed field with different semantics, the draft MUST show before/after — check that section hardest.
07Variants
- sunset-email — same draft shortened to the customer-facing email version
- changelog-line — one-liner version for the changelog, linking the full notice
- internal-first — drafts the internal heads-up to support/CS before the public notice
08FAQ
Can it send the notice to customers?
It drafts text only — notices go out through your real channels. A deprecation email nobody approved is a support incident.
Does it handle breaking vs non-breaking?
Say which it is in the input; the draft structure differs (breaking changes get the migration section up top).
Minimum viable input?
A one-line 'endpoint X is going away' plus the new path — the prompt structures the rest, you add dates.
09Run it — or hand it to us
Tell us what you want Grok Bot to do: hello@awayhand.com
10Related templates
Release Notes Drafter
Merged PRs in — readable release notes out, weekly.
dev · 2026-10-24
Bug Report Structurer
Messy bug reports in, structured tickets out.
dev · 2026-10-24
↩Also referenced by
unofficial template from a community-run directory — not affiliated with the product's vendor · disclaimer
New templates as they land. No hype.
Email to subscribe →