KS
Killer-Skills

worklog — how to use worklog how to use worklog, worklog setup guide, worklog alternative, worklog vs trello, worklog install, what is worklog, worklog for AI agents, task state management with worklog, worklog file format

v1.0.0
GitHub

About this Skill

Ideal for Task Management Agents requiring organized workflow tracking and explicit state updates in Markdown files. worklog is a task state management system that updates worklog files, including localdocs/worklog.todo.md, localdocs/worklog.doing.md, and localdocs/worklog.done.md, to track task progress.

Features

Updates task state in worklog files using explicit arguments
Supports three worklog file types: backlog, in-progress, and completed
Uses append-only mode for completed tasks in localdocs/worklog.done.md
Requires specific argument format: [state] [description]
Allows marking tasks as done using the 'done [description]' command

# Core Topics

taewook486 taewook486
[0]
[0]
Updated: 2/28/2026

Quality Score

Top 5%
54
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
Cursor IDE Windsurf IDE VS Code IDE
> npx killer-skills add taewook486/real-estate-mcp/worklog

Agent Capability Analysis

The worklog MCP Server by taewook486 is an open-source Categories.community integration for Claude and other AI agents, enabling seamless task automation and capability expansion. Optimized for how to use worklog, worklog setup guide, worklog alternative.

Ideal Agent Persona

Ideal for Task Management Agents requiring organized workflow tracking and explicit state updates in Markdown files.

Core Value

Empowers agents to manage tasks efficiently by updating state in worklog files, utilizing explicit arguments for task management, and organizing tasks into backlog, in-progress, and completed categories using Markdown files like `worklog.todo.md`, `worklog.doing.md`, and `worklog.done.md`.

Capabilities Granted for worklog MCP Server

Updating task states in worklog files for project tracking
Organizing tasks into backlog, in-progress, and completed categories for team management
Marking tasks as done using the `done` argument for progress tracking

! Prerequisites & Limits

  • Requires explicit arguments for task management
  • Limited to local file system access for worklog files
  • Append-only for completed tasks in `worklog.done.md`
Project
SKILL.md
2.1 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

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

Looking for an alternative to worklog or building a Categories.community AI Agent? Explore these related open-source MCP Servers.

View All

widget-generator

Logo of f
f

widget-generator is an open-source AI agent skill for creating widget plugins that are injected into prompt feeds on prompts.chat. It supports two rendering modes: standard prompt widgets using default PromptCard styling and custom render widgets built as full React components.

149.6k
0
Design

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

72.8k
0
Communication