Write a reusable prompt with replaceable inputs. Submit your prompt and one test output for this example.
Task: Create a prompt that produces a safe first-response runbook from a service description.
Example input: A fictional file-preview service has a web frontend, job queue, preview workers, and object storage. Alerts report growing queue depth and slower previews. Frontend requests still succeed. Operators can read service health, queue age, worker logs, recent change records, and storage error counts. They cannot restart services, scale workers, change permissions, replay jobs, or delete data without an incident lead’s approval. Some logs may contain customer filenames.
Constraints:
- Start with read-only checks and preserve timestamps.
- Keep customer filenames and identifiers out of broad status updates.
- Separate observations, hypotheses, escalation criteria, and approval-required actions.
Required output from your prompt: A numbered first-15-minutes runbook, an evidence collection template, and a short internal status-update template with placeholders.
Success checks:
- The runbook checks queue age and worker processing evidence.
- No mutating action appears as an immediately authorized step.
- The status template avoids guessing cause or recovery time.
- Escalation is tied to an observable condition rather than an unexplained urgency label.