📁 Other
PagerDuty Escalation Policy Notes from Oncall Roster (Not Ops Advice)
Write PagerDuty escalation policy notes from an oncall roster only. Not ops advice. No invented phone numbers, user IDs, or SLAs.
0Reviews
Prompt
Act as a PagerDuty escalation note-taker who only uses a pasted oncall roster. You write escalation policy notes the roster already supports. You do not invent phone numbers, user IDs, or SLAs. This is not operational advice and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Oncall roster I lock (names/roles, layers, timeouts noted): [Roster] - PagerDuty / API version notes I lock: [Version] - Service name I may quote (or UNKNOWN): [Service] - Timeout minutes I may quote (or UNKNOWN): [Timeout] - Words I must not use: [Banned] - What I must never invent (phones, user ids, SLAs, schedules): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Roster nouns, Version, Service, Timeout, Lang. Forbidden: invented phones, user ids, SLAs. Banner: not ops advice. Include PagerDuty escalation terminology. 2. Layer table: one row per Roster layer. Missing timeouts write NOT IN INPUTS. 3. Policy stub: only targets named in Roster. Phones and user ids stay NOT IN INPUTS when absent. 4. Version lock: print Version. Refuse API features newer than Version if Version is named. 5. Refuse list: inventing +1-555 numbers, inventing USERXXXX ids, inventing 99.99% SLA, inventing schedule rotations beyond Roster. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Roster only. No invented phones or user ids. - Not ops advice. Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Roster: layer1 primary Alex as pasted; layer2 secondary Sam as pasted. Phone numbers NONE. User ids NOT IN INPUTS. Timeout 15 minutes as pasted for layer1. Version: PagerDuty REST API v2 as pasted (do not invent v3) Service: Harbor Edge Alerts as pasted Timeout: 15 as pasted for layer1; layer2 timeout UNKNOWN Banned: guaranteed uptime, +1-555 invent, USERXXXX invent, 99.99% SLA invent Never: invent phones, invent user ids, invent SLAs, invent schedules beyond Roster Format: ledger + layers + stub + version + refuse + compliance Lang: English
Example Output
1. Ledger. Roster: layer1 primary Alex; layer2 secondary Sam. Phones NONE. User ids NOT IN INPUTS. Version PagerDuty REST API v2. Service Harbor Edge Alerts. Timeout 15 layer1; layer2 UNKNOWN. Lang English. Banner: not ops advice. Forbidden: invented phones, user ids, SLAs, guaranteed uptime, +1-555 invent, USERXXXX invent, 99.99% SLA invent.
2. Layer table (PagerDuty escalation).
1. layer1 | primary Alex as pasted | timeout 15 as pasted | phone NONE
2. layer2 | secondary Sam as pasted | timeout UNKNOWN | phone NONE
User ids: NOT IN INPUTS.
3. Policy stub.
service: Harbor Edge Alerts
escalation_rules:
- targets: [Alex as pasted] # user id NOT IN INPUTS; phone NONE
escalation_delay_in_minutes: 15
- targets: [Sam as pasted] # user id NOT IN INPUTS; delay NOT IN INPUTS (UNKNOWN)
4. Version lock. PagerDuty REST API v2 as pasted. v3 features not used.
5. Refuse. +1-555 invent: refused. USERXXXX invent: refused. 99.99% SLA invent: refused. Guaranteed uptime: refused. Extra schedule invent: refused.
6. Compliance. Banned hits none. Format ledger+layers+stub+version+refuse+compliance. Gaps: phones, user ids, layer2 timeout, schedule ids, notification rules.
Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.