rohitg00/handoff-protocols
packages/core/src/methodology/packs/collaboration/handoff-protocols/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add rohitg00/skillkit handoff-protocolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 12, 2026, 2:01 AM16.8s1 file scanned
SKILL.md
- name:
- handoff-protocols
- description:
- 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.
- version:
- 1.0.0
- difficulty:
- beginner
- estimatedTime:
- 10
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
# 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] |
### Open Questions
- [Question 1]
- [Question 2]
## Technical Details
### Architecture/Design
[Relevant diagrams or links]
### Key Files
- `path/to/file1.ts` - [Purpose]
- `path/to/file2.ts` - [Purpose]
### Dependencies
- [Dependency 1]: [How it's used]
- [Dependency 2]: [How it's used]
## Current State of Code
### What's Complete
- [x] [Completed item 1]
- [x] [Completed item 2]
### In Progress
- [ ] [In progress item] - [Current state]
### Not Started
- [ ] [Pending item 1]
- [ ] [Pending item 2]
## Known Issues
### Active Issues
- [Issue 1]: [Description and current understanding]
### Workarounds in Place
- [Workaround 1]: [Why it exists, how to remove it]
## How to Continue
### Immediate Next Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Things to Watch Out For
- [Gotcha 1]
- [Gotcha 2]
### Who to Contact
- [Name/Team] for [Topic]
- [Name/Team] for [Topic]
## Resources
- [Link to design doc]
- [Link to requirements]
- [Link to related PRs]
Handoff Meeting Checklist
If doing a live handoff:
Before Meeting:
- [ ] Prepare handoff document
- [ ] Ensure code is in clean state
- [ ] List questions you anticipate
During Meeting:
- Walk through handoff document
- Show current state of code
- Demo any working functionality
- Explain key decisions and trade-offs
- Highlight risks and unknowns
- Answer questions
- Verify recipient understands
After Meeting:
- [ ] Share access to all resources
- [ ] Offer availability for follow-up questions
- [ ] Confirm handoff complete
Code State Preparation
Before handing off, ensure:
# 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
Leave the code in a state where:
- It compiles/runs
- Tests pass
- No work-in-progress changes uncommitted
- Clear commit messages explain recent changes
Communication Templates
Async Handoff Message
Hi [Name],
I'm handing off [Task/Project] to you. Here's what you need to know:
**Status:** [Current state in one sentence]
**What I've Done:**
- [Accomplishment 1]
- [Accomplishment 2]
**Next Steps:**
1. [Immediate next action]
2. [Following action]
**Watch Out For:**
- [Important gotcha]
**Resources:**
- Handoff doc: [link]
- Code: [branch name]
- Related PR: [link]
Let me know if you have questions!
Requesting Additional Context
Hi [Name],
I'm picking up [Task] from your handoff. A few clarifications:
1. [Specific question 1]
2. [Specific question 2]
Also, I noticed [observation]. Was that intentional?
Thanks!
Handoff Anti-Patterns
Avoid: brain dumps of unstructured info, disappearing after handoff, omitting critical context, and handing off code in a broken state.
Receiving a Handoff
When you receive work:
- Read documentation before asking questions
- Acknowledge receipt to confirm handoff
- Identify gaps in your understanding
- Ask focused questions about specific unclear points
- Verify you can build/run the current state
- Document any additional context you discover
Handoff Quality Checklist
For the giver:
- [ ] Documentation is complete and current
- [ ] Code is in clean, working state
- [ ] All access/permissions transferred
- [ ] Key contacts introduced
- [ ] Questions answered or noted
- [ ] Availability for follow-up communicated
For the receiver:
- [ ] Documentation reviewed
- [ ] Can build and run the code
- [ ] Understand current state
- [ ] Know next steps
- [ ] Know who to contact
- [ ] No blocking questions
Integration with Other Skills
- structured-review: Get review before handoff if work is complete
- parallel-investigation: Handoff individual threads
- planning/task-decomposition: Reference task breakdown in handoff
Related Skills
rohitg00/find-skills
tools
VerifiedTrustedCommunity
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI. Supports browsing official partner collections (Anthropic, Vercel, Supabase, Stripe, and more) and community repositories, searching by domain or technology, and installing specific skills from GitHub. Use when the user wants to find, browse, or install new agent skills, plugins, extensions, or add-ons; asks 'is there a skill for X' or 'find a skill for X'; wants to explore a skill store or marketplace; needs to extend agent capabilities in areas like React, testing, DevOps, security, or APIs; or says 'browse skills', 'search skill marketplace', 'install a skill', or 'what skills are available'.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/test-patterns
development
VerifiedTrustedCommunity
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/red-green-refactor
development
VerifiedTrustedCommunity
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.
757SKILL.mdUpdated Apr 12, 2026
rohitg00/testing-anti-patterns
development
VerifiedTrustedCommunity
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
757SKILL.mdUpdated Apr 12, 2026