save-task-list

Save current session task lists to .claude/archon/sessions/task-lists.jsonl for reuse.

23.1k|3.5k|Updated Feb 7, 2025
One-click install
npx skills add https://github.com/coleam00/Archon --skill save-task-list-coleam00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: save-task-list
Source: https://github.com/coleam00/Archon/tree/main/.claude/skills/save-task-list
Command: npx skills add https://github.com/coleam00/Archon --skill save-task-list-coleam00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Saves the current session's task list for reuse across future Claude Code sessions, enabling task continuity across sessions and projects.

Core Features & Use Cases

  • Session-scoped persistence: saves task lists to .claude/archon/sessions/task-lists.jsonl.
  • Start-up restoration: outputs CLAUDE_CODE_TASK_LIST_ID=<id> claude to resume work.
  • Validation and observability: includes a Stop hook to verify outputs and a PostToolUse hook for logging tool usage.

Quick Start

Invoke the skill with /save-task-list to capture and reuse the current session's task list.

Frequently Asked Questions about save-task-list

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

FAQPage Schema
How do I save my coding task list and reuse it across Claude Code sessions?

You can save your session task list by invoking the skill, which persists tasks, summaries, and dependencies to a JSONL file and outputs a resume command to restore the list when starting a new Claude Code session.

How does session task list persistence work when switching projects?

Session persistence works by saving tasks to a JSONL file and using a SessionStart hook to verify and surface the restored task list automatically when you begin a new coding session or switch projects.

Can I use Claude Code hooks to enforce task completion and log tool usage?

Yes, you can enforce task completion and log tool usage by implementing a Stop hook to verify outputs and a PostToolUse hook to capture tool usage logs during your coding workflow sessions.

What is the best way to preserve context and dependencies when starting a new coding session?

The best way to preserve context is to save the session task list to a JSONL file, which captures task summaries and dependencies so you can resume work using the restored task list ID.

Do I need to configure any dependencies to save and restore my session task list?

No external dependencies are required; the skill relies on internal Claude Code hooks and settings to save task lists to a JSONL file and verify the restored list on session start.