Skip to content

Session Continuity

Session continuity solves the biggest pain point in AI-assisted development: every new session starts with zero context. STATUS.md and NEXT-SESSION-START-HERE.md work together to give incoming AI assistants immediate orientation.

Without session continuity:

  1. You start a new AI session
  2. The AI asks “What are we working on?”
  3. You spend 10 minutes re-explaining context
  4. The AI makes assumptions about project state
  5. Work gets repeated or contradicted

STATUS.md tracks the project’s current state over time. It’s a living document updated at every checkpoint.

Sections:

SectionContent
Project OverviewType, goal, deployment target
Phase TrackingCurrent phase with checkbox items
Health IndicatorsBuild status, test results, known issues
Key DecisionsDate, decision, rationale (table format)
Session HistoryWhat each session accomplished

Example entry:

### Session 3 — 2026-02-15
**Focus**: Authentication implementation
**Accomplished**:
- Implemented JWT auth with refresh tokens
- Added rate limiting middleware
- Tests passing: 47/47
**Remaining**: OAuth2 integration

NEXT-SESSION-START-HERE.md — What to do next

Section titled “NEXT-SESSION-START-HERE.md — What to do next”

NEXT-SESSION-START-HERE.md is the orientation document for the next AI session (or the next human picking up the project). It’s updated at the end of every work session.

Sections:

SectionContent
What This Project IsOne-paragraph identity
Current StatusCompleted items and remaining items
Immediate Next StepsPrioritized list of what to do
Key FilesTable of important files and their purposes
Quick ReferenceCommon commands
Important RemindersGotchas, constraints, things not to forget
Session ends:
→ Update STATUS.md (session history, phase checkboxes)
→ Update NEXT-SESSION-START-HERE.md (next steps, current state)
New session starts:
→ AI reads AGENTS.md (project context)
→ AI reads NEXT-SESSION-START-HERE.md (what to do now)
→ AI reads STATUS.md if needed (deeper history)
→ Work begins with full context

The CHECKPOINT phase of Jimmy’s Workflow includes updating these files:

CHECKPOINT: Mark complete with validity conditions

  • Update STATUS.md with what was accomplished
  • Update NEXT-SESSION if the session might end

This makes session continuity part of the workflow, not an afterthought.

Terminal window
git clone https://github.com/ydun-code-library/Ydun_ai_workflow.git
cd Ydun_ai_workflow
cp templates/core/STATUS.md.template /path/to/your-project/STATUS.md
cp templates/core/NEXT-SESSION-START-HERE.md.template /path/to/your-project/NEXT-SESSION-START-HERE.md

Fill in the project identity sections, then update them at each checkpoint. The templates have clear placeholder markers for every section.

  • STATUS.md grows over time — Don’t trim session history. It’s valuable context for understanding why decisions were made.
  • NEXT-SESSION-START-HERE.md is always current — Unlike STATUS.md which accumulates, this file should reflect the present state only.
  • Be specific in next steps — “Continue auth work” is useless. “Implement OAuth2 callback handler in src/auth/oauth.ts, test with Google provider” is actionable.
  • Include the commands — If the next step requires running something, put the exact command in the file.