save-task-list

Save the active Claude Code task list and install a SessionStart validator.

Updated May 13, 2026
One-click install
npx skills add https://github.com/cliffthelin/AXiomEngine --skill save-task-list-cliffthelin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-task-list
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/save-task-list
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill save-task-list-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, bash, find.

What problem does it solve?

This Skill prevents lost momentum by saving the current Claude Code task list and reliably restoring it in a later session.

Core Features & Use Cases

  • Session task-list persistence: Captures the most recent task list directory under ~/.claude/tasks and records which session saved it.
  • Startup validation via SessionStart hook: Installs a settings-level SessionStart hook that checks the provided CLAUDE_CODE_TASK_LIST_ID exists and reports a task count.
  • Operational quality gates & observability: Uses a Stop hook to verify the startup command/task list was produced and a PostToolUse hook to log tool invocations.
  • Use case: When you start planning a refactor into multiple tasks, you can save that plan, close the session, and continue later using the same task list with confirmation that it exists.

Quick Start

Ask to run the save-task-list workflow for your current Claude Code session so you can continue the exact same task plan in a new session.

Frequently Asked Questions about save-task-list

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore a Claude Code task list across sessions?

To restore a Claude Code task list across sessions, this Skill locates the newest task directory under ~/.claude/tasks, logs a session-to-task-list mapping in JSONL, and installs a SessionStart hook to validate the task list ID on startup.

How does session persistence work for multi-step refactoring plans?

Session persistence for multi-step refactoring works by capturing the most recent task directory and installing a settings.local.json SessionStart hook. This hook validates the CLAUDE_CODE_TASK_LIST_ID exists and emits the startup command to resume the plan.

Do I need jq and bash to use governance hooks for task management?

Yes, you need jq and bash installed to use these governance hooks for task management. The Skill relies on bash execution and uses jq to parse JSON structures within settings.local.json and the JSONL session mapping logs.

Can I use workflow restore for a task-directory-based workflow?

Yes, you can use workflow restore for any task-directory-based workflow. It creates a repeatable restart point by saving the active task plan and validating its existence through a PostToolUse hook that logs tool invocations during the session.

What is the best way to prevent lost momentum when closing a Claude Code session?

The best way to prevent lost momentum when closing a Claude Code session is to save the active task list ID and install a Stop hook. This hook verifies the startup command was produced and ensures the task plan is validated for the next session.