Worklog Task Management

VerifiedSafe

Updates worklog files by moving tasks between todo/doing/done states. Helps track progress, start new work, or mark tasks complete. Requires explicit arguments: state and description.

Sby Skills Guide Bot
ProductivityIntermediate
1306/2/2026
Claude Code
#worklog#task-tracking#productivity#file-management

Recommended for

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
When to use it

Use this skill during active development or sessions to log progress and maintain a clear task trail.

When not to use it

Do not use for items that are not yet part of the approved plan; instead, add them to the dedicated backlog file.

Security analysis

Safe
Quality score95/100

The 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

Mark task as done
worklog done Finished implementing the user authentication module in auth.py
Start working on a task
worklog doing Refactor database connection in db/connection.py
Add a task to backlog
worklog todo Write unit tests for the API endpoints

name: 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 — backlog
  • localdocs/worklog.doing.md — in progress
  • localdocs/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 complete
  • doing [description] — start working on a task
  • todo [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]

  1. Read worklog.doing.md; find matching item (keyword match, not exact)
  2. Remove the item from doing
  3. Append to worklog.done.md under today's date section (## YYYY-MM-DD), creating the section if absent
  4. If no match in doing, append directly to done without removing anything

doing [description]

  1. Read worklog.todo.md; find matching item
  2. Remove the item from todo
  3. Append to worklog.doing.md
  4. If no match in todo, append directly to doing

todo [description]

  1. 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]
Related skills