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.
The problem
Section titled “The problem”Without session continuity:
- You start a new AI session
- The AI asks “What are we working on?”
- You spend 10 minutes re-explaining context
- The AI makes assumptions about project state
- Work gets repeated or contradicted
The solution: two files
Section titled “The solution: two files”STATUS.md — Where the project is
Section titled “STATUS.md — Where the project is”STATUS.md tracks the project’s current state over time. It’s a living document updated at every checkpoint.
Sections:
| Section | Content |
|---|---|
| Project Overview | Type, goal, deployment target |
| Phase Tracking | Current phase with checkbox items |
| Health Indicators | Build status, test results, known issues |
| Key Decisions | Date, decision, rationale (table format) |
| Session History | What 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 integrationNEXT-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:
| Section | Content |
|---|---|
| What This Project Is | One-paragraph identity |
| Current Status | Completed items and remaining items |
| Immediate Next Steps | Prioritized list of what to do |
| Key Files | Table of important files and their purposes |
| Quick Reference | Common commands |
| Important Reminders | Gotchas, constraints, things not to forget |
How they work together
Section titled “How they work together”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 contextJimmy’s Workflow integration
Section titled “Jimmy’s Workflow integration”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.
Getting started
Section titled “Getting started”git clone https://github.com/ydun-code-library/Ydun_ai_workflow.gitcd Ydun_ai_workflowcp templates/core/STATUS.md.template /path/to/your-project/STATUS.mdcp templates/core/NEXT-SESSION-START-HERE.md.template /path/to/your-project/NEXT-SESSION-START-HERE.mdFill 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.