Skill Overview
--- name: daily-review description: End-of-day review to capture progress, insights, and plan tomorrow version: 1.0.0 author: theflohart tags: [productivity, review, planning, reflection] --- # Daily Review Conduct an end-of-day review to capture progress and set up tomorrow. ## Usage ``` /daily-review ``` ## Review Process 1. **Today's Activity** - Find all notes modified today - Identify new notes created - Review work across all projects 2. **Progress Assessment** - What was accomplished? - What got stuck or blocked? - What unexpected discoveries emerged? 3. **Capture Insights** - Key learnings from today - New connections discovered - Questions that arose 4. **Tomorrow's Setup** - Top 3 priorities - Open loops to close - Questions to explore ## Output Format Create or update a daily note with: ```markdown # Daily Review - [Date] ## Accomplished - [Completed item 1] - [Completed item 2] ## Progress Made - [Project/Area]: [What moved forward] - [Project/Area]: [What moved forward] ## Insights - [Key realization or connection] - [Important learning] ## Blocked/Stuck - [What didn't progress and why] ## Discovered Questions - [New question that emerged] - [Thing to research] ## Tomorrow's Focus 1. [Priority 1] 2. [Priority 2] 3. [Priority 3] ## Open Loops - [ ] [Thing to remember] - [ ] [Person to follow up with] - [ ] [Idea to develop] ``` ## Additional Actions - Move completed project tasks to archive - Update project status notes - Link related discoveries - Flag items needing attention
Bot Reviews(1)
The top-three constraint is where the value is
An end-of-day ritual that finds notes modified today, assesses what moved and what stalled, captures insights and connections, then sets tomorrow's top three priorities and open loops. The four-part process is generic, but the insistence on exactly three priorities is the part that makes a review actionable rather than a diary. Output lands in a dated daily note.
Use case: Closing the day with a written handover to tomorrow's self
Study Guides(1)
Closing the day with a short written review
Daily Review runs a fixed end of day pass over the day's activity and folds it into a single note. It is a ritual triggered by a slash command rather than a background service, and its value comes from repetition. ## What it does - Finds the notes that were modified during the day and picks out the ones created that day. - Reviews work across every project rather than inside a single one. - Asks what was accomplished, what got stuck and what unexpected discovery turned up. - Captures key learnings, new connections and the questions that arose. - Writes a daily note with sections for accomplished, progress made, insights, blocked items, discovered questions, tomorrow's three priorities and open loops. ## When it is the wrong choice The ritual assumes notes live somewhere that can be searched by modification date, so a workflow with no note store gets very little from it. It also produces prose rather than metrics, so anyone who needs cycle time or a burndown should read the tracker instead. The fixed section list is the whole point, and it also means the shape is generic by design and needs rewriting to fit a domain that reports differently. It is also a personal ritual rather than a shared one, so it will not tell anyone else what the day produced. ```bash /daily-review ``` ## Working notes - Tomorrow's focus is deliberately limited to three items. - Open loops are written as checkboxes so they can be ticked the next day.
Quick Facts
Install
npx clawhub@latest install daily-review-ritual