handoff-protocols

Featured

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.

Data & Documents 745 stars 68 forks Updated 1 months ago Apache-2.0

Install

View on GitHub

Quality Score: 98/100

Stars 20%
96
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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] | 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...

Details

Author
rohitg00
Repository
rohitg00/skillkit
Created
4 months ago
Last Updated
1 months ago
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

handoff

Hand off to a fresh Claude session. Use when context is full, you've finished a logical chunk of work, or need a fresh perspective. Work continues from hook.

24,081 Updated today
gastownhall
Testing & QA Solid

spec-flow

Spec-driven development workflow. Interactive phase-by-phase confirmation from proposal to implementation. Trigger: 'spec-flow', 'spec mode', 'need a plan', 'structured development', 'write a spec', 'feature spec', 'technical spec', '需求文档', '技术方案', '任务拆解', '规格驱动', '写个方案', '做个规划', '结构化开发', 'plan this feature', 'break this down', 'design doc'. Creates .spec-flow/ directory with proposal, requirements, design, and tasks.

31 Updated 3 months ago
echoVic
Data & Documents Solid

short-term-memory

Maintain working context via current-context.md - read before and update after every response with timestamp YYYYMMDD-HHMMSS

21 Updated 2 months ago
Malaiac
Web & Frontend Solid

brainstorming-design-docs

Guides a raw idea through structured brainstorming into a fully fleshed-out design document formatted for SharePoint. Asks clarifying questions one at a time, proposes alternative approaches with trade-offs, builds the design incrementally with user approval, then delivers a complete SharePoint-ready document. Use when a user wants to develop an idea, proposal, project plan, or initiative into a structured doc. Triggers include "help me think through this", "turn this idea into a design doc", "I want to design a new [process/project/feature/solution]", "brainstorm this with me", or when a user describes a rough idea and wants to make it concrete.

56 Updated 3 weeks ago
zrosenfield