kim-dh2417 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:
작업 개요진행 업무변경 사항사용 기술 / 도구작업 방식검증 내역이슈 / 리스크산출물다음 작업
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.