From markdown-tasks
Work through all incomplete tasks in .llm/todo.md with one subagent and commit per task, continuing past blocked tasks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/markdown-tasks:markdown-do-all-tasksThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `markdown-tasks` skill for script path rules and task semantics. Use this workflow only when live edits are permitted; leave plan mode before starting the loop.
Use the markdown-tasks skill for script path rules and task semantics. Use this workflow only when live edits are permitted; leave plan mode before starting the loop.
The leader coordinates the loop and does not implement tasks. It may only:
task_get.py.task_mark.py --marker='!'.HEAD.task_archive.py.The leader must not read .llm/todo.md directly, read task-referenced source files, or edit implementation files. Each worker discovers and reads its own implementation context.
Extract the first incomplete task:
python <plugin-root>/scripts/task_get.py .llm/todo.md
If no task is returned, proceed to archiving. Otherwise:
HEAD commit.markdown-do-one-task; do not combine tasks or add unrelated work.task_mark.py only after validation succeeds.After the worker returns:
Require a clean worktree. Stop and report if the worker left staged or unstaged changes.
On success, verify that HEAD advanced by exactly one commit and that task_get.py no longer returns the completed task.
On failure, verify that HEAD did not advance, then mark the first incomplete task blocked so the loop can continue:
python <plugin-root>/scripts/task_mark.py .llm/todo.md --marker='!'
If the worker made commits before failing or the task state is ambiguous, stop instead of marking or stacking more work.
Blocked [!] tasks are skipped by task_get.py, so each failed task is attempted once and cannot create an infinite loop.
Before extracting another task, run the repository's precommit test against the committed HEAD:
git test run HEAD --retest --verbose --verbose
Also check git test results HEAD when available. Continue only when the command succeeds and the recorded result is good. Stop if the result is bad or unknown; never stack another task on an unverified commit.
Repeat extraction, delegation, result handling, and the HEAD gate until no incomplete tasks remain.
When task_get.py returns no result, every task is completed [x] or blocked [!]. Archive the list:
python <plugin-root>/scripts/task_archive.py .llm/todo.md
Report the archive path and identify blocked tasks reported during this run. Do not archive early when user-supplied stopping instructions leave incomplete [ ] tasks.
npx claudepluginhub motlin/claude-code-plugins --plugin markdown-tasksGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.