Rollback Strategy Planner
Defining severity levels with response time targets turns vague 'something is wrong' situations into structured incident response.
I manage {{prompt_count}} production prompts across {{product_areas}}. I need a rollback strategy for when prompt updates cause issues.\n\nCurrent process: {{current_process}}\n\nDesign a rollback protocol that covers:\n1. Detection: how to identify that a prompt update is causing problems (metrics, alerts, user reports)\n2. Assessment: severity classification (P0-P3) with response time targets\n3. Rollback execution: step-by-step procedure for reverting to the last known good version\n4. Communication: templates for notifying stakeholders\n5. Post-mortem: analysis template for understanding what went wrong\n6. Prevention: checklist to run before deploying future prompt updates
Variables to customize
Why this prompt works
Defining severity levels with response time targets turns vague 'something is wrong' situations into structured incident response.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Forcing the agent to plan before acting prevents premature execution and wasted steps. Explicit dependency mapping enables parallel execution and catches logical gaps early.
Tool Selection AgentThe ReAct pattern (Reason + Act) creates an explicit reasoning trace that improves tool selection accuracy. The error-handling rule prevents infinite retry loops.
Prompt CompressorExplicitly requiring all functional requirements to be preserved prevents the model from over-compressing and losing critical instructions.
Memory Management AgentExplicit memory read/write instructions create agents that improve over time. Categorization keeps memories organized, and the deduplication rule prevents context bloat.