Content & Video Skill
AI Influencer Pipeline
Standalone 5-step pipeline
$15
Postmortem Writing
Write effective blameless postmortems with root cause analysis, timelines, and action items.
A complete method for writing blameless postmortems that turn incidents into organizational learning instead of finger-pointing. It supplies the structure: timeline, root cause analysis, detection and response review, impact, lessons, and tracked action items, plus facilitation guidance for the postmortem meeting itself. The outcome is incidents that don't recur, because every contributing factor gets a concrete, owned fix.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Content & Video
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
An incident you do not learn from is an incident you have scheduled to repeat. Outages become blameless, evidence-backed documents with owned action items, all on a seven-day clock.
- Checks the trigger first: severe incidents, customer-facing outages over 15 minutes, data loss, near-misses and novel failure modes all qualify, then locks the cadence of draft within 2 days, meeting by day 5, finalized document and tickets by day 7.
- Builds the minute-by-minute timeline and an executive summary with quantified impact: affected customers, duration, revenue and support load, because vague impact produces vague fixes.
- Digs to root cause with a structured 5 Whys where every why carries an evidence line, and pairs it with the Swiss Cheese model: listing every defense layer whose hole lined up (review gap, missing test, unrepresentative staging, slow alert) instead of hunting one villain.
- Applies the blameless filter to every sentence: names become roles, 'engineer X broke it' becomes 'the pipeline had no canary stage so the bad release ran for 8 minutes', because blame kills the information flow the document exists to capture.
- Maps detection and response gaps explicitly: what fired and when, how long orientation took, where the rollback decision stalled, and where the team simply got lucky.
- Converts findings into Pareto-prioritized action items where the top one or two P0 fixes should prevent 80 percent of recurrence, every item gets a ticket, an owner and a due date (orphan action items are banned), and a quarterly review checks whether closed actions actually stopped repeats.
One power source. 6 lines out.
postmortem-writing · core
core active · 6 lines
- ✓ conducting a post-incident
Conducting a post-incident review after a SEV1 or SEV2
- ✓ writing a standard postm…
Writing a standard postmortem document with timeline and impact
- ✓ running a five whys root…
Running a Five Whys root-cause analysis
- ✓ facilitating a blameless
Facilitating a blameless postmortem meeting
- ✓ producing a quick postmo…
Producing a quick postmortem for a minor incident
- ✓ reviewing patterns across
Reviewing patterns across incidents quarterly
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Fewer repeat incidents because action items are concrete, owned, and tracked to closure
license: perpetual -
Faster, calmer incident reviews with a ready structure and facilitation script
license: perpetual -
Psychological safety that surfaces real causes instead of hidden ones
license: perpetual -
Sharper detection and response over time by analyzing the gaps each incident exposes
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Standard postmortem template with executive summary, timeline, RCA, detection, and impact
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Engineering, SRE, and on-call teams who want incident reviews that prevent recurrence rather than assign blame.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We're a small team without formal SEV levels, is this overkill?
No, it scales down: a dedicated quick postmortem template exists for minor incidents, while the full structure (timeline, RCA, detection review, impact) is reserved for the ones that hurt. You can adopt the blameless framing and Five Whys without ever defining severity tiers.
-
How does writing a document actually prevent incidents from recurring?
The document is the enforcement mechanism: every contributing factor must end in a concrete action item with an owner, a due date, and a ticket link, tracked to closure. The Five Whys template maps each root cause to an improvement type, so fixes target causes rather than symptoms.
-
Will it dig through my logs and find the root cause for me?
No. It structures the analysis: the timeline, the Five Whys, the meeting facilitation, but the investigation itself runs on your telemetry and your engineers' knowledge. It makes the thinking rigorous; it doesn't do the debugging.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.