todo

Manage persistent, file-based todos across Claude Code sessions.

Updated Aug 27, 2026

Search Tags:#automation #workflow #planning #cli #todo #persistent

Ready to run

npx skills add https://github.com/SienkLogic/towline --skill todo-sienklogic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo
Source: https://github.com/SienkLogic/towline/tree/main/plugins/dev/skills/todo
Command: npx skills add https://github.com/SienkLogic/towline --skill todo-sienklogic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Native Claude Code Tasks are session-scoped — they vanish when the conversation ends. Towline todos persist as .planning/todos/*.md files across sessions, context resets, and compactions.

Core Features & Use Cases

Persist across sessions using file-based todo items stored in .planning/todos/pending/ and .planning/todos/done/.
Subcommands support add, list, and done with automatic slug generation, theme inference, and state updates.
Use Case: Keep track of actionable tasks during a long Claude Code session and resume later without losing history.

Quick Start

Add a new todo with a concise description.

Frequently Asked Questions about todo

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

FAQPage Schema

How do I persist todos across Claude Code sessions?▼

Persistent todos survive across Claude Code sessions by saving items as markdown files in the .planning/todos directory structure. This file-based approach ensures durable task tracking that withstands context resets and compactions without losing history.

How do I manage long-running workflow tasks when the conversation ends?▼

Long-running workflow tasks are managed by saving actionable tasks as file-based todo items in pending and done directories. You can add, list, and mark tasks as done, enabling resumable progress tracking when you return to the session.

Why do my native Claude Code tasks disappear after a context reset?▼

Native Claude Code tasks disappear after a context reset because they are session-scoped and stored in memory. Persistent todos solve this by writing task state to markdown files on disk, ensuring durable tracking across context resets and compactions.

Do I need a YAML frontmatter to enable context loading for persistent todos?▼

Yes, a YAML frontmatter with name and description fields is required to enable discovery and context loading. This metadata allows the persistent todo system to properly identify and load the correct task tracking context across sessions.

What is the best way to track resumable progress for long-running automation workflows?▼

The best way to track resumable progress is using a file-based todo system that stores items in pending and done folders. This approach supports automatic slug generation and state updates, providing durable task tracking for long-running automation workflows.