Design
Error Message Rewrite
Replace error sludge with clear recovery paths.
Use when
Your product exposes raw provider errors, stack traces, or dead-end messages.
Cadence
When users hit confusing errors
Verification
Every in-scope user-visible error is accounted for, rewritten or blocked, and verified in a reachable state.
Advanced specStructured loop spec
| Field | Value |
|---|---|
| Name | Error Message Rewrite |
| Category | Design |
| Trigger | When users hit confusing errors |
| Objective | Replace error sludge with clear recovery paths. |
| Allowed inputs | Relevant files, source notes, logs, tests, screenshots, metrics, or task state for this loop |
| Allowed actions | Define the exact scope, source of truth, and approval boundary.; Inspect current state and rank the highest-risk gap.; Make one small, reversible improvement.; Run the stated verification and record evidence.; Stop on success, budget, no progress, or approval required. |
| Verification | Every in-scope user-visible error is accounted for, rewritten or blocked, and verified in a reachable state. |
| Stop condition | Stop when the verifier passes, the budget is exhausted, no progress is made, a blocker appears, or approval is required. |
| Budget | Set a time, turn, token, retry, file, or dollar cap before running the loop. |
| Approval boundary | Human approval required before publishing, sending, deleting, spending, changing accounts, touching production, or making reputational/legal/financial commitments. |
| Safe output | Draft, report, checklist, table, or approval-gated recommendation |
| Works with | Claude, ChatGPT, Gemini, any tool-using AI assistant |
RunbookSteps
- Define the exact scope, source of truth, and approval boundary.
- Inspect current state and rank the highest-risk gap.
- Make one small, reversible improvement.
- Run the stated verification and record evidence.
- Stop on success, budget, no progress, or approval required.
Copy promptPrompt
Run the Error Message Rewrite loop. Use it when Your product exposes raw provider errors, stack traces, or dead-end messages. Work in bounded iterations: inspect current state, choose the highest-risk gap, make one reversible improvement, verify it, and record evidence. Stop when Every in-scope user-visible error is accounted for, rewritten or blocked, and verified in a reachable state. or when blocked, budget exhausted, or approval is required.