Skill

next-task

Recommends the next task by scanning markdown files in tasks directory, filtering pending tasks without unmet dependencies, and ranking by priority, effort, and creation date. Use when asking what to work on next.

Markdown

developer-tools

automation

npx claudepluginhub driangle/taskmd --plugin taskmd-lite

Tool Access

This skill is limited to using the following tools:

GlobRead

Preview

Find the next recommended task using priority ranking — no CLI required.

SKILL.md

Similar Skills

next-task

Retrieves next recommended task from taskmd CLI with user arguments, reads details, and displays summary including ID, title, status, priority, and description. Use for task assignments or next steps.

2 tools

taskmd

ctx-next

Suggests 1-3 prioritized next tasks by analyzing TASKS.md, recent sessions via ctx journal, and priority tags. Use at session start, after tasks, or when unsure what to prioritize.

2 tools

ctx

file-todos

Manages file-based todo tracking system in todos/ directory using markdown files: creates todos from feedback, updates status/dependencies, triages items, integrates with slash commands and code reviews.

1 file

compound-engineering

Stats

Parent Repo Stars16

Parent Repo Forks2

Last CommitMar 13, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Next Task

Find the next recommended task using priority ranking — no CLI required.

Instructions

The user may provide optional filters in $ARGUMENTS (e.g. --tag mvp, --group cli).

Find the task directory:

Read .taskmd.yaml if it exists to check for a custom dir field
Default to tasks if not configured

Scan all task files: Use Glob with <task-dir>/**/*.md

Exclude .worklogs/ directories

Read frontmatter of each task file and collect: id, title, status, priority, effort, dependencies, tags, group, created, owner

Filter candidates:

Include only tasks with status: pending (or no status field)
Exclude tasks whose dependencies include any task that is NOT completed
Apply any user filters from $ARGUMENTS (e.g. --tag, --group, --owner)

Rank candidates using this priority order:

Priority (descending): critical > high > medium > low > unset
Effort (ascending): small > medium > large > unset (prefer smaller tasks as tiebreaker)
Created date (ascending): older tasks first

Present the top recommendation:

Read the full task file of the #1 ranked task
Show: ID, title, priority, effort, tags, and the full description
Optionally mention the next 2-3 runner-up tasks

See SPEC_REFERENCE.md (in the plugin root) for valid field values and ranking logic.

Next Task

Find the next recommended task using priority ranking — no CLI required.

Instructions

The user may provide optional filters in $ARGUMENTS (e.g. --tag mvp, --group cli).

Find the task directory:
- Read .taskmd.yaml if it exists to check for a custom dir field
- Default to tasks if not configured
Scan all task files: Use Glob with <task-dir>/**/*.md
- Exclude .worklogs/ directories
Read frontmatter of each task file and collect: id, title, status, priority, effort, dependencies, tags, group, created, owner
Filter candidates:
- Include only tasks with status: pending (or no status field)
- Exclude tasks whose dependencies include any task that is NOT completed
- Apply any user filters from $ARGUMENTS (e.g. --tag, --group, --owner)
Rank candidates using this priority order:
1. Priority (descending): critical > high > medium > low > unset
2. Effort (ascending): small > medium > large > unset (prefer smaller tasks as tiebreaker)
3. Created date (ascending): older tasks first
Present the top recommendation:
- Read the full task file of the #1 ranked task
- Show: ID, title, priority, effort, tags, and the full description
- Optionally mention the next 2-3 runner-up tasks

See SPEC_REFERENCE.md (in the plugin root) for valid field values and ranking logic.