| name | tasks |
| description | Work with markdown-based task lists in .llm/todo.md files. Use when managing tasks, working with todo lists, extracting incomplete tasks, marking tasks complete, or implementing tasks from a task list. |
Markdown Task Management
This skill enables working with the markdown task list stored in .llm/todo.md.
Resolve <plugin-root> before running plugin scripts:
- In Claude Code, use
${CLAUDE_PLUGIN_ROOT}.
- In Codex, use the plugin root that contains this
skills/tasks/SKILL.md file.
Scripts
task_get.py - Extract Next Task
Extract the first incomplete task with its context:
python <plugin-root>/scripts/task_get.py .llm/todo.md
Returns the first [ ] checkbox line with all indented context lines below it.
Exit codes: 0 (success), 1 (file not found or error)
task_add.py - Add New Task
Add a new task:
python <plugin-root>/scripts/task_add.py .llm/todo.md "Task description
Context line 1
Context line 2"
When adding more than one task, chain the calls into a single bash command with && rather than running a separate command per task:
python <plugin-root>/scripts/task_add.py .llm/todo.md "First task
Context line 1" && \
python <plugin-root>/scripts/task_add.py .llm/todo.md "Second task" && \
python <plugin-root>/scripts/task_add.py .llm/todo.md "Third task"
Running the whole batch as one command keeps the write window to .llm/todo.md extremely short, so concurrent sessions writing to the same file are far less likely to interleave their tasks.
Creates the .llm/ directory and todo.md file if they do not exist, and appends the new task with a [ ] checkbox. The script preserves all indentation in multi-line strings.
Exit codes: 0 (success), 1 (error)
task_mark.py - Mark Task
Mark the first incomplete task with a marker character:
python <plugin-root>/scripts/task_mark.py .llm/todo.md
python <plugin-root>/scripts/task_mark.py .llm/todo.md --marker='!'
Changes the first [ ] to [x] by default. Pass --marker with any single non-space character (e.g. !, >, -) to use a different marker.
Exit codes: 0 (success), 1 (no incomplete tasks or error)
task_archive.py - Archive Task List
Archive a completed task list:
python <plugin-root>/scripts/task_archive.py .llm/todo.md
Moves the file to .llm/YYYY-MM-DD-todo.md where YYYY-MM-DD is today's date.
Exit codes: 0 (success), 1 (file not found or error)
Task Format
The task list is in .llm/todo.md.
NEVER use the Read tool on .llm/todo.md. Always interact with the task list exclusively through the Python scripts.
Task States
[ ] - Not started (ready to work on)[x] - Completed[!] - Blocked after failed attempt
Task Structure
Each task includes indented context lines with full implementation details:
- Absolute file paths
- Exact function/class names
- Code analogies to existing patterns
- Dependencies and prerequisites
- Expected outcomes
Standalone Context
Each task is extracted and executed in isolation. Every task must contain ALL context needed to implement it. Repeat shared context in every related task. Never reference other tasks.
If tasks were created from a plan file, include the plan file path in each task so the implementing agent can read the full context.
Plan Mode
When using Claude Code's native plan mode to design an implementation before creating tasks:
- The plan file is written to
~/.claude/plans/<auto-generated-name>.md (e.g., ~/.claude/plans/abstract-knitting-garden.md)
- Before adding any tasks, archive the plan locally:
- Create the
.llm/plans/ directory if it does not exist
- Move the file from
~/.claude/plans/<auto-generated-name>.md to .llm/plans/<yyyy-mm-dd>-<descriptive-name>.md
- Choose a concise, meaningful name that describes the plan's purpose (e.g.,
2025-12-04-thread-safety-tests.md, 2025-12-04-plugin-hook-system.md)
- Include the absolute path to the archived
.llm/plans/ file in each task so the implementing agent can read the full context
When using Codex planning, store the plan under .llm/plans/<yyyy-mm-dd>-<descriptive-name>.md before adding tasks, then include that absolute path in each task.
