worklog

Track task progress by moving entries between worklog.todo.md, worklog.doing.md, and worklog.done.md files. You apply explicit state transitions during development sessions by providing a state argument and a task description to update your local worklog files.

Manage a sprint backlog by adding tasks to worklog.todo.md, moving active items to worklog.doing.md, and appending completed work under today's date in worklog.done.md. This explicit state transition approach keeps project work organized across local markdown files.

Move a task to done by running the worklog command with the done state and a task description. The process reads the source files and appends the completed task entry under today's date in worklog.done.md to record progress.

No, updating task state requires explicit arguments in the form of a state keyword and a description. You must provide the target state and task details to modify the corresponding worklog.todo.md, worklog.doing.md, or worklog.done.md files correctly.

Yes, task tracking with local markdown files is designed for development sessions and project work. It handles tasks as they are created, started, and completed by applying explicit state transitions across the worklog files.

State transitions fail when explicit arguments are not provided in the correct format. Ensure you specify the state and description accurately so the process reads the correct source files and appends entries to the right worklog markdown file.