Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs.
Passed 17 of 22 test cases with the skill, and 12 of 22 without it.
and 7 more in the full report
5 fixed12 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
When drafting the Technical Details section of a handoff document for a web application, what specific inventory sub-sections must be populated to help the incoming engineer navigate the codebase?
| Checked | Without skill | With skill |
|---|---|---|
| Includes a Key Files section mapping file paths to their specific purposes. | Missed | Passed |
| Includes a Dependencies section describing how each external dependency is utilized. | Missed | Passed |
The instructions your model reads when the skill loads.
You are executing a work handoff between team members or agents.
| Type | When | Key Characteristics |
|---|---|---|
| Planned | End of shift, vacation, role change | Time to prepare docs; opportunity for sync meeting; gradual transition possible |
| Unplanned | Illness, emergency, priority change | Limited prep time; rely on existing docs; may need to reconstruct context |
| Partial | Transfer one piece while retaining other work | Requires clear boundary definition; shared ownership and integration points |
# Handoff: [Task/Project Name]
## Quick Summary
[One paragraph: What is this and current state]
## Current Status
- [ ] Phase: [Design/Implementation/Testing/etc]
- [ ] Progress: [X% complete / Y of Z tasks done]
- [ ] Blockers: [Current blockers, if any]
- [ ] Next Action: [Very next thing to do]
## Context
### What We're Building
[Brief description of the goal/feature]
### Why
[Business/technical justification]
### Key Decisions Made
| Decision | Options Considered | Choice | Rationale |
|----------|-------------------|--------|-----------|
| [D1] | A, B, C | B | [Why B was chosen] |
test cases passed, vs 12 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.