session-handoff

Automating end-of-session handoffs generates a canonical HANDOFF-S{N}.md artifact, updates root TRACKER.md with metrics, and commits the state. It captures session outcomes, propagates continuity, and re-checks playtest innovations to prepare the next session.

An end-of-session handoff ritual resets workflow state by writing deterministic artifacts. It ensures no session ends without capturing outcomes, updating the root TRACKER.md with metrics, and re-running innovation threshold checks before committing.

Resetting state and propagating party continuity after a playtest requires generating a HANDOFF-S{N}.md file and updating the root TRACKER.md. This deterministic process captures session outcomes and re-checks playtest innovations to prepare the next session.

You do not need external dependencies to generate handoff artifacts and update trackers. The automation operates independently to write the HANDOFF-S{N}.md file, update the root TRACKER.md, and produce a commit-ready state without relying on external components.

The best way to ensure no session ends without updating the tracker is enforcing an end-of-session handoff ritual. This pipeline stage generates deterministic artifacts, updates root TRACKER.md with metrics, and re-runs innovation threshold checks before committing.

Your session tracker needs a handoff artifact to propagate continuity and re-check playtest innovations. The HANDOFF-S{N}.md file captures session outcomes and updates the root TRACKER.md, ensuring the next session begins with a deterministic, commit-ready state.