FG-0702 Session Handoff Protocol
Description
Define a structured format for transferring context between sessions. Every session end is a potential knowledge cliff: if context isn't captured, the next session starts from scratch. The Session Handoff Protocol creates a standardized 'shift change brief' that captures: what was accomplished, what's in progress, what decisions are pending, and what context the next session needs to continue seamlessly.
Implementation
Create a handoff template with 4-6 fields: Accomplished (what shipped), In Progress (what's partially done), Pending Decisions (what needs resolution), Context (what the next session needs to know), Blockers (what's preventing progress). Complete the handoff at every session end. Store handoffs where the next session will read them during context recovery.
Success Indicators
- Next-session startup time is minimized by quality handoffs
- No work is lost between sessions due to context gaps
- Handoffs capture enough context for a different agent to continue the work
- Handoff quality is consistent across sessions
Failure Modes
- Handoffs skipped under time pressure: exactly when they're most needed
- Handoffs too brief: next session can't reconstruct context
- Handoffs too verbose: next session spends more time reading than working
- Handoffs stored where the next session doesn't read them