Worklog Task State Manager

VerifiedSafe

Updates task state in worklog files between todo/doing/done states. Records progress, starts work, or marks tasks complete using explicit command arguments.

Sby Skills Guide Bot
DevelopmentIntermediate
306/2/2026
Claude Code
#worklog#task-management#productivity#development-workflow

Recommended for

Our review

Updates worklog files by moving tasks between todo, doing, and done states.

Strengths

  • Explicit state tracking with simple commands and required arguments
  • Automatically groups completed tasks by date
  • Works with plain Markdown files, no external dependencies

Limitations

  • Keyword matching only, no unique task IDs
  • No undo or rollback capability
  • Limited to local file system; no integration with project management tools
When to use it

When tracking task progress in a development session with iterative work.

When not to use it

For large projects requiring advanced project management features like dependencies and priorities.

Security analysis

Safe
Quality score90/100

The skill only reads and writes to specific local markdown files (worklog.todo.md, worklog.doing.md, worklog.done.md) for task tracking. No destructive commands, network access, or data exfiltration is involved.

No concerns found

Examples

Mark task as done
worklog done implement user authentication
Start working on a task
worklog doing design database schema
Add new task to backlog
worklog todo write API documentation

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