Skip to content
Skills Library
Personal productivity · Planning

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.

Repository
taskmd ↗
Licence
MIT
Last repository change
02.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.

Licence

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

  1. Instructions
Original SKILL.md headings · 56 lines, 396 words
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: Glob, Read, Edit
---

# Update Task

Update fields of an existing task — no CLI required.

## 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. **Find the task file**:
   - Read `.taskmd.yaml` for custom `dir` (default: `tasks`)
   - Use `Glob` for `<task-dir>/**/*<ID>*.md`
   - If multiple matches, read frontmatter to find the exact ID match
   - If not found, list available tasks

3. **Read the task file** with the `Read` tool

4. **Apply updates using the `Edit` tool**:

   ### Frontmatter field updates
   For each field to change, edit the YAML frontmatter:
   - **status**: Replace the `status: <old>` line with `status: <new>` — valid values: pending, in-progress, completed, in-review, blocked, cancelled
   - **priority**: Replace `priority: <old>` with `priority: <new>` — valid: low, medium, high, critical
   - **effort**: Replace `effort: <old>` with `effort: <new>` — valid: small, medium, large
   - **type**: Replace `type: <old>` with `type: <new>` — valid: feature, bug, improvement, chore, docs
   - **owner**: Replace or add `owner: "<value>"`
   - **phase**: Replace or add `phase: "<value>"` — must match a phase `id` in `.taskmd.yaml`. If the phase doesn't exist yet, add it to the `phases` array in `.taskmd.yaml` first (see `SPEC_REFERENCE.md`)
   - **parent**: Replace or add `parent: "<value>"`
   - **title**: Replace the `title: "..."` line

   ### Array field updates (tags, dependencies, pr)
   - **Add tag**: Add the value to the `tags` array in frontmatter
   - **Remove tag**: Remove the value from the `tags` array
   - **Add dependency**: Add the ID to the `dependencies` array
   - **Remove dependency**: Remove the ID from the array
   - **Add PR**: Add the URL to the `pr` array
   - **Remove PR**: Remove the URL from the array

   If a field doesn't exist in the frontmatter yet, add it before the closing `---`

   ### Body updates
   - **description/subtasks/acceptance criteria**: Edit the markdown body directly

5. **Validate** the changes:
   - Ensure enum values are valid (see SPEC_REFERENCE.md)
   - Ensure the frontmatter is still valid YAML
   - If a field value is invalid, explain the valid options to the user

6. **Confirm** the changes to the user, showing what was updated

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

Versions

RepositoryScoreLicence
This page · driangle/taskmd90MIT
driangle/taskmd100MIT

Database snapshot: 13.11.2026 · package version 7817c89377bf (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

  • 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-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…
  • 90get-task
    Get details of a specific task by ID or name. Use when the user wants to view or look up a task.
  • 100pr-update
    Update an existing pull request's title and description based on current branch commits. Use when PR needs to be refreshed after new commits or when asked to update PR.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.