add-task
/add-task
Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
- Author
- driangle ↗
- Repository
- taskmd ↗
- Licence
- MIT
- Last repository change
- 02.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 1
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
Original author description
Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
How it works
- Instructions
SKILL.md preview
---
name: add-task
description: Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
allowed-tools: Read, Edit, Bash
---
# Add Task
Create a new task file using the `taskmd add` CLI command.
## Instructions
The user's task description is in `$ARGUMENTS`.
1. **Parse the user's input** from `$ARGUMENTS` to extract:
- The task **title** (required)
- An optional **template** name (e.g. "bug", "feature", "chore", or a custom template)
- Any optional flags: `--priority`, `--effort`, `--tags`, `--group`, `--depends-on`, `--parent`, `--owner`, `--slug`, `--phase`
2. **Choose the group** based on the task's domain (pass with `--group`):
- `cli` — CLI commands, Go backend, terminal features
- `web` — Web frontend, UI, React components
- Omit `--group` for cross-cutting, infrastructure, documentation, or unclear domain
3. **Run `taskmd add`** with the appropriate flags:
```bash
# Basic task
taskmd add "Fix the login bug" --group cli
# With a template
taskmd add "Login fails on Safari" --template bug --group cli
# With extra flags
taskmd add "Dark mode support" --template feature --priority high --tags ui,frontend --group web
# With a custom slug (overrides auto-generated slug from title)
taskmd add "Fix the login bug" --slug fix-login --group cli
# With a phase (must match a phase id from .taskmd.yaml)
taskmd add "Add phase filtering" --phase core-cli --group cli
```
When the user mentions a phase, milestone, or sprint, check `.taskmd.yaml` for configured `phases` and use the matching phase `id` with `--phase`. If the phase doesn't exist yet, add it to `.taskmd.yaml` first:
```yaml
# in .taskmd.yaml
phases:
- id: v2-launch
name: "V2 Launch"
description: "Features for the v2.0 release"
due: 2026-06-01 # optional
```
Each phase needs an `id` (referenced by tasks), `name` (display label), and optionally `description` and `due` date.
Available templates can be listed with `taskmd templates list`. Built-in templates include `bug`, `feature`, and `chore`. Projects may define custom templates in `.taskmd/templates/`.
4. **Fill in the task content**: Read the created file and replace placeholder content (HTML comments like `<!-- ... -->`, `TODO`, `1. ...`) with real content derived from the user's description in `$ARGUMENTS`. Fill in:
- The **Objective** section with a clear description of the goal
- The **Tasks** section with specific, actionable subtasks
- The **Acceptance Criteria** with concrete, verifiable criteria
- Any template-specific sections (e.g. "Steps to Reproduce", "Expected Behavior" for bug templates)
Use your understanding of the user's request to write meaningful content — don't leave placeholders.
5. **Validate** by running `taskmd validate` to ensure the task file is valid. If validation fails, fix the issues.
6. **Confirm** the created file path and ID to the user.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · driangle/taskmd | 100 | MIT |
| microbus-io/fabric | 100 | Apache-2.0 |
| driangle/taskmd | 100 | MIT |
| AdrianV101/obsidian-pkm-plugin | 98 | MIT |
| tbeack/fsad_playbook | 84 | MIT |
Database snapshot: 13.11.2026 · package version 13db3d3a5dcb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 81task_create
Create exactly one new task file for one upcoming work item. Use when the user asks to make, add, file, write, or capture a single task or todo. Use task for listing, querying, updating, archiving, linting, or multi task backlog work. - 100list-tasks
List tasks from the project's taskmd files, with optional filters (status, priority, phase, group, owner). Use whenever the user asks what is pending, in progress, done, outstanding, assigned, high priority, or "on the plate" — including phrasings like "my tasks", "my todos" or… - 100list-tasks
List tasks from the project's taskmd files, with optional filters (status, priority, phase, group, owner). Use whenever the user asks what is pending, in progress, done, outstanding, assigned, high priority, or "on the plate" — including phrasings like "my tasks", "my todos" or… - 91add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server. - 100task-prd-creator
Use when the user says I want to add X, implement Y, create a task for Z, or plan this feature. Writes a task file plus a PRD under .agent/, links them, and waits for approval before any implementation starts. - 91add-tool
Scaffold a new MCP tool definition. Use when the user asks to add a tool, create a new tool, or implement a new capability for the server.