Skill

add-task

Creates taskmd-compliant Markdown task files: parses title/metadata from arguments, generates IDs (sequential/prefixed/random/ULID), infers groups, structures with objective/subtasks/acceptance criteria. Uses .taskmd.yaml config.

Markdown

developer-tools

automation

npx claudepluginhub driangle/taskmd --plugin taskmd-lite

Tool Access

This skill is limited to using the following tools:

GlobReadWrite

Preview

Create a new task file — no CLI required.

SKILL.md

Similar Skills

add-task

Creates taskmd task files via CLI: parses user input for title, template, flags like priority/tags/group; fills objective, subtasks, criteria; validates output. Use when adding project tasks.

3 tools

taskmd

creating-task

Creates tasks or sections in TASKS.md to track project work. Auto-triggers on phrases like 'add a task', 'todo', 'let's plan', or untracked future work.

cotask

ctx-add-task

Adds actionable tasks to TASKS.md for follow-up work or subtasks using ctx bash tool. Validates specificity, priority, uniqueness, and actionability before recording.

1 tool

ctx

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.

Add Task

Create a new task file — no CLI required.

Instructions

The user's task description is in $ARGUMENTS.

Parse the user's input from $ARGUMENTS to extract:

The task title (required)
Any optional metadata: priority, effort, type, tags, group, dependencies, parent, owner, phase

Read configuration:

Read .taskmd.yaml if it exists for: task dir (default: tasks), id config (strategy, prefix, padding, length), and phases

Determine the group based on the task's domain:

If the user specified --group, use that
Otherwise infer from context (e.g., CLI/backend → cli, web/frontend → web, or root for cross-cutting)

Generate the task ID:

Read the ID strategy from .taskmd.yaml (default: sequential)
Scan existing files with Glob for <task-dir>/**/*.md to determine used IDs
Sequential (default): Find the highest numeric ID, add 1, zero-pad to padding width (default 3). E.g., if highest is 042, next is 043
Prefixed: Find highest number with the configured prefix. E.g., dr-001, dr-002
Random: Generate a random alphanumeric string of configured length (default 6) containing at least one digit
ULID: Generate a ULID-like ID — use current timestamp in Crockford Base32 + random chars

Create the task file using Write:

Path: <task-dir>/<group>/<ID>-<slug-title>.md (or <task-dir>/<ID>-<slug-title>.md if no group)
Slug: lowercase, hyphenated version of the title (max ~50 chars)
Content:

---
id: "<ID>"
title: "<title>"
status: pending
priority: <priority if provided>
effort: <effort if provided>
type: <type if provided>
tags: [<tags if provided>]
dependencies: [<deps if provided>]
parent: "<parent if provided>"
owner: "<owner if provided>"
phase: "<phase if provided>"
created: <today's date YYYY-MM-DD>
---

# <Title>

## Objective

<Description derived from user's input>

## Tasks

- [ ] <Subtask 1>
- [ ] <Subtask 2>

## Acceptance Criteria

- <Criterion derived from the task>

Only include optional frontmatter fields that were specified or can be inferred. Don't include empty fields.

Confirm the created file path and ID to the user

See SPEC_REFERENCE.md (in the plugin root) for valid field values, ID strategies, and frontmatter schema.

Add Task

Create a new task file — no CLI required.

Instructions

The user's task description is in $ARGUMENTS.

Parse the user's input from $ARGUMENTS to extract:

The task title (required)
Any optional metadata: priority, effort, type, tags, group, dependencies, parent, owner, phase

Read configuration:

Read .taskmd.yaml if it exists for: task dir (default: tasks), id config (strategy, prefix, padding, length), and phases

Determine the group based on the task's domain:

If the user specified --group, use that
Otherwise infer from context (e.g., CLI/backend → cli, web/frontend → web, or root for cross-cutting)

Generate the task ID:

Read the ID strategy from .taskmd.yaml (default: sequential)
Scan existing files with Glob for <task-dir>/**/*.md to determine used IDs
Sequential (default): Find the highest numeric ID, add 1, zero-pad to padding width (default 3). E.g., if highest is 042, next is 043
Prefixed: Find highest number with the configured prefix. E.g., dr-001, dr-002
Random: Generate a random alphanumeric string of configured length (default 6) containing at least one digit
ULID: Generate a ULID-like ID — use current timestamp in Crockford Base32 + random chars

Create the task file using Write:

Path: <task-dir>/<group>/<ID>-<slug-title>.md (or <task-dir>/<ID>-<slug-title>.md if no group)
Slug: lowercase, hyphenated version of the title (max ~50 chars)
Content:

---
id: "<ID>"
title: "<title>"
status: pending
priority: <priority if provided>
effort: <effort if provided>
type: <type if provided>
tags: [<tags if provided>]
dependencies: [<deps if provided>]
parent: "<parent if provided>"
owner: "<owner if provided>"
phase: "<phase if provided>"
created: <today's date YYYY-MM-DD>
---

# <Title>

## Objective

<Description derived from user's input>

## Tasks

- [ ] <Subtask 1>
- [ ] <Subtask 2>

## Acceptance Criteria

- <Criterion derived from the task>

Only include optional frontmatter fields that were specified or can be inferred. Don't include empty fields.

Confirm the created file path and ID to the user

See SPEC_REFERENCE.md (in the plugin root) for valid field values, ID strategies, and frontmatter schema.