📁 Other
Sentry Issue Alert Project Checklist from Ops Notes (No Invented Uptime Percents)
Compile a Sentry issue-alert-project checklist from pasted ops notes only. No invented uptime percents, latency ranks, or ops scoreboards. Not a live Sentry sync.
0Reviews
Prompt
Act as a Sentry issue-alert-project checklist engineer who only uses pasted ops notes. You compile an issue-alert-project checklist the notes already support. You do not invent uptime percents, latency ranks, ops scoreboards, or guaranteed SLO claims. This is not a live Sentry sync, not a Datadog invent, and not SRE consulting advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops notes I lock (issue stubs, alert cues, project fragments): [OpsNotes] - Sentry org or version notes I lock: [Version] - Org or workspace label I may quote (or UNKNOWN): [OrgLabel] - Issue titles already present (or UNKNOWN): [IssueTitles] - Alert cues already present (or UNKNOWN): [AlertCues] - Project cues already present (or UNKNOWN): [ProjectCues] - Environment cues already present (or UNKNOWN): [EnvironmentCues] - Words I must not use: [Banned] - What I must never invent (uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OpsNotes nouns, Version, OrgLabel, IssueTitles, AlertCues, ProjectCues, EnvironmentCues, Lang. Banner: not SRE consulting advice; not a live Sentry sync. Forbidden: invented uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims. 2. Issue-alert-project checklist: one checkbox row per IssueTitles entry. Attach only AlertCues and ProjectCues named beside that issue in OpsNotes. Missing alert or project write NOT IN INPUTS. 3. Environment sketch: for each EnvironmentCues entry, list issues that name it. Do not invent a 99.97% uptime claim if absent. 4. Org caution block: quote OrgLabel and Version only. Release packs not in OpsNotes stay NOT IN INPUTS. 5. Refuse list: inventing 99.97% uptime percents, inventing latency ranks, inventing ops scoreboards, inventing guaranteed SLO claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print issue and alert counts from OpsNotes only. Format as Format. Constraints: - Issue-alert-project checklist from OpsNotes only. No invented uptime percents. - Honor Version. No emojis. Not a live Sentry dashboard. Not SRE consulting advice.
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
OpsNotes: issue title Harbor Quay Timeout Issue as pasted alert cue alert:pier-p1 as pasted project cue project:quay-api as pasted; issue title Quay Storm NullRef Issue as pasted alert cue alert:storm-warn as pasted. Uptime invent NONE. Latency invent NONE. Version: Sentry as pasted (do not invent unreleased AI SLO coach) OrgLabel: Cedar Pier observability org as pasted IssueTitles: Harbor Quay Timeout Issue as pasted; Quay Storm NullRef Issue as pasted. Release pack UNKNOWN. AlertCues: alert cue alert:pier-p1 as pasted for Harbor Quay Timeout Issue; alert cue alert:storm-warn as pasted for Quay Storm NullRef Issue. Rule pack UNKNOWN. ProjectCues: project cue project:quay-api as pasted for Harbor Quay Timeout Issue; Quay Storm NullRef Issue project NOT IN INPUTS. EnvironmentCues: environment cue env:prod-east as pasted for Harbor Quay Timeout Issue. Owner pack UNKNOWN. Banned: 99.97% uptime, latency rank #1, guaranteed ops scoreboard Never: invent uptime percents, invent latency ranks, invent ops scoreboards, invent guaranteed SLO claims Format: ledger + issue-alert-project checklist + environment sketch + org caution + refuse + compliance Lang: English
Example Output
1. Ledger. OpsNotes: issue title Harbor Quay Timeout Issue + alert cue alert:pier-p1 + project cue project:quay-api; issue title Quay Storm NullRef Issue + alert cue alert:storm-warn. Uptime invent NONE. Latency invent NONE. Version Sentry. OrgLabel Cedar Pier observability org. IssueTitles Harbor Quay Timeout Issue; Quay Storm NullRef Issue. AlertCues alert:pier-p1 for Harbor Quay Timeout Issue; alert:storm-warn for Quay Storm NullRef Issue. ProjectCues project:quay-api for Harbor Quay Timeout Issue; Quay Storm NullRef Issue project NOT IN INPUTS. EnvironmentCues env:prod-east for Harbor Quay Timeout Issue. Owner pack UNKNOWN. Lang English. Banner: not SRE consulting advice; not a live Sentry sync. Forbidden: invented uptime percents, latency ranks, ops scoreboards, guaranteed SLO claims, 99.97% uptime, latency rank #1, guaranteed ops scoreboard. 2. Issue-alert-project checklist. [ ] Harbor Quay Timeout Issue | alert alert:pier-p1 as pasted | project project:quay-api as pasted. [ ] Quay Storm NullRef Issue | alert alert:storm-warn as pasted | project NOT IN INPUTS. Rule pack not attached. Release pack not added. 3. Environment sketch. environment cue env:prod-east | issue Harbor Quay Timeout Issue as pasted. Quay Storm NullRef Issue environment | NOT IN INPUTS. Uptime percents NOT IN INPUTS so do not invent 99.97% uptime. Second environment cue not invented. 4. Org caution. OrgLabel Cedar Pier observability org. Version Sentry. Owner pack UNKNOWN. Do not invent SLO claim packs. 5. Refuse. 99.97% uptime percents: refused. latency ranks: refused. ops scoreboards: refused. guaranteed SLO claims: refused. Unreleased AI SLO coach: refused. 6. Compliance. Banned hits none. Issues 2. Alerts named 2. Format ledger+issue-alert-project checklist+environment sketch+org caution+refuse+compliance. Gaps: Quay Storm NullRef Issue project, Quay Storm NullRef Issue environment, Rule pack, Release pack, Owner pack. 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.