work-diary

Generate structured diary entries from session context into monthly markdown files.

1|Updated Dec 30, 2024
One-click install
npx skills add https://github.com/FarzamMohammadi/dev-toolbox --skill work-diary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-diary
Source: https://github.com/FarzamMohammadi/dev-toolbox/tree/main/ai/claude-code/skills/work-diary
Command: npx skills add https://github.com/FarzamMohammadi/dev-toolbox --skill work-diary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates the creation of portable diary entries from session context, reducing manual note-taking and ensuring consistent structure for reflections and decisions.

Core Features & Use Cases

  • Structured diary entries with sections: Intention, Work Done, Decisions & Rationale, Tools & Techniques, Learnings, Reflections.
  • Aggregates context from multiple sources (tickets, commits, conversations) into a monthly journal file (YYYY/month.md).
  • Guided Quick Start and optional prompts to clarify ambiguous context using AskUserQuestion.

Quick Start

Create a new diary entry for today and append it to YYYY/month.md using the default template, filling sections with the session context.

Frequently Asked Questions about work-diary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate engineering diary entries from session context?

Engineering diary entries are generated by aggregating session context from tickets, commits, and conversations into structured sections like Intention, Work Done, and Reflections. The skill appends each frontmatter-defined entry to a YYYY/month.md file.

What is the best way to document engineering decisions and rationale during a session?

Documenting engineering decisions and rationale is best handled by a structured diary template featuring dedicated sections for Decisions & Rationale, Tools & Techniques, and Learnings. This automated approach ensures consistent reflection and reduces manual note-taking.

How do I aggregate work journal entries into a monthly markdown file?

Aggregating work journal entries into a monthly markdown file is done by appending each session's diary entry to a YYYY/month.md file. The skill automates this by building frontmatter-defined entries from your current session context.

Can I use session context to capture engineering learnings and outcomes automatically?

Yes, you can capture engineering learnings and outcomes automatically from session context. The skill processes context from tickets, commits, and conversations to populate guided sections like Learnings and Reflections.

Does this engineering diary skill require any dependencies or external tools?

No, this engineering diary skill does not require any dependencies or external tools. It operates independently to generate portable diary entries and append them to your monthly markdown files.