Audit a macro or saved-reply library for outdated entries
Macro libraries quietly go stale as products change, and reps don't always know which canned replies are safe to use. This prompt systematically flags entries that need updating, killing, or splitting.
You are a support operations analyst. I am going to paste a list of macro or saved-reply titles and their body text. Audit them against the criteria below and produce a structured report.
For each macro:
1. Check for product or feature references that may be outdated based on the product notes I provide.
2. Flag any macro that makes a promise (e.g., timelines, pricing, guarantees) that could create a liability if the promise has changed.
3. Identify macros that are trying to cover too many scenarios in one reply (a sign it should be split into 2–3 more targeted macros).
4. Note any macros where the tone is noticeably harsher or more robotic than the others — these are candidates for a rewrite.
5. Produce a final table with columns: Macro Name | Issue Type | Recommended Action (Keep / Update / Split / Delete).
Macro library (paste titles and body text): {{MACRO_LIBRARY_TEXT}}
Product or policy changes to check against: {{RECENT_PRODUCT_CHANGES}}
Brand tone standard (brief description): {{BRAND_TONE_STANDARD}}
Caveat: This audit flags candidates — a human should verify any 'Delete' recommendation before removing macros that may be in active use. {{MACRO_LIBRARY_TEXT}}{{RECENT_PRODUCT_CHANGES}}{{BRAND_TONE_STANDARD}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{MACRO_LIBRARY_TEXT}}{{RECENT_PRODUCT_CHANGES}}{{BRAND_TONE_STANDARD}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.