session-summary

You log developer session state by appending a structured Markdown entry to a feature's session-log.md, synthesizing git activity and conversation context to record completed work, in-progress tasks, and next steps for seamless continuity.

Preserving work context across ATDD sessions requires appending end-of-session state to session-log.md, capturing decisions, problems, and deferrals so the next session resumes with accurate task continuity and known blockers.

Creating a session summary from git activity involves deriving prior tasks, current task, and next tasks from handoff files and conversation context, then appending the synthesized entry to session-log.md without overwriting previous logs.

Session logging never overwrites previous entries; it strictly appends new structured Markdown records to session-log.md, ensuring the full historical context of completed work and decisions remains intact across multiple work sessions.

Session logging supports spec-driven engineering workflows by recording deterministic handoff summaries with checkpoint null and no human action required, enabling downstream processing to resume scoped features accurately.

You generate an end-of-session handoff summary when wrapping up a scoped feature work session, ensuring an accurate log of completed work, in-progress tasks, and next steps is preserved for the next developer.