session-handoff-resume

Session Handoff & Resume (2026 — Cross-Model Edition)

English | Bahasa Indonesia

---

English

Orchestration & Integration

Connects and orchestrates with relevant domain skills like brainstorming, zero-to-prod-orchestrator, and project-context-mapper to ensure cohesive execution.

Description

Saves ultra-compact project checkpoints and enables seamless work resumption across new chat sessions, different accounts, or different AI models (Gemini, Claude, GPT). Designed for minimum token consumption while preserving full context needed for continuation.

Trigger Conditions

• Session is running very long and context window is nearly exhausted.
• User wants to switch to a new chat session or different AI model.
• User wants to save progress before closing and resume later.
• User says "save checkpoint", "handoff", "save progress", "resume later".

Checkpoint Format (Ultra-Compact)

When creating a checkpoint, output a compact YAML block under 200 tokens:

# CHECKPOINT — [Project Name] — [Date]
project: "[Project Name]"
goal: "[One-line goal of the current session]"
status: "[brief status: e.g., '60% — backend API done, frontend in progress']"
stack: "[e.g., Next.js 15 + Hono + Supabase + Drizzle]"
last_completed:
  - "[Most recent task completed]"
  - "[Second most recent]"
next_tasks:
  - "[Immediate next task]"
  - "[Following task]"
  - "[Following task]"
blockers: "[Any known blockers or pending decisions, or 'none']"
key_files:
  - "[path/to/critical/file.ts]"
  - "[path/to/another/file.ts]"
env_needed: "[List of env vars needed, e.g., SUPABASE_URL, STRIPE_KEY]"
notes: "[Any critical context that doesn't fit above]"

Cross-Model Handoff Protocol (2026)

Different AI models interpret context differently. Use this universal handoff prompt:

## RESUME CONTEXT — [Project Name]

You are resuming work on [Project Name]. Read this context carefully before taking any action.

**Goal**: [One-sentence project goal]
**Current Status**: [What's been done, what's pending]
**Tech Stack**: [Stack details]
**Repository**: [path or URL if available]

**Completed**:
- ✅ [Done item 1]
- ✅ [Done item 2]

**Next Tasks** (in priority order):
1. [ ] [Immediate next task — be specific]
2. [ ] [Second task]
3. [ ] [Third task]

**Critical Files to Read First**:
- [file path] — [why it's critical]
- [file path] — [why it's critical]

**Known Constraints**:
- [Constraint 1, e.g., "Use pnpm, not npm"]
- [Constraint 2, e.g., "Admin panel must be on admin.domain.com"]

**Do NOT**:
- [Something the previous session explicitly avoided]
- [Another anti-pattern to avoid]

Start by reading the critical files listed above, then confirm you understand the current state before proceeding.