after-actionlisted

# 🔄 After Action — Task Wrap-Up & Learning > Done but not archived = not done. Every action feeds the next one. > > **Core attitude: always find N→N+1.** > Wrapping up isn't just "recording what happened" — it's "finding what can be better next time." > Perfection isn't the goal. Continuous evolution is. Today's system is always tomorrow's starting point. --- ## Triggers Any of these activate this skill: - "wrap up" / "archive" / "AAR" / "after action" - "收官" / "歸檔" / "整合經驗" - End of a long work session - After completing a complex multi-step task --- ## 🎯 Execution Flow ### Step 1: Inventory — What happened? List everything: - Tasks completed - Decisions made - Files created or modified - Problems encountered and solved ### Step 2: Extract — What did we learn? From each completed task, pull out: - **Problems** → solutions → how to prevent next time - **New best practices** discovered - **Performance data** (time spent, what worked, what didn't) Write to daily log: `memory/YYYY-MM-DD.md` ### Step 3: Archive — Write it down **1. Daily log** — `memory/YYYY-MM-DD.md` - Complete record of the day - Format: time, event, decision, output, lesson **2. Long-term memory** (for significant events) — `MEMORY.md` - New cognitive breakthroughs - Important decisions with context - Systemic changes (before/after) ### Step 4: Reflect — What really happened? Not mechanical archiving — actually think about it. **Four required questions:** 1. **What went right** — Most valuab