update-task
/update-task
Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties.
- Author
- driangle ↗
- Repository
- taskmd ↗
- Licence
- MIT
- Last repository change
- 02.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- 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.
What it does and when to use it
Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties.
Original author description
Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties.
How it works
- Instructions
SKILL.md preview
--- name: update-task description: Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties. allowed-tools: Bash, Read, Edit --- # Update Task Update fields of an existing task. ## Instructions The user's query is in `$ARGUMENTS` (e.g. "set task 042 to high priority and in-progress", "rename task 15 to Fix auth bug", "add tag backend to 042"). 1. **Parse the user's input** from `$ARGUMENTS` to extract: - The **task ID** (required) - The **fields to update** and their new values 2. **Look up the task**: Run `taskmd get <ID>` to confirm the task exists - If not found, run `taskmd list` to show available tasks and ask the user which one they meant 3. **Determine how to apply each update**: ### Fields supported by `taskmd set` (use CLI): - `--title` — new title; also updates the matching `#` heading in the task body. Add `--rename` to move the file to `<id>-<new-slug>.md` (the file otherwise keeps its old name, which is harmless — tasks resolve by ID). - `--status` — pending, in-progress, completed, in-review, blocked, cancelled - `--priority` — low, medium, high, critical - `--effort` — small, medium, large - `--type` — feature, bug, improvement, chore, docs - `--owner` — assignee name - `--parent` — parent task ID (empty string to clear) - `--phase` — phase ID (must match a phase id in `.taskmd.yaml`; empty string to clear). If the phase doesn't exist in `.taskmd.yaml`, add it there first (see `add-task` skill for the phases config format). - `--add-tag` / `--remove-tag` — add or remove tags (repeatable) - `--add-pr` / `--remove-pr` — add or remove PR URLs (repeatable) - `--depends-on` — replace dependencies (comma-separated IDs, e.g. `010,015`; empty string to clear) Build a single `taskmd set <ID>` command with all applicable flags: ```bash taskmd set 042 --priority high --status in-progress --add-tag backend ``` ### Fields NOT supported by `taskmd set` (edit file directly): - **custom frontmatter fields** — edit the frontmatter directly - **description / subtasks / acceptance criteria** — edit the markdown body For direct file edits: 1. Read the task file with the `Read` tool 2. Use the `Edit` tool to make the change 3. Run `taskmd validate` to ensure the file is still valid 4. **Handle errors**: - If the task ID is invalid or not found, tell the user and suggest running `taskmd list` - If a field value is invalid (e.g. `--priority mega`), explain the valid options - If `taskmd validate` fails after a direct edit, fix the issue before confirming 5. **Confirm** the changes to the user, showing what was updated
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · driangle/taskmd | 100 | MIT |
| driangle/taskmd | 90 | MIT |
Database snapshot: 13.11.2026 · package version 5b27887f5c20 (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
- 100update-work-item
Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed. - 100get-task-status
Get only the metadata/status of a task without full details. Use when the user wants to quickly check a task's status, priority, or other metadata. - 95update-linear-issue
Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational… - 90org-update-todo
Update the TODO state and metadata of an existing org-mode heading via the org MCP server. Use when the user wants to change a task's state, priority, tags, or timestamps. Triggers: "mark as done", "complete this task", "reschedule", "change priority", "update the deadline",… - 100update-task-status
Use when you want to update the workflow status of an octomux task, add a note, rename it, or link external references (e.g. Jira tickets) - 100task
在 SoduWork 里管任务:把聊清楚的事建成任务、顺手派给 AI 执行机或起流程、查自己名下的任务、改状态和验收要点。当人说「帮我建个任务」「这件事交给 AI 去做」「我手上还有什么活」「把这个标成做完了」,或者你们已经把一件事聊明白、该落成一条任务时使用。