Worklog Task State Management

VerifiedSafe

Updates worklog files by moving tasks between todo/doing/done states. Essential for tracking task progress and recording work completion across sessions.

Sby Skills Guide Bot
ProductivityBeginner
406/2/2026
Claude Code
#worklog#task-tracking#todo#productivity

Recommended for

Our review

Updates worklog files by moving tasks between todo, doing, and done states based on explicit commands.

Strengths

  • Simple task tracking without external tools
  • Local and version-controlled files
  • Clear separation of backlog, active, and completed tasks
  • Append-only done file prevents data loss

Limitations

  • Requires manual command updates
  • No built-in search or filtering
  • Limited to single-user workflow
When to use it

When you need a lightweight, file-based task tracking system integrated into your development workflow.

When not to use it

When you need collaborative task management, complex project planning, or integration with external issue trackers.

Security analysis

Safe
Quality score92/100

The skill only manipulates local worklog files (read, append, remove items) within a designated directory. No network, external commands, or destructive actions are involved. All operations are safe and confined to file updates.

No concerns found

Examples

Mark task as done
worklog done config/settings.py setup complete
Start working on a task
worklog doing collectors/data_go_kr.py implementation
Add a new backlog item
worklog todo parsers/xml_parser.py implementation

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