# Developer Worklog Writer

> Use when the user wants a developer-style work log, daily engineering report, 업무일지, or progress summary that records work completed, changes made, validation performed, issues, risks, tools used, and next steps. Best for end-of-day summaries and OneDrive worklog updates.

- Skill: `kim-dh2417/developer-worklog-writer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kim-dh2417/developer-worklog-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kim-dh2417/developer-worklog-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: kim-dh2417 (https://skillmd.com/u/kim-dh2417)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/kim-dh2417/developer-worklog-writer

---


# Developer Worklog Writer

Write work logs for engineering work in a consistent, developer-oriented format.

## Use This Skill When

- The user asks for `업무일지`, daily report, engineering log, or today's work summary.
- The user wants the log to include technical details, validation, risks, or next steps.
- The user wants the result written into a file, especially a dated file in a fixed folder.

## Output Structure

Use this order unless the user asks otherwise:

1. `작업 개요`
2. `진행 업무`
3. `변경 사항`
4. `사용 기술 / 도구`
5. `작업 방식`
6. `검증 내역`
7. `이슈 / 리스크`
8. `산출물`
9. `다음 작업`

## Writing Rules

- Write from the perspective of work completed today.
- Prefer concrete changes over vague summaries.
- Name project, commit, key documents, or major files when relevant.
- Separate implementation, documentation, validation, and deployment status when useful.
- If the session included process improvements, record them under `작업 방식`.
- If the user experimented with repeatable workflows, add a short `Skill화 관점 메모` section.

## Quality Bar

- Make it readable by a lead or manager in one pass.
- Make it specific enough that the engineer can resume later from the log.
- Include verification status explicitly: lint, test, browser check, deploy status, etc.
- If deployment failed but push succeeded, record both separately.

## File Handling

- Reuse the user's established storage location if one exists.
- Prefer one dated file per day.
- If a prior day's worklog exists, follow its formatting unless the user has requested a new standard.