worklog
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].
Best use case
worklog is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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].
Teams using worklog should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/worklog/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How worklog Compares
| Feature / Agent | worklog | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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].
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
template-proposal-review
Review proposal files in localdocs/localdocs/proposals/ and decide whether to apply them to the upstream python-project-template repository. Use when evaluating proposals generated by template-upstream, deciding which ones to accept or reject, and applying accepted ones to the template repo. Triggers on: "proposal 검토", "제안 검토", "template에 반영할지", "proposals 리뷰", "upstream 반영 결정".
template-downstream
Update .claude/, .mcp.json, and .pre-commit-config.yaml from the upstream python-project-template repository into the current project. Only files that exist upstream are updated — project-only files are never deleted. Use when pulling latest tooling, rules, hooks, or skills from the canonical template into this project. Triggers on: "템플릿 최신화", "template sync", "upstream 반영", "template 업데이트".
template-broadcast
Apply template-downstream to all registered downstream projects in bulk, one project at a time. Use when you want to push the latest .claude/, .mcp.json, or .pre-commit-config.yaml to every project at once. Triggers on: "일괄 배포", "전체 프로젝트에 내려보내기", "모든 프로젝트 업데이트", "broadcast template", "bulk sync".
tdd
Test-Driven Development workflow. Use for ALL code changes - features, bug fixes, refactoring. TDD is non-negotiable.
sparks-create
Apply the 13 thinking tools from "Sparks of Genius" (생각의 탄생) to reframe any problem through creative, cross-disciplinary lenses. Use when conventional analysis falls short, when you need a fresh creative angle, or when the problem spans multiple domains.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
rethink-unblock
Break out of a stuck approach by reframing a technical problem through structured thinking frameworks. Use when blocked, going in circles, or when a fresh perspective is needed on architecture, design, or debugging.
refactoring
Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities.
python-mcp-expert
Expert assistant for developing Model Context Protocol (MCP) servers in Python. Use when creating, debugging, or optimizing MCP servers with FastMCP, tools, resources, and prompts.
python-conventions
Python coding conventions and guidelines including PEP 8, type hints, docstrings, and testing standards. Automatically applied when working with Python files.
prd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
planning
Planning work in small, known-good increments. Use when starting significant work or breaking down complex tasks.