21 lines
1.3 KiB
Markdown
21 lines
1.3 KiB
Markdown
Save current session state as an EEMS handover for the next session to pick up. Execute in order:
|
|
|
|
1. INVENTORY: List what was worked on this session — features built, configs changed, files modified, decisions made, ideas captured. Be exhaustive.
|
|
|
|
2. ARTIFACTS: List every file created or modified this session with full paths. Include configs, scripts, plugins, docs, plists — anything touched.
|
|
|
|
3. OPEN ITEMS: List unfinished work, next steps, blocked items, and pending decisions. Be specific — "write science agent prompt" not "finish agent work".
|
|
|
|
4. STORE: Write a single comprehensive memory to EEMS with subject `handover.session.YYYY-MM-DD` containing:
|
|
- Numbered sections matching the session's work areas
|
|
- Every artifact path
|
|
- Every open item as a clear action
|
|
- Session metadata (host, user, session ID if available)
|
|
- Cross-references to other EEMS entries created this session (by ID)
|
|
|
|
5. VERIFY: Read back the stored handover memory. Confirm it contains enough context for a fresh session with no prior context to resume work.
|
|
|
|
6. SIGNAL: Tell Pilot the handover is stored and which EEMS ID to reference. Remind them to run `/receive` in the next session.
|
|
|
|
Optimize for agentic retrieval — the consumer is another AI session, not a human. Use structured formats, explicit paths, concrete next-step verbs. No prose padding.
|