session-handoff

To document an AI assistant session state for a seamless handoff, invoke the skill at session end to capture project memory, decisions, and open questions into a single handoff.md file, overwriting any prior version to prevent state drift.

The best way to capture project context and pending tasks is generating a concise handoff document that strictly derives outcomes, recent commits, and open questions from the current session context, ensuring the next session resumes work without losing critical state.

Memory management preserves task IDs and statuses by reading prior handoff documents before generating a new one. This ensures continuity by carrying over existing identifiers and tracking states into the newly captured session context.

Yes, you can overwrite a previous handoff document without losing critical project decisions because the skill reads the existing file to preserve task IDs, statuses, and prior context before creating a fresh capture of the current session state.

You need to generate a handoff.md file for your research session when you are ready to end the current interaction and want to ensure seamless resumption by recording outcomes, pending tasks, and context for the next session.

No, generating a session handoff requires no specific dependencies or external components. The skill operates independently to read your session context and output a complete handoff.md file directly into your project root.