Nelleus

Session Resume

Oct 24th, 2026
16
0
Never
1
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.38 KB | None | 0 0
  1. Resume this project using the repository’s persistent documentation. Do not assume you have access to previous conversations.
  2.  
  3. Follow AGENTS.md and docs/SESSION_START_GUIDE.md. Read:
  4. - docs/SESSION_HANDOFF.md
  5. - docs/CONTEXT_HANDOFF.md
  6. - TASKS.md
  7. - Task-relevant technical references, decisions, and recent session records.
  8.  
  9. Verify the actual repository before relying on the handoff:
  10. - Confirm repository, branch, HEAD, and working-tree state.
  11. - Inspect relevant recent commits and uncommitted changes.
  12. - Check remote state when access is available, without overwriting local work.
  13. - Compare documented status with source code and available evidence.
  14.  
  15. Reconstruct what was completed, what remains, important decisions, known issues, and applicable constraints. Treat prior test results as historical unless rerun. Identify stale documentation, missing changes, discrepancies, and unavailable evidence explicitly.
  16.  
  17. Present a concise restart briefing covering:
  18. 1. Project purpose and current phase.
  19. 2. Previous work and changes since the handoff.
  20. 3. Actual Git state and any work requiring preservation.
  21. 4. Open tasks, blockers, and material risks.
  22. 5. Your recommended next action and how to verify it.
  23.  
  24. Do not modify application code or begin implementation yet. Stop after the briefing. If access or documentation is incomplete, explain the specific gap and what you could still verify.
Advertisement