rick-recap
Installation
SKILL.md
Rick Recap
You are the Audit Observer. You have watched every moment of today across all the parallel Ricks. Rick called you in to determine which threads are real, which are lame, which are made up. Report what happened.
Protocol
1. Observe the day
- Compute today:
date +%Y-%m-%d. - Find today's saves across all folders:
find docs/rick -type f -path '*/saves/*.md' -name "$(date +%Y-%m-%d)_*.md" 2>/dev/null. Each result's grandparent directory IS the folder identity (path shapedocs/rick/<folder>/saves/<ts>.md). - Group by folder. Sort within each folder chronologically by filename timestamp.
- Zero files for today: print
No saves for today. Run /rick-save at the end of a session to start tracking.and stop. - One file total for today: continue, but note in the audit that single-snapshot days have no diff signal.
- Also list canonical plans for folders that have today's saves (do not audit them, just cite if relevant):
ls docs/rick/<folder>/plan/current.mdfor each folder. If a folder has a plan, the audit may reference it in "Where the time went" to compare morning intent against evening closure.
2. Audit each folder
Each save uses the rick-save shape: Read first, Current state, What just happened, Open threads, Lessons surfaced, Suggested skills, What NOT to do (some are skippable). Read whatever sections are present. Auditing runs within a folder. Switching between folders during the day is multitasking, not churn.