aegis-handover-writer

Generate dated session-end handover files and update the HANDOVER-LATEST.md symlink.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill aegis-handover-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aegis-handover-writer
Source: https://github.com/RideMatch1/a.e.g.i.s/tree/main/packages/skills/skills/foundation/aegis-native/aegis-handover-writer
Command: npx skills add https://github.com/RideMatch1/a.e.g.i.s --skill aegis-handover-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes a structured session-end handover file at .claude/handover/HANDOVER-YYYY-MM-DD-<topic>.md and updates HANDOVER-LATEST.md symlink to seed the next agent with complete context, enabling seamless continuation across sessions.

Core Features & Use Cases

  • Generates a dated handover file with key sections (Status, Metrics, Files Changed, Skill Changes, Open items, Recommendations) and maintains HANDOVER-LATEST.md as the active pointer.
  • Supports continuous updates during long-running builds by appending or overwriting depending on today’s file state to preserve history.
  • Integrates with git and .aegis state to tailor the handover for the current phase and involved skills, ensuring the next agent starts with the right context.

Quick Start

Use aegis-handover-writer to create and update today's HANDOVER, then verify HANDOVER-LATEST.md points to the new file.

Frequently Asked Questions about aegis-handover-writer

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

FAQPage Schema
How do I automate session handover documentation for autonomous AI agents?

Update session handover documents by appending or overwriting today's file to preserve history while maintaining the latest pointer. This supports continuous updates during long-running builds by keeping the handover workflow consistent and the active context current.

What is a session handover file and when do I need it for state management?

Integrate handover generation with git and state directories to tailor the handover for the current phase and involved skills. This ensures the next agent starts with the right context by automatically capturing commits and state changes specific to the workflow.

What's the best way to maintain a latest handover symlink for continuous workflow context?

Maintain a latest handover symlink by automatically updating the pointer to the newest dated markdown file after generation. This guarantees the next autonomous agent always reads the most recent session context, enabling seamless continuation across sessions.

Does session handover generation work with git state for multi-phase builds?

Yes, session handover generation integrates with git and state directories to tailor the document for the current phase and involved skills. This captures commits and state changes to ensure the next agent starts with the right context for the build.