skills.rest
alexica00
alexica00COMMUNITY
Explore all skills by this author →
GitHub

handoff-update

Update existing handoff documents with section-specific merge rules.

Updated May 30, 2026
Search Tags:#automation#workflow#documentation#merge#handoff#file-management#session-progress
One-click install
npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill handoff-update-alexica00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-update
Source: https://github.com/alexica00/claude-code-ultimate-guide/tree/main/examples/skills/handoff-update
Command: npx skills add https://github.com/alexica00/claude-code-ultimate-guide --skill handoff-update-alexica00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handoffs between teams or sessions often get out of sync as progress evolves. This skill ensures an existing handoff document is updated consistently, preserving history while incorporating new progress.

Core Features & Use Cases

  • Applies distinct merge rules per section: append for Work Done, replace for Status and Next Steps, and merge for Files and Discoveries.
  • Creates a new handoff if no source exists.
  • Works with argument-based file resolution or session history.

Quick Start

Provide the target handoff path as an argument and run the update to merge progress.

Frequently Asked Questions about handoff-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate updating an existing handoff document with new session progress?▼

The skill resolves the target handoff file using a provided path argument, searches session history, or generates a default file path to locate and update the correct handoff document automatically.

What happens to my handoff documentation if no source file is found during the update?▼

If no source handoff document is found, the skill falls back to creating a new handoff document from scratch, ensuring session progress is documented even without a pre-existing file.

What is the best way to preserve progress history while updating team handoff documents?▼

To preserve history during handoff updates, apply an append-only rule to Work Done sections while replacing Status and Next Steps, ensuring past progress is retained while current status stays accurate.

Can I merge session progress into specific documentation sections without overwriting entire files?▼

Yes, you can merge session progress into specific handoff sections using distinct rules: append-only for Work Done, replace for Status and Next Steps, and merge for Files and Discoveries without overwriting the entire file.

Related Skills

Explore More Content & Communication Skills→
ccfccf

event-store-design

Design event stores with schemas, versioning, and append-only streams.

Community
Intermediate
elithrarelithrar
190

summarize-work

Analyze session history and git state to generate structured commit-message summaries.

Community
Basic
BeltDoorBeltDoor

checkpoint

Save active development session progress with git commits and recovery context.

Community
Advanced
danievanzyldanievanzyl
1

wrap-up

Automate post-merge PR confirmation, main updates, and worktree cleanup.

Community
Intermediate