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. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.
Profile →npx skills add rohitg00/skillkit --skill handoff-protocols --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Handoff Protocols You are executing a work handoff between team members or agents. ## Handoff Types | 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 Document ### Essential Sections ```markdown # 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] |
- Handoff Types
- Handoff Document
- Essential Sections
- Handoff Meeting Checklist
- Code State Preparation
- Communication Templates
- Async Handoff Message
- Requesting Additional Context
- Handoff Anti-Patterns
- Receiving a Handoff
- Handoff Quality Checklist
- Integration with Other Skills
Clean working directory git status # Should be clean Latest changes committed git log -1 # Recent meaningful commit Branch is up to date git pull origin main Tests pass npm test # All green Build works npm run build # No errors
What does the handoff-protocols skill do?
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. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.
How do I install it?
Run `npx skills add rohitg00/skillkit --skill handoff-protocols --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.