Codex Skill: Reflect
How to run a review — weekly, monthly, or quarterly. This is the X (eXamine) step in the CODEX method.
The Review Philosophy
Reviews are not administrative tasks. They are the mechanism by which the system learns. Without reflection, you capture and execute but never improve. The codex compounds in value exactly as much as you review it.
Weekly Review (Every Sunday, ~30 min)
- Open last week’s daily logs — scan
HP/29 Life Systems/Daily Notes/ - Open
_codex/templates/review.md— fill in a new weekly review - Answer the questions:
- What were the 3 biggest things that happened?
- What did I say I’d do that I didn’t? Why?
- What’s my energy level going into next week?
- What are my top 3 priorities for next week?
- Run inbox triage — use the
organizeskill - Check active projects — update status on any project files
Save as: HP/29 Life Systems/Reviews/YYYY-MM-DD-weekly.md
Monthly Review (1st of each month, ~60 min)
- Read the last 4 weekly reviews
- Fill in
_codex/templates/review.mdfor the full month - Run the Quadrant Check section — one paragraph per quadrant
- Review metrics against targets — update any tracking files
- Update
_codex/system/active-goals.md— are the priorities still right? - Close or archive completed projects
Save as: HP/29 Life Systems/Reviews/YYYY-MM-monthly.md
Quarterly Review (Jan/Apr/Jul/Oct, ~2-3 hours)
Everything in monthly, plus:
- Read all monthly reviews for the quarter
- Review major decisions made — are they holding up?
- Review long-term projects — are they on track?
- Update
_codex/system/identity.md— has anything shifted? - Set OKRs or theme for next quarter
Save as: HP/29 Life Systems/Reviews/YYYY-QN-quarterly.md
(e.g. 2026-Q1-quarterly.md)
Agent Support
AI agents can support the review process by:
- Summarizing daily logs for the review period
- Flagging unfinished items from previous reviews
- Identifying patterns across entries (recurring blockers, energy dips)
- Drafting the metrics table from tracked data