skills.rest
tomwangowa
tomwangowaCOMMUNITY
Explore all skills by this author →
GitHub

work-log-analyzer

Parse Markdown work logs to track TODOs, decisions, and timeline events.

1|Updated Jan 10, 2026
Search Tags:#task management#log analysis#journaling#developer productivity#decision tracking#project history
One-click install
npx skills add https://github.com/tomwangowa/agent-skills --skill work-log-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-log-analyzer
Source: https://github.com/tomwangowa/agent-skills/tree/main/work-log-analyzer
Command: npx skills add https://github.com/tomwangowa/agent-skills --skill work-log-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers quickly find information, track task progress, understand decision evolution, and manage TODOs directly from their work logs and journals.

Core Features & Use Cases

  • Query Project History: Understand how features or decisions evolved over time.
  • Manage TODOs: Track pending, overdue, and completed tasks.
  • Extract Decision Rationale: Discover why certain technical choices were made.
  • Use Case: You need to recall when a specific feature was decided upon and why. This Skill can scan your work logs to provide a timeline and the reasoning behind that decision.

Quick Start

Analyze the file 'example_worklog.md' to find all outdated TODO items.

Frequently Asked Questions about work-log-analyzer

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

FAQPage Schema
How do I extract decision rationale and track project history from work logs?▼

You can analyze work logs and development notes to track project evolution and understand decision rationale. It identifies specific patterns in Markdown to provide a timeline of technical choices and events.

How do I find outdated or pending TODOs in Markdown development notes?▼

You can analyze Markdown development notes to find outdated TODOs by identifying specific task patterns. The skill scans structured or unstructured logs to track pending, overdue, and completed tasks.

Can I search for keywords and timeline events in unstructured developer journals?▼

Yes, you can perform general keyword searches and timeline queries within unstructured developer journals. The skill parses Markdown formats to identify chronological events and track project history.

Does this work with unstructured Markdown journals or do I need a specific format?▼

It works with both structured and unstructured Markdown work logs. You do not need a specific format, as it identifies patterns for tasks, decisions, and chronological events directly from the text.

What is the best way to analyze work logs to understand feature evolution?▼

The best way to analyze work logs for feature evolution is to run timeline queries on your development notes. This tracks project history and reveals when specific features were decided upon.

Related Skills

Explore More Software Engineering Skills→
justinsenseijustinsensei
1

obsidian-logs

Create and format chronological logs in Obsidian with markdown structure.

Community
Advanced
alexgrebeshok-coderalexgrebeshok-coder
8

executive-dashboard

Generate weekly and monthly executive project portfolio dashboards and reports.

Community
Advanced
mrgeoffrichmrgeoffrich
3

execute-next-task

Claim and execute next unblocked project ticket with environment setup and test runs.

Community
Advanced
flowelflowel

xinchao-work-assistant

Manage local AI work directories and track Markdown tasks with PowerShell.

Community
Advanced