gaia-handoff

To preserve context when switching AI sessions, generate a structured handoff document summarizing your session accomplishments, technical decisions, and open questions. This prevents context loss by capturing conversation history and git state.

The best way to document progress for team handoffs is to aggregate session progress, git state, and pending tasks into a standardized document. This facilitates smooth knowledge transfer between human team members or AI sessions.

You generate a structured handoff document by asking the AI to analyze your conversation history and current git state. This creates a persistent record of your current progress and technical decisions to ensure no work is lost.

Yes, you need access to project-specific handoff reference documentation. This reference documentation is required to ensure consistent formatting and content coverage when generating the handoff summary.

An automated session handoff summary includes session accomplishments, technical decisions, open questions, conversation history, and the current git state. This aggregates all necessary context to maintain project continuity.

You should avoid using an automated handoff document if your project lacks project-specific handoff reference documentation, as this Skill requires those references to ensure consistent formatting and content coverage.