motlin/markdown-tasks
plugins/markdown-tasks/skills/tasks/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add motlin/claude-code-plugins markdown-tasksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 5:26 PM114.6s1 file scanned
SKILL.md
- name:
- markdown-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.
Scripts
task_get.py - Extract Next Task
Extract the first incomplete task with its context:
python ${CLAUDE_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 ${CLAUDE_PLUGIN_ROOT}/scripts/task_add.py .llm/todo.md "Task description
Context line 1
Context line 2"
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_complete.py - Mark Task Done
Mark the first incomplete task as done:
python ${CLAUDE_PLUGIN_ROOT}/scripts/task_complete.py .llm/todo.md
Changes the first [ ] to [x].
Exit codes: 0 (success), 1 (no incomplete tasks or error)
task_archive.py - Archive Task List
Archive a completed task list:
python ${CLAUDE_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'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>.mdto.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)
- Create the
- Include the absolute path to the archived
.llm/plans/file in each task so the implementing agent can read the full context
Related Skills
motlin/finish
tools
VerifiedTrustedCommunity
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
13SKILL.mdUpdated Apr 19, 2026
motlin/git-workflow
development
VerifiedTrustedCommunity
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
12SKILL.mdUpdated Apr 19, 2026
motlin/cli
tools
VerifiedTrustedCommunity
CLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.
11SKILL.mdUpdated Apr 19, 2026
motlin/maven-cli
tools
VerifiedTrustedCommunity
Maven CLI invocation patterns. Use whenever running `mvn` commands in Java/Maven projects. Covers when `-am` is required, why `-o` (offline) mode hides bugs in multi-worktree setups, and how to verify compile/test cleanly without trusting stale `~/.m2` artifacts.
10SKILL.mdUpdated May 7, 2026