Write the per-session entry in a feature's session-log.md so the human can close the laptop and pick back up cleanly. The human-readable counterpart to the machine handoffs. checkpoint: null.
When to use
At the end of a work session on a feature. A lifecycle hook may nudge this workflow when supported by the current Codex hook schema; that hook is optional project config, not part of this skill.
Not for: mid-session (nothing's wrapping up); syncing the tracker (progress-log); per-skill records (each skill's own handoff).
Workflow
- Resolve + scope — resolve the methodology root + manifest via
${PLUGIN_ROOT}/scripts/dae_resolve.py(seereferences/resolving.md). Scope = the feature(s) the session touched (default: current branch; multiple → an entry in each; none → nothing to log, stop). - Gather — synthesize from this session's
handoffs/*.md, git activity on the branch, and conversation context (decisions, problems, deferrals). - Append the entry — append (never overwrite) to
features/NNN-<slug>/session-log.md:
## Session — <ISO date> <start>–<end>
**Current state:** <which checkpoint, one line>
### Previous tasks (done this session)
- ...
### Current task
- <in progress at session end, if any>
### Next tasks
- <concrete, actionable, ordered>
### Open questions / blockers
- <or "None">
Create the file with a # Session log — <title> heading if absent.
- Handoff — emit a summary.
Handoff
Emit per ${PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; human_action_needed: no; recommended_next: the first "Next task" from the entry. (session-summary is not the handoff processor, so it follows the normal contract — no exemption.)
session-log.md vs handoffs vs progress.md
Three records, three readers: handoffs/ = machine, per-invocation; progress.md = machine-derived, glanceable; session-log.md = human, per-session, narrative. They don't duplicate — different granularity, different reader.
References
- Foundation Design —
session-log.mdin the storage layout, the session-log ↔ handoffs distinction (Section 5)