On-Call Handoffs
Software development skill, available on Zeplik
On-Call Handoffs is a ready-to-run software development skill on Zeplik. Not for live incidents (use incident-response) or postmortems (use postmortem-writing). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The On-Call Handoffs skill loads automatically when your request matches it, or you can invoke it directly by typing /on-call-handoff-patterns in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the On-Call Handoffs skill can do
- Generate complete shift handoff documents from pasted alerts or notes
- Structure active incidents, investigations, deploys, and known issues by section
- Provide async and mid-incident handoff templates for edge cases
- Build rotation onboarding checklists for new on-call engineers
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the On-Call Handoffs skill works
/on-call-handoff-patterns
Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts. The user describes their shift (open incidents, investigations, recent deploys) or pastes alert history and notes; deliver a complete handoff document, process improvements, or an onboarding plan as chat artifacts. For actively managing an incident in progress, use incident-response; for writing up a resolved incident, use postmortem-writing.
When to Use
- Transitioning on-call responsibilities
- Writing shift handoff summaries
- Documenting ongoing investigations
- Establishing on-call rotation procedures
- Improving handoff quality
- Onboarding new on-call engineers
Core Concepts
1. Handoff Components
| Component | Purpose |
|---|---|
| Active Incidents | What's currently broken |
| Ongoing Investigations | Issues being debugged |
| Recent Changes | Deployments, configs |
| Known Issues | Workarounds in place |
| Upcoming Events | Maintenance, releases |
2. Handoff Timing
Recommended: 30 minutes of overlap between shifts.
- Outgoing: 15 min writing the handoff document, 15 min sync call with incoming.
- Incoming: 15 min reviewing the document, 15 min sync call, 5 min verifying alerting setup (fire a test alert and confirm receipt before the outgoing engineer logs off).
Writing a Handoff
When the user asks for a handoff document, collect (or infer from what they pasted): active incidents with severity and current owner, investigations with current hypothesis and next step, deploys and config changes from the shift, known issues with their workarounds, and upcoming maintenance or releases. Every section gets at least one entry or an explicit "none" -- an empty section is not a completed section. Deliver the document as a markdown artifact plus a one-paragraph verbal-style summary for the sync call.
Troubleshooting
Incoming engineer misses a critical issue because the handoff document was incomplete. Use the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit "none"). Make incomplete handoffs a blameless postmortem action item.
A 30-minute sync call is not possible due to timezone gaps. Fall back to the async quick handoff template. Supplement with a short recorded walkthrough or voice memo covering the watch list. Ensure the incoming engineer has a direct contact method for follow-up questions.
The incoming engineer inherits a mid-incident and is immediately overwhelmed. Use the incident handoff template specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions.
Handoff documents are inconsistently formatted across teams. Adopt one shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). Link each handoff from the on-call schedule entry in PagerDuty.
Incoming engineer cannot verify their alerting works before the outgoing engineer logs off. Add a standard step: outgoing engineer fires a test alert and confirms the incoming engineer receives it in PagerDuty and Slack before ending the overlap window.
Templates and Detailed Worked Examples
The full template library (standard shift handoff, async quick handoff, mid-incident handoff, rotation onboarding checklist) lives in references/details.md. Read that file when you need the concrete templates.
Usage
/on-call-handoff-patterns $ARGUMENTS
How to use the On-Call Handoffs skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the On-Call Handoffs skill right away.
Describe your software development task
Ask in plain language, or type /on-call-handoff-patterns to invoke the skill directly. Zeplik recognizes the On-Call Handoffs skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- wshobson
- License
- MIT
Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the On-Call Handoffs skill?
- On-Call Handoffs is a ready-to-run software development skill on Zeplik. Not for live incidents (use incident-response) or postmortems (use postmortem-writing). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use On-Call Handoffs on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /on-call-handoff-patterns in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the On-Call Handoffs skill use?
- Any model you choose. Zeplik works across every model in one chat, so the On-Call Handoffs skill runs on your preferred model for the task.
- Where does the On-Call Handoffs skill come from?
- The On-Call Handoffs skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the On-Call Handoffs skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related software development skills
- .NET BackendBuild ASP.NET Core 8+ backends with EF Core: auth, background jobs, production API patterns
- Advanced Git WorkflowsUse for advanced Git surgery: interactive rebase, cherry-pick, bisect, reflog recovery, and history cleanup before merging. Not for parallel worktree workflows (use using-git-worktrees).
- Adversarial Code ReviewHunt for bugs in code the user shares by assuming defects exist and attacking the code through several distinct lenses, then report severity-ranked findings with evidence. Use for "review this", "what could go wrong", "bug hunt", or pre-merge scrutiny of a change. Read-only, it reports problems and does not rewrite the code. Not for style cleanup (use simplify-code) or for writing new code.
- AI Agent FrameworksUse when building multi-agent systems or agent orchestration -- LangChain/LangGraph, agent team design, task coordination, pipelines. Not for authoring a Zeplik skill (use skill-creator).
- Algolia SearchAdd Algolia search: indexing strategies, React InstantSearch, relevance tuning, search-as-you-type
- Android CI/CDAutomate Android CI/CD to Google Play: keystore, GitHub Secrets, multi-stage release workflow for RN, Flutter, native
More on Zeplik
Try On-Call Handoffs on Zeplik
Every model, one chat. Bring the On-Call Handoffs skill into your next conversation and let the assistant do the work.