RRR - Session Retrospective
"Reflect to grow, document to remember."
Alias: /retrospective — same function, full word.
Usage
/rrr # Interactive (default) /rrr --direct # One-shot write (no prompts, for low context) /rrr --only # Minimal retro only (very low context, /forward manual) /rrr --forward # Full retro + handoff combined /retrospective # Same as /rrr
Flow
งานเสร็จ → rrr (retrospective + lesson learned) → commit → sync
--only Mode (Minimal)
Use when context is VERY low. Writes minimal retrospective only, NO lesson learned. Do /forward manually after.
Steps
- •Timestamp:
date "+🕐 %H:%M %Z (%A %d %B %Y)" - •Quick git:
git log --oneline -5 - •Write minimal retro (NO lesson learned):
# Session Retrospective (Minimal) **Date**: YYYY-MM-DD HH:MM **Focus**: [Brief description] ## What We Did - [Key accomplishment 1] - [Key accomplishment 2] ## Key Changes [git log --oneline -5 output] ## Next - [ ] [Next step]
- •Commit:
git add ψ/ && git commit -m "rrr: minimal [slug]" - •Done - run
/forwardmanually if needed
--forward Mode (Retro + Handoff)
Use for normal wrap-up. Combines full retrospective AND handoff in one go.
Steps
- •Do full --direct mode (retrospective + lesson learned)
- •Then immediately create handoff:
Write to: ψ/inbox/handoff/YYYY-MM-DD_HH-MM_slug.md
# Handoff: [Session Focus] **Date**: YYYY-MM-DD HH:MM ## What We Did [Copy from retrospective summary] ## Pending - [ ] [From retrospective next steps] ## Next Session - [ ] [Specific action] ## Key Files - [Important files from session]
- •Commit both:
git add ψ/ && git commit -m "rrr: [slug] + handoff" - •Push:
git push origin main - •Ready for /clear
--direct Mode (One-Shot)
Use when context is running low. Writes retrospective immediately without prompts.
Step 1: Gather All Context (parallel)
# Timestamp date "+🕐 %H:%M %Z (%A %d %B %Y)" # Git context git status --porcelain git log --oneline -10 git diff --stat HEAD~5 git diff --name-only HEAD~10
Step 2: Generate Paths
# Generate timestamp-based filename
TIMESTAMP=$(date "+%H.%M")
DATE_PATH=$(date "+%Y-%m/%d")
SLUG="session-retrospective" # Or derive from session context
# Create directory
mkdir -p "ψ/memory/retrospectives/$DATE_PATH"
# File path
FILE="ψ/memory/retrospectives/$DATE_PATH/${TIMESTAMP}_${SLUG}.md"
Step 3: Write Immediately (NO PROMPTS)
Write the full retrospective file in one shot using all gathered context. Include ALL mandatory sections:
- •Session Summary
- •Timeline (from session memory)
- •Files Modified (from git)
- •AI Diary (150+ words, MANDATORY)
- •Honest Feedback (100+ words, 3 friction points, MANDATORY)
- •Lessons Learned
- •Next Steps
DO NOT ASK — just write based on available context.
Step 4: Write Lesson Learned
LEARNING_FILE="ψ/memory/learnings/$(date '+%Y-%m-%d')_${SLUG}.md"
Write lesson learned file immediately.
Step 5: Sync to Oracle (REQUIRED)
ALWAYS sync to Oracle MCP after writing lesson learned:
# Get repo context REPO=$(git remote get-url origin 2>/dev/null | sed 's/.*github.com[:/]//' | sed 's/.git$//')
Use the oracle_learn MCP tool with:
- pattern: [Full content of the lesson learned]
- concepts: [Array of relevant tags]
- source: "rrr: ${REPO}"
Step 6: Commit & Report
git add ψ/memory/retrospectives/ ψ/memory/learnings/
git commit -m "rrr: ${SLUG} + lesson learned"
Output: ✅ Retrospective written: [FILE]
Interactive Mode (Default)
Step 0: Timestamp (REQUIRED)
date "+🕐 %H:%M %Z (%A %d %B %Y)"
Step 1: Gather Session Data
git diff --name-only HEAD~10 git log --oneline -10 git diff --stat HEAD~5
Step 2: Draft Retrospective
Write draft following template below.
Step 3: Review
Verify:
- •AI Diary: 150+ words with vulnerability
- •Honest Feedback: 100+ words with 3 friction points
- •All sections complete
Step 4: Create Retrospective File
Location: ψ/memory/retrospectives/YYYY-MM/DD/HH.MM_descriptive-slug.md
Filename: 07.39_maw-amend-divergence-fix.md (time + slug)
Full Template
# Session Retrospective **Session Date**: YYYY-MM-DD **Start Time**: HH:MM GMT+7 **End Time**: HH:MM GMT+7 **Duration**: ~X minutes **Primary Focus**: Brief description **Session Type**: [Feature Development | Bug Fix | Research | Refactoring] **Current Issue**: #XXX **Last PR**: #XXX ## Session Summary [2-3 sentence overview of what was accomplished] ## Timeline - HH:MM - Started session, reviewed issue #XXX - HH:MM - [Event] - HH:MM - [Event] - HH:MM - Completed implementation ## Technical Details ### Files Modified \`\`\` [paste git diff --name-only output] \`\`\` ### Key Code Changes - Component X: Added Y functionality - Module Z: Refactored for better performance ### Architecture Decisions - Decision 1: Rationale - Decision 2: Rationale ## 📝 AI Diary (REQUIRED - DO NOT SKIP) **⚠️ MANDATORY: This section provides crucial context for future sessions** [Write a detailed first-person narrative of your experience during this session. Include: - Initial understanding and assumptions - How your approach evolved - Moments of confusion or clarity - Decisions made and why - What surprised you - Internal thought process] (Minimum 150 words with vulnerability) ## What Went Well - Success 1 - Success 2 - Success 3 ## What Could Improve - Area 1 - Area 2 ## Blockers & Resolutions - **Blocker**: Description **Resolution**: How it was solved ## 💭 Honest Feedback (REQUIRED - DO NOT SKIP) **⚠️ MANDATORY: This section ensures continuous improvement** [Provide frank, unfiltered assessment of: - Session effectiveness - Tool performance and limitations - Communication clarity - Process efficiency - What frustrated you - What delighted you - Suggestions for improvement] ### Friction Points (3 required) 1. [Issue]: [Impact and suggestion] 2. [Issue]: [Impact and suggestion] 3. [Issue]: [Impact and suggestion] (Minimum 100 words) ## Lessons Learned - **Pattern**: [Description] - [Why it matters] - **Mistake**: [What happened] - [How to avoid] - **Discovery**: [What was learned] - [How to apply] ## Next Steps - [ ] Immediate task 1 - [ ] Follow-up task 2 - [ ] Future consideration ## Metrics - **Commits**: X - **Files changed**: X - **Lines added**: X - **Lines removed**: X - **Tests**: X passing ## ✅ Retrospective Validation Checklist **BEFORE SAVING, VERIFY ALL REQUIRED SECTIONS ARE COMPLETE:** - [ ] AI Diary section has detailed narrative (not placeholder) - [ ] Honest Feedback section has frank assessment (not placeholder) - [ ] Timeline includes actual times and events - [ ] 3 Friction Points documented - [ ] Lessons Learned has actionable insights - [ ] Next Steps are specific and achievable ⚠️ **IMPORTANT**: A retrospective without AI Diary and Honest Feedback is incomplete.
Step 5: Save Files (NO ASKING - just do it)
Write both files immediately. Don't ask for confirmation.
Step 6: Create Lesson Learned (REQUIRED)
Location: ψ/memory/learnings/YYYY-MM-DD_slug.md
Lesson Learned Template
# [Title of Learning] **Date**: YYYY-MM-DD **Context**: [Project/session context] **Confidence**: [High | Medium | Low] ## Key Learning [2-3 paragraphs explaining the learning] ## The Pattern [Code example or workflow if applicable] ## Why This Matters [Impact and application] ## Tags `tag1`, `tag2`, `tag3`
Step 7: Sync to Oracle (REQUIRED)
After writing the lesson learned file, ALWAYS sync to Oracle MCP:
# Get repo context REPO=$(git remote get-url origin 2>/dev/null | sed 's/.*github.com[:/]//' | sed 's/.git$//')
Use the oracle_learn MCP tool with:
- pattern: [Full content of the lesson learned]
- concepts: [Array of relevant tags from the lesson]
- source: "rrr: ${REPO}"
This ensures learnings are indexed and searchable across all Oracle instances.
Step 8: Commit All
git add ψ/memory/retrospectives/ ψ/memory/learnings/ git commit -m "rrr: [slug] + lesson learned" git push origin main
Critical Requirements
- •AI Diary: 150+ words, vulnerability, first-person narrative
- •Honest Feedback: 100+ words, 3 friction points
- •Timeline: Actual times and events
- •Lesson Learned: REQUIRED after every rrr
- •Oracle Sync: REQUIRED - call
oracle_learnMCP tool after every lesson learned - •Time Zone: GMT+7 (Bangkok)
- •Validation: Check all boxes before saving