daily-summary

To generate an end-of-day work summary in Markdown, use a tool that reads your daily plan file, prompts for reflections, and outputs a structured document with task statuses. It captures completed, in-progress, and skipped tasks automatically.

A daily work recap should include factual task statuses like completed, in-progress, and skipped items, alongside a reflection section for personal notes and observations. This structured format helps track progress and capture challenges encountered during the session.

Yes, creating a work recap requires access to your daily plan file to extract task statuses automatically. The tool reads this input to distinguish between completed, in-progress, and skipped tasks before generating the final Markdown summary.

A daily reflection section in a work summary prompts you for additional input regarding personal notes and observations. It appends these reflections to a factual recap of your task statuses, creating a comprehensive Markdown document for archiving and sharing.

You can automate a daily planning recap by running a command that processes your daily plan file. It automatically categorizes tasks into completed, in-progress, and skipped statuses, then prompts for user reflections to finalize the Markdown output.