work-logs

Record AI task work logs into daily markdown files with structured entries.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AoManoh/project_templates --skill work-logs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-logs
Source: https://github.com/AoManoh/project_templates/tree/main/skills/work-logs
Command: npx skills add https://github.com/AoManoh/project_templates --skill work-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how an AI records work so decisions, actions, debugging results, and learnings persist in files instead of disappearing inside chat history.

Core Features & Use Cases

  • Work log per day: Writes entries into docs/work-logs/YYYY-MM-DD.md using real China/Shanghai time to keep timelines consistent.
  • Structured, reusable entries: Enforces a minimum set of fields (what/why/changed files) and expands with richer sections for complex troubleshooting or decision-making.
  • Daily summary that stays last: Maintains a 今日日志总结 section at the end of the log document and updates it after each task.
  • Self-check for future recoverability: Requires a verification pass to ensure the log remains understandable and helpful months later.

Quick Start

Ask your AI agent to record today’s work into the repository’s docs/work-logs using the work-logs templates.

Frequently Asked Questions about work-logs

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

FAQPage Schema
How do I record AI task work logs into markdown files for later recovery?

Recording AI task work logs into markdown files involves appending structured entries into a daily file named YYYY-MM-DD.md. This process preserves decisions, actions, and debugging results in your repository instead of losing them inside chat history.

What is the best way to maintain a development workflow evidence trail?

The best way to maintain a development workflow evidence trail is to enforce a self-check verification pass on structured markdown entries. This ensures each completed task logs what, why, and changed files, remaining understandable months later.

How does time stamping work for daily markdown work logs?

Time stamping for daily markdown work logs uses real Asia/Shanghai time to choose the correct `docs/work-logs/YYYY-MM-DD.md` file. This keeps timelines consistent across end-to-end development, debugging, and refactoring workflows.

Can I use markdown work logs for debugging and refactoring workflows?

You can use markdown work logs for debugging and refactoring workflows by expanding structured entries with richer sections for complex troubleshooting. Each completed task leaves an evidence trail detailing decisions and changed files.

Do I need to update the daily summary manually after appending work log entries?

You need to update the daily summary after appending work log entries to keep it at the end of the markdown document. The Skill maintains a `今日日志总结` section and updates it after each task completion.