save-session

Save Session

Capture full session state so the next session can resume with zero context loss.

Trigger

User invokes /save-session or says "save session", "save state", "save progress"

Steps

1. Gather context

• Review all files modified during this session (git diff or conversation recall)
• Review what was discussed, attempted, and decided
• Note errors encountered and how they were resolved (or not)
• Check current build/test status if relevant

2. Create session file

mkdir -p {{SESSION_DIR}}

Write to {{SESSION_DIR}}/YYYY-MM-DD-<short-id>-session.md using today's date.

3. Populate every section below

Write every section honestly. "Nothing yet" or "N/A" for empty sections. An incomplete file is worse than an honest empty section.

# Session: YYYY-MM-DD

**Started:** [time if known]
**Last Updated:** [current time]
**Project:** [project name or path]
**Topic:** [one-line summary]

---

## What We Are Building

[1-3 paragraphs. Enough context for someone with zero memory to understand the goal.]

---

## What WORKED (with evidence)

[Only confirmed working things. Each item includes WHY you know it works.]

- **[thing]** — confirmed by: [specific evidence]

---

## What Did NOT Work (and why)

[MOST IMPORTANT SECTION. Every failed approach with the EXACT reason.]

- **[approach]** — failed because: [exact reason / error message]

---

## What Has NOT Been Tried Yet

[Promising approaches not yet attempted. Specific enough to act on.]

- [approach / idea]

---

## Current State of Files

| File | Status | Notes |
|------|--------|-------|
| `path/to/file` | Complete / In Progress / Broken / Not Started | [details] |

---

## Decisions Made

[Architecture choices, tradeoffs accepted, approaches chosen and why.]

- **[decision]** — reason: [why]

---

## Blockers & Open Questions

- [blocker / open question]

---

## Exact Next Step

[The single most important thing to do when resuming. Precise enough to start immediately.]