Personal productivity · Tool integration
complete-task
/complete-task
Mark a task as completed. Use when the user wants to mark a task as done or complete.
- Author
- driangle ↗
- 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
Mark a task as completed. Use when the user wants to mark a task as done or complete.
Original author description
Mark a task as completed. Use when the user wants to mark a task as done or complete.
How it works
- Instructions
Original SKILL.md headings · 48 lines, 406 words
SKILL.md preview
---
name: complete-task
description: Mark a task as completed. Use when the user wants to mark a task as done or complete.
allowed-tools: Glob, Read, Edit, Write
---
# Complete Task
Mark a task as completed — no CLI required.
## Instructions
The user's query is in `$ARGUMENTS` (a task ID like `077`). If `$ARGUMENTS` is empty or does not contain a task ID, infer the task from conversation context (e.g., the task currently being worked on). If the task cannot be determined, ask the user which task to complete.
1. **Find the task file**:
- Read `.taskmd.yaml` for custom `dir` (default: `tasks`) and `workflow` mode (default: `solo`)
- Use `Glob` for `<task-dir>/**/*$ARGUMENTS*.md`
- Read frontmatter to confirm the ID matches
- If not found, list available tasks
2. **Read the task file** to understand the full task scope:
- Get current status and verify fields
- Identify all **subtask checklists** (`- [ ]` / `- [x]` items) in the task body
- Identify any **acceptance criteria** section
3. **Verify subtasks and acceptance criteria are met**:
- Review each subtask checklist item — confirm the work has been done
- Review each acceptance criterion — confirm it is satisfied
- **Check off** (`- [x]`) any items that are complete but not yet checked off by editing the task file
- If any items are genuinely incomplete, report them to the user and ask how to proceed — do NOT mark the task as completed
4. **Add a final worklog entry** (if worklogs are enabled):
- Check `.taskmd.yaml` for `worklogs: true` — worklogs are opt-in, so skip this step unless the key is explicitly set to `true`
- If enabled, find or create the worklog file at `<task-dir>/<group>/.worklogs/<ID>.md` (or `<task-dir>/.worklogs/<ID>.md` for root tasks)
- Append a timestamped completion summary
5. **Check the workflow mode** from `.taskmd.yaml`:
### Solo mode (default)
- If the task has `verify` checks in frontmatter:
- For `bash` type: Run each `run` command via Bash (in the specified `dir` or project root) and check exit code
- For `assert` type: Evaluate each `check` by inspecting the codebase
- If any check fails, report failures and do NOT mark as completed
- If all checks pass (or no verify checks): Edit the frontmatter to set `status: completed`
### PR-review mode
- Edit the frontmatter to set `status: in-review` instead of `completed`
- Note to the user that in pr-review mode, the task completes when the PR is merged
6. **Confirm** the status change to the user
See `SPEC_REFERENCE.md` (in the plugin root) for valid field values, workflow modes, and verify check format.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · driangle/taskmd | 90 | MIT |
| driangle/taskmd | 90 | MIT |
Database snapshot: 13.11.2026 · package version faeef3c40b7b (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
- 95nacl-tl-docs
Documentation updates for approved tasks. Use when: update documentation, write docs, finalize task, complete task, mark done, or the user says "/nacl-tl-docs UC###". - 90task
This skill should be used when the user wants to "create a task", "start a new task", "split a task", "make this an epic", "mark a task in progress", "mark a task done", "complete a task", "run this task autonomously", "set a budget on this task", "raise the budget", "save what… - 100manage-tasks
Maintain a checkable to-do list — add, complete, reprioritize, and review tasks — as an interactive hologram. Use for "add a task", "what's on my list?", "mark X done", "show my to-dos", or planning the day. Triggers: task, to-do, todo, add to my list, mark done, check off, my tasks, what's left. - 87mark-done
Use when: kullanıcı "task done", "mark complete", "iş bitirildi", "completed_work entry", "master_task DONE update" der ya da /pseo-mark-done çağırır; master_task primary key task_id resolve + completion_evidence reference + completed_work append + master_task status DONE update… - 91do-one-task
Find and implement the next incomplete task from .llm/todo.md, commit it through the finish workflow, and mark it done. Use when the user wants the next queued task done. - 100todo
Add, complete, view, or link plans to items in the project backlog (GitHub issues or brain/todos.md). Use when the user says "todo", "add a todo", "mark done", "what's on the backlog", "show todos", "list tasks", "check off", or wants to manage their task list.