How do I install the Worklog skill?

Run npx skillmds@latest add m0m0i/worklog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Worklog safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Worklog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Worklog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Worklog?

m0m0i (@m0m0i) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Worklog by m0m0i — Agent Skill

Name: Worklog
Author: m0m0i

File contents

worklog — Record the session

A spec says what was intended. A diff says what changed. Neither says why the approach shifted at 3pm, and that is the thing a future session — or a colleague — most needs and can least reconstruct.

Steps

Determine today's date. The target file is .work_logs/<YYYY-MM-DD>.md; create it if missing.
Gather facts rather than impressions: commits since the last entry, files changed, specs touched, decisions made, threads left open.
Append an entry from the template. Attribute it to whoever is running this.
Keep it skimmable. Bullets, not prose.

Entry template

## <YYYY-MM-DD> — <contributor>

### Summary
<1–2 lines: what moved>

### Activities
- <spec slug> (<issue>): <what happened, including Red/Green/Refactor progress>

### Decisions
- <decision> — <why, and what it rules out>

### Next steps
- [ ] <the specific next action, not "continue">

Rules

The entry rides the branch it describes. Run after implement, it is committed on the issue's branch and ships inside that issue's single pull request — it is never a pull request of its own.
Append. Never rewrite past entries. This is an audit trail; a corrected past is not one. If an earlier entry was wrong, say so in today's entry.
One section per session. Several people on the same day means several sections under that date, not a merged one.
Record decisions with their reasons, including the options rejected. A decision without its "why" gets re-litigated in three weeks by someone who has forgotten there was a reason.
Reference specs by slug and issues by number so entries cross-link to .specs/ and the tracker.
If the reviewer produced findings that were accepted rather than fixed, they belong in Decisions with the reason. Silent deferral is how a Medium becomes a Blocker later.

---name: worklogdescription: Append a dated entry to .work_logs/ summarizing what changed this session — activities, decisions, next steps. Use at the end of a working session or right after implement.---# worklog — Record the sessionA spec says what was intended. A diff says what changed. Neither says **why the approach shifted at 3pm**, and that is the thing a future session — or a colleague — most needs and can least reconstruct.## Steps1. Determine today's date. The target file is `.work_logs/<YYYY-MM-DD>.md`; create it if missing.2. Gather facts rather than impressions: commits since the last entry, files changed, specs touched, decisions made, threads left open.3. Append an entry from the template. Attribute it to whoever is running this.4. Keep it skimmable. Bullets, not prose.## Entry template```markdown## <YYYY-MM-DD> — <contributor>### Summary<1–2 lines: what moved>### Activities- <spec slug> (<issue>): <what happened, including Red/Green/Refactor progress>### Decisions- <decision> — <why, and what it rules out>### Next steps- [ ] <the specific next action, not "continue">```## Rules- **The entry rides the branch it describes.** Run after `implement`, it is committed on the issue's branch and ships inside that issue's single pull request — it is never a pull request of its own.- **Append. Never rewrite past entries.** This is an audit trail; a corrected past is not one. If an earlier entry was wrong, say so in today's entry.- One section per session. Several people on the same day means several sections under that date, not a merged one.- **Record decisions with their reasons**, including the options rejected. A decision without its "why" gets re-litigated in three weeks by someone who has forgotten there was a reason.- Reference specs by slug and issues by number so entries cross-link to `.specs/` and the tracker.- If the reviewer produced findings that were accepted rather than fixed, they belong in Decisions with the reason. Silent deferral is how a Medium becomes a Blocker later.

Frequently asked questions

Worklog