end-of-day-review

Write a dated end-of-day review file with goals and next steps.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill end-of-day-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: end-of-day-review
Source: https://github.com/tomzx/agents/tree/main/skills/end-of-day-review
Command: npx skills add https://github.com/tomzx/agents --skill end-of-day-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-day reflections are often skipped or inconsistent, leaving teams misaligned about what happened and what to do next. This guide provides a structured way to capture daily progress, assess alignment with personal and team goals, and prepare a concrete plan for tomorrow.

Core Features & Use Cases

  • Structured prompts that surface alignment between daily actions and goals.
  • Automatic creation of a daily review document that records decisions, learnings, and next steps.
  • Optional context integration by reading today’s activity summaries and goals to inform the review.

Quick Start

Run the end-of-day review to generate today’s {YEAR}/{MONTH}/{DAY}.review.md from available context.

Frequently Asked Questions about end-of-day-review

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

FAQPage Schema
How do I structure an end-of-day review to align daily work with goals?

An end-of-day review captures daily progress, assesses alignment with personal and team goals, and prepares a concrete plan for tomorrow's priorities. Structured prompts surface alignment between daily actions and goals.

What is the best way to track daily learnings and decisions for my team?

Tracking daily learnings and decisions is best handled by writing a dated review document that records decisions, learnings, and next steps to keep teams aligned about what happened and what to do next.

How do I generate a daily reflection markdown file automatically?

To generate a daily reflection markdown file, run the end-of-day review process which writes a dated review to a structured directory path using the current year, month, and day.

Can I integrate team goals into my daily reflection process?

You can integrate team goals into your daily reflection by placing a team-goals markdown file in your base directory, which the review process reads as optional context to inform the alignment assessment.

Do I need a goals file to run the end-of-day review?

You do not need a goals file to run the end-of-day review; context files like goals and team-goals are optional, allowing the review to function with or without predefined goal context.