Session Documenter Skill
Automatically document all work, decisions, and context throughout the session for continuity.
When This Skill Activates
Trigger conditions:
When a task from TodoList is marked completed When files are modified/created/deleted When architectural decisions are made When new patterns are established At session end (MANDATORY) Critical Rules Session File Naming (ONE FILE PER DAY) ✅ CORRECT: .agent/SESSIONS/2025-11-15.md ❌ WRONG: .agent/SESSIONS/2025-11-15-feature-name.md
Multiple sessions same day → Same file, Session 1, Session 2, etc.
Flowcharts (MANDATORY for features)
Include flowchart for:
New features Feature modifications Multi-component bug fixes Session Entry Structure Session number and title System flow diagram (mermaid or text) Affected components (frontend, backend, data, external) What was done (task checklist) Key decisions (with rationale) Files changed Mistakes and fixes Next steps Related Files to Update .agent/SESSIONS/README.md .agent/SYSTEM/SUMMARY.md .agent/TASKS/*/TODO.md .agent/SYSTEM/ARCHITECTURE.md (if architectural decisions) References Full guide: Phases, automation, validation, examples