From markdown-tasks
Find and implement the next incomplete task from .llm/todo.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/markdown-tasks:markdown-do-one-taskThe 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 the markdown-tasks skill for script path rules and task semantics.
Extract the next task:
python <plugin-root>/scripts/task_get.py .llm/todo.md
If no task is returned, report that there are no incomplete tasks.
Implement only the extracted task. Ignore unrelated TODO/TASK comments in source code.
Run appropriate tests and validation. Complete the repository's finish workflow so the task has its own commit, precommit passes against that commit, and the branch is rebased when required. If the build, git, and orchestration plugins are installed, use their precommit, git-commit, git-rebase, and finish skills.
Mark the task complete only after implementation, commit, and validation succeed:
python <plugin-root>/scripts/task_mark.py .llm/todo.md
If implementation or validation fails, leave the task incomplete and report the failure. The markdown-do-all-tasks leader is responsible for marking failed attempts [!].
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.