| name | session-notes |
| description | Use when writing or updating Engineering session notes. Covers the format, what to include, and filing location. |
Session Notes Procedure
When to Use
At the end of every Engineering work session, or during the session when significant work is completed. Session notes are the Engineering equivalent of HQ's memory log.
File Location
[ENGINEERING_REPO]/notes/session_YYYY-MM-DD.txt
One file per day. Append to existing file if multiple sessions in a day.
Format
=== Session: YYYY-MM-DD HH:MM CDT ===
## Summary
[2-3 sentence overview of what was accomplished]
## Work Completed
- [Specific task/change with file references]
- [Test results: N passing, N new, N regressions]
- [Branch: branch-name, commit: hash]
## Decisions Made
- [Decision with rationale]
- [XD-NNN reference if cross-org]
## Issues Found
- [Bug/gap with severity and owner]
## Next Steps
- [What needs to happen next]
- [Blockers for HQ if any]
## Files Changed
- [List of key files modified]
Rules
- Always include test counts (passing, new, regressions)
- Always include branch and commit info
- Reference XD- IDs for cross-org decisions
- Flag anything that needs HQ input explicitly
- Update
../../../shared_context/project_status_sync.STUB.md if milestones change
