Name: save-session
Author: klu-dev

Prompt file imported from klu-dev/porting-ecc-to-vscode (.github/prompts/save-session.prompt.md). Copyright stays with the author.

Capture everything that happened in this session and save it so the next session can pick up where this one left off.

Process

Step 1: Gather context

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

Step 2: Write the session file

Save to .github/session-data/YYYY-MM-DD-<short-description>.md (create directory if needed).

Step 3: Populate all sections below

Write every section honestly. Do not skip — write "N/A" if empty. An incomplete file is worse than an honest empty section.

Session File Format

# Session: YYYY-MM-DD

**Project:** [project name or path]
**Topic:** [one-line summary]

## What We Are Building
[1-3 paragraphs with enough context for zero-memory resumption]

## What WORKED (with evidence)
- **[thing]** — confirmed by: [specific evidence]

## What Did NOT Work (and why)
- **[approach]** — failed because: [exact reason / error message]

## What Has NOT Been Tried Yet
- [approach / idea]

## Current State of Files
| File | Status | Notes |
|------|--------|-------|
| `path/to/file` | Complete / In Progress / Broken / Not Started | [details] |

## Decisions Made
- **[decision]** — reason: [why]

## Blockers & Open Questions
- [blocker or question]

## Exact Next Step
[The single most important thing to do when resuming]

Step 4: Show the file to the user

After writing, display contents and ask: "Does this look accurate? Anything to correct?"

Rules

Each session gets its own file — never append to previous
"What Did NOT Work" is the most critical section — prevents retrying failed approaches
The file is meant to be read at the start of the next session via /resume-session

{ "prompt": "Capture everything that happened in this session and save it so the next session can pick up where this one left off.\r\n\r\n## Process\r\n\r\n### Step 1: Gather context\r\n\r\n- Review files modified during this session (use git diff or recall from conversation)\r\n- Review what was discussed, attempted, and decided\r\n- Note errors encountered and how they were resolved (or not)\r\n- Check current test/build status if relevant\r\n\r\n### Step 2: Write the session file\r\n\r\nSave to `.github/session-data/YYYY-MM-DD-<short-description>.md` (create directory if needed).\r\n\r\n### Step 3: Populate all sections below\r\n\r\nWrite every section honestly. Do not skip — write \"N/A\" if empty. An incomplete file is worse than an honest empty section.\r\n\r\n## Session File Format\r\n\r\n```markdown\r\n# Session: YYYY-MM-DD\r\n\r\n**Project:** [project name or path]\r\n**Topic:** [one-line summary]\r\n\r\n## What We Are Building\r\n[1-3 paragraphs with enough context for zero-memory resumption]\r\n\r\n## What WORKED (with evidence)\r\n- **[thing]** — confirmed by: [specific evidence]\r\n\r\n## What Did NOT Work (and why)\r\n- **[approach]** — failed because: [exact reason / error message]\r\n\r\n## What Has NOT Been Tried Yet\r\n- [approach / idea]\r\n\r\n## Current State of Files\r\n| File | Status | Notes |\r\n|------|--------|-------|\r\n| `path/to/file` | Complete / In Progress / Broken / Not Started | [details] |\r\n\r\n## Decisions Made\r\n- **[decision]** — reason: [why]\r\n\r\n## Blockers & Open Questions\r\n- [blocker or question]\r\n\r\n## Exact Next Step\r\n[The single most important thing to do when resuming]\r\n```\r\n\r\n### Step 4: Show the file to the user\r\n\r\nAfter writing, display contents and ask: \"Does this look accurate? Anything to correct?\"\r\n\r\n## Rules\r\n\r\n- Each session gets its own file — never append to previous\r\n- \"What Did NOT Work\" is the most critical section — prevents retrying failed approaches\r\n- The file is meant to be read at the start of the next session via `/resume-session`", "variables": [], "notes": "Save current session state so work can be resumed later with full context.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/klu-dev/porting-ecc-to-vscode", "path": ".github/prompts/save-session.prompt.md", "ref": "05710308b32281dfc5c65069eba977670868c05a", "url": "https://github.com/klu-dev/porting-ecc-to-vscode/blob/05710308b32281dfc5c65069eba977670868c05a/.github/prompts/save-session.prompt.md", "key": "klu-dev/porting-ecc-to-vscode/.github/prompts/save-session.prompt.md" } } }

save-session

About

Process

Step 1: Gather context

Step 2: Write the session file

Step 3: Populate all sections below

Session File Format

Step 4: Show the file to the user

Rules

Use it

Manifest

Reviews