work-log

Name: work-log
Availability: InStock
Author: neighbor-game-ai

Maintain date-stamped Markdown logs linked to a central TODO.md.

Updated Aug 27, 2026

Search Tags:#logs #notes #todo #project-management #task-tracking #work-log

Ready to run

npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill work-log-neighbor-game-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-log
Source: https://github.com/neighbor-game-ai/DreamCore-V2-sandbox/tree/main/.claude/skills/work-log
Command: npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill work-log-neighbor-game-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams systematically record and manage per-project work history by linking detailed logs with TODO references, ensuring traceability and accountability.

Core Features & Use Cases

Structured logging: Create and maintain a .claude/logs directory with date-stamped entries that capture tasks, owners, and outcomes.
Plan-to-log linkage: Use the .claude/plans directory to store planned work and tie it to actual notes in logs and updates in TODO.md.
Use Case: A project team can review a month's work by querying logs for specific tasks and cross-referencing progress in the central TODO.md.

Quick Start

Create the .claude/logs and .claude/plans directories, then start adding dated task logs and updating the project TODO.md to reflect progress.

Frequently Asked Questions about work-log

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

FAQPage Schema

How do I track project work logs with linked TODO references?▼

To track project work logs, this skill creates a .claude/logs directory with date-stamped Markdown entries and links them to a central TODO.md. This setup ensures granular task tracing and accountability across software projects.

What is the best way to maintain compliance-ready task histories for software projects?▼

Compliance-ready task histories are maintained by capturing detailed, date-stamped Markdown logs with owners and outcomes. This deterministic file structure provides the granular tracing needed for retrospective reviews and compliance audits.

How do I link planned project work to actual task logs?▼

You can link planned work to task logs by storing plans in a .claude/plans directory and tying them to dated notes in the logs directory. Updates are then cross-referenced in the central TODO.md to reflect actual progress.

Can I use this work-log skill for retrospective reviews across multiple projects?▼

Yes, this skill supports retrospective reviews for project teams by organizing per-project work history. You can query date-stamped logs for specific tasks and cross-reference progress in the central TODO.md.

Do I need to manually create directories to start tracking project work logs?▼

No, the quick start process involves creating the .claude/logs and .claude/plans directories. Once created, you can start adding dated task logs and updating the project TODO.md to reflect progress seamlessly.

What limitations exist when using Markdown files for project task tracking?▼

Using Markdown files for project task tracking relies on a deterministic file structure without external databases. This approach is designed for granular task tracing and documentation, but may lack real-time synchronization features found in dedicated project-management platforms.