session-manager

Invoke the session resume flow, which reads the most recent WFS session file and handoff document from the .workflow directory, checks git log and status, then presents a session brief with completed, in-progress, and blocked items plus recommended next actions.

Run the session complete flow at the end of your session. It generates a markdown handoff document covering completed work, decisions with rationale, blocked items, and prioritized next actions, plus a JSON state file for programmatic recovery.

Yes, the session sync flow reads all active session files in .workflow/active, pulls in commits from other sessions, and flags conflicts when two sessions modified the same file. Conflicts are presented to the user and never auto-resolved.

Session state lives in a .workflow directory with active/ holding WFS-<timestamp> JSON files and handoffs/ holding markdown handoff documents. Older sessions are archived to .workflow/archive after 20 active files accumulate.

Skip it for self-contained one-shot tasks where session overhead is unjustified, and for full project planning, which belongs to a conductor-style skill. It tracks state and context, not requirements or specifications.