harness-step3-session-management

To persist Claude Code session state, you save workspace context to files like init.sh, tasks.json, and progress.md at the project root instead of relying on memory. This ensures immediate context restoration when resuming work.

The best way to manage a task queue for multi-session workflows is maintaining a structured JSON file with fields like id, title, status, priority, and blocked_by. This guides the next steps across sessions without re-explaining work.

An append-only progress log in markdown format helps resuming development sessions by preserving a human-readable history of completed work. New sessions read this log to quickly restore context and continue multi-step tasks.

Yes, you need a SKILL.md file at the project root to enable state persistence. It must include YAML frontmatter with the name and description fields, while optional scripts, references, and assets are loaded on demand.

You can perform environment health checks at the start of a Claude Code session by running an init.sh script. This script executes startup commands and smoke tests to validate the workspace before reading the task queue.

Claude Code agents forget prior context between runs because sessions rely on volatile memory. Overcome this amnesia problem by persisting critical workspace state to files on disk for quick resumes.