save-task-list

To preserve your Claude Code task list for reuse across sessions, invoke the save-task-list skill to log the current session's tasks to a JSONL file and install a SessionStart hook for automatic cross-session restoration.

Session persistence for task lists works by logging the session-to-task-list mapping to a JSONL file and installing a settings-level SessionStart hook that verifies and surfaces the restored planning state on new sessions.

Yes, you can recover planning state and task dependencies after closing a Claude Code session by using a startup command that resumes work with the preserved task list logged in the session archive.

The best way to save a workflow task list for continuity across development sessions is to use a skill-scoped hook that verifies completion and logs the task list mapping for audit and recovery.

No, you do not need any dependencies or external components to save session task lists, as the skill operates independently using internal hooks and a local JSONL log file for persistence.

Your restored task list shows a warning on session start because the installed SessionStart hook verifies the restoration status and surfaces a confirmation or warning if the task list state is incomplete or mismatched.