Our review
Updates worklog files by moving tasks between todo/doing/done states based on explicit commands.
Strengths
- Clear state tracking with separate files for backlog, in-progress, and completed tasks
- Flexible keyword matching to locate and move tasks automatically
- Automatically groups completed tasks under daily date sections
Limitations
- Requires explicit arguments; fails gracefully if omitted
- Keyword matching may be ambiguous with similar task descriptions
- Does not handle future items that are not yet in an approved plan
Use this skill during active development or sessions to log progress and maintain a clear task trail.
Do not use for items that are not yet part of the approved plan; instead, add them to the dedicated backlog file.
Security analysis
SafeThe skill only reads and writes local markdown files for task tracking. It contains no destructive commands, network access, or handling of secrets. File operations are limited to worklog files, and no malicious or obfuscated actions are present.
No concerns found
Examples
worklog done Finished implementing the user authentication module in auth.pyworklog doing Refactor database connection in db/connection.pyworklog todo Write unit tests for the API endpointsname: worklog description: Update worklog files by moving tasks between todo/doing/done states. Use when recording task progress, starting new work, or marking tasks complete. Requires explicit arguments: worklog [done|doing|todo] [description].
Worklog
Update task state in worklog files. Requires explicit arguments.
Worklog Files
localdocs/worklog.todo.md— backloglocaldocs/worklog.doing.md— in progresslocaldocs/worklog.done.md— completed (grouped by date, append-only)
worklog is for current phase/session execution tracking.
For future items not yet included in an approved plan, use localdocs/backlog.<topic>.md.
Arguments
$ARGUMENTS must be: [state] [description]
done [description]— mark task completedoing [description]— start working on a tasktodo [description]— add to backlog
If no arguments, stop and output:
Error: worklog requires explicit arguments.
Usage: worklog [done|doing|todo] [description]
Examples:
worklog done config/settings.py setup complete
worklog doing collectors/data_go_kr.py implementation
worklog todo parsers/xml_parser.py implementation
What to Read (by command)
done: Read worklog.doing.md only — to find and remove the matching item.
doing: Read worklog.todo.md only — to find and remove the matching item.
todo: No need to read any file — just append.
Never read worklog.done.md — it is append-only and grows over time.
Update Rules
done [description]
- Read
worklog.doing.md; find matching item (keyword match, not exact) - Remove the item from doing
- Append to
worklog.done.mdunder today's date section (## YYYY-MM-DD), creating the section if absent - If no match in doing, append directly to done without removing anything
doing [description]
- Read
worklog.todo.md; find matching item - Remove the item from todo
- Append to
worklog.doing.md - If no match in todo, append directly to doing
todo [description]
- Append item to end of
worklog.todo.md
Writing Style
- Concise bullet points — focus on what was done, not how
- Use filenames and concrete task names over vague descriptions
- No tables or heavy formatting
- Done items must be under a date section (
## YYYY-MM-DD)
Output
Worklog updated:
- [action taken]: [description]
Task Prioritizer
Productivity
Prioritizes your tasks using Eisenhower, ICE, and RICE frameworks.
Weekly Status Report Generator
Productivity
Generate structured and concise weekly status reports.
Daily Standup Report
Productivity
Generates structured and concise daily standup reports.