DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
On Call Handoff Patterns
Master on-call shift handoffs with context transfer, escalation procedures, and documentation.
A complete on-call shift transition system that prevents context loss between engineers. It ships ready-to-use handoff document templates, sync-meeting agendas, and escalation matrices so the incoming engineer never starts a shift blind. Built on a measurable principle: the receiving engineer should know what the outgoing one knew, every time.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Context that lives in one engineer's head pages two engineers at 3am. This shift-boundary routine forces that context onto paper, then proves the transfer on a sync call.
- Before the shift starts: verify access end to end (VPN, kubectl, log aggregator, PagerDuty routing with a test alert), review the last two weeks of incidents and skim the critical runbooks.
- The outgoing engineer fills five mandatory handoff sections: active incidents, ongoing investigations, recent changes, known issues with workarounds, upcoming events. Writing 'none' is allowed, leaving a section blank is not.
- A 30-minute overlap runs the handoff: 15 minutes writing the document, 15 minutes on a sync call where the incoming engineer repeats each section back, proving the context actually transferred.
- The incoming engineer completes a confirm checklist before taking the pager: PagerDuty routes to them, Slack notifications fire, dashboards open, escalation paths are known.
- During the shift every alert follows the escalation matrix: issue type maps to a first and second escalation contact, and 30 minutes without a diagnosis means escalate, not hero.
- After the shift: handoff document completed, investigation tickets updated, postmortems filed for incidents, and flaky alerts get a ticket instead of being muted.
One power source. 6 lines out.
on-call-handoff-patterns · core
core active · 6 lines
- ✓ writing a full shift han…
Writing a full shift handoff document
- ✓ handing off mid-incident
Handing off mid-incident without dropping context
- ✓ quick async handoffs over
Quick async handoffs over chat
- ✓ onboarding a new on-call
Onboarding a new on-call engineer
- ✓ standing up an on-call r…
Standing up an on-call rotation from scratch
- ✓ running a 15-minute hand…
Running a 15-minute handoff sync call
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
-
Cuts incident response time by transferring complete context, not fragments
license: perpetual -
Removes 'who do I page?' hesitation with a pre-built escalation threshold matrix
license: perpetual -
Reduces on-call burnout through clear checklists and alert-fatigue discipline
license: perpetual -
Catches weak defense layers (flaky alerts, known issues) before they cause incidents
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Three handoff templates: full shift, quick async, and mid-incident
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.
For SRE and platform teams who run on-call rotations and want every shift transition to be reliable instead of a coin flip.
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 page through PagerDuty and chat in Slack, does this assume a specific toolchain?
No tool lock-in: the handoff templates, checklists, and escalation matrices are plain documents that work over any paging or chat stack. The quick async template is even designed to be pasted straight into a chat thread.
-
How does it actually stop context from getting lost between shifts?
Every handoff document forces five mandatory sections: Active Incidents, Investigations, Recent Changes, Known Issues, and Upcoming Events, so nothing lives only in the outgoing engineer's head. Three template variants (full shift, quick async, mid-incident) match the structure to how much time you have.
-
Will it configure my monitoring or fix flaky alerts?
No. It transfers and documents what your monitoring already shows; flaky alerts and weak defense layers get surfaced in the Known Issues section so someone owns them, but the skill never touches your alerting config itself.
-
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.