
Tech & Dev Prompt Library
Developers, tech leads and solo builders who want prompts that survive real code.




Prompt setAI Coding & Development Prompts
Turns a messy incident channel into a reviewable blameless postmortem without a single made-up timestamp.
$9· one file, yours to keep
Yours to keep · instant download
Or all of them, $6.99/mo
Incident Report & Postmortem Generator and 2,500+ other specialists, in your AI. Ask for any of them by name.
7 days free, then $6.99/mo · cancel anytime
One file
All-in-one
30-day money-back · secure checkout by Stripe
================================================================================ KISSMYSKILLS.COM AI Incident Report & Postmortem Generator Prompt Pack - Instant Use ================================================================================ WHAT YOU JUST BOUGHT -------------------------------------------------------------------------------- A copy-paste prompt pack that turns the mess left after an incident - raw notes, Slack or Teams exports, pager alerts, ticket comments, a half-written timeline - into the documents people actually need afterwards: a blameless
Here is our #inc-checkout Slack export (CET) and the PagerDuty alert list (UTC). Build the timeline in UTC, then write a blameless postmortem, severity SEV2 on our scale.
You get: a UTC timeline table with source per line and impact start, detect, mitigate and resolve marked → [TIME NEEDED] wherever the export has no time → time to detect and mitigate with the arithmetic shown → contributing factors labelled CONFIRMED or HYPOTHESIS → what went well, poorly and lucky → action items with [OWNER NEEDED] and [DATE NEEDED] until you fill them → a customer status update and a 200-word executive summary.
It gives you 38 prompts and 2 master formulas that turn raw incident material into finished documents: a UTC timeline, detection and response metrics, impact and error budget, causal analysis, a blameless postmortem, action items with owners and dates, status page updates, an executive summary, a review meeting agenda, and incident reports for workplace, safety and IT security events.
Dragan - Incident Responder and Petronella - Incident Response Analyst help while a security incident is being handled and investigated. Cosimo - Runbook & SOP Writer writes procedures in advance. This pack works after any incident, software or not: it turns what happened into the postmortem, the incident report, the customer update and the action list.
Every prompt tells the AI to use only facts in your material. Missing times, impact numbers, owners and dates come back as placeholders like [TIME NEEDED] or [OWNER NEEDED], causes are labelled CONFIRMED or HYPOTHESIS, and revenue is never estimated. Search the output for NEEDED before you publish it.
Yes. Paste your template headings and your severity scale at the start of the chat and the prompts fill your structure. If you have no scale, prompt 31 proposes an example SEV1-SEV4 scale to adapt, clearly marked as an example rather than a standard.
Download your .skill file from the order email or your account. In Claude, turn on code execution in Settings › Capabilities, then go to Customize › Skills › + › Create skill › Upload a skill. Start a new chat and ask for the specialist by name.