pause-session

Write a .development/next.md snapshot with session context and next steps.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/doolin/dave-skills --skill pause-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pause-session
Source: https://github.com/doolin/dave-skills/tree/main/skills/pause-session
Command: npx skills add https://github.com/doolin/dave-skills --skill pause-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture session context and next steps before stepping away, ensuring continuity and reducing re-discovery overhead.

Core Features & Use Cases

  • Writes a .development/next.md snapshot containing:
    • What was done this session
    • Current state (branch, uncommitted changes, open PRs/MRs)
    • What's next (the next concrete action)
    • Blockers (external inputs, CI results)
    • Starter prompt (ready-to-paste Claude prompt)
  • Stages and commits the update with a one-line summary so the history stays concise.
  • Generates a ready-to-paste starter prompt to jump back into the project quickly.

Quick Start

Run the pause-session skill to snapshot the current project state, generate .development/next.md with a ready-to-paste starter prompt, and commit it with a one-line summary.

Frequently Asked Questions about pause-session

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save my git session context before stepping away from a project?

To save your git session context before stepping away, pause-session writes a .development/next.md file capturing what was done, current state, and next steps. It also stages and commits the snapshot with a one-line summary.

What is the best way to capture uncommitted changes and blockers when ending a development session?

The best way to capture uncommitted changes and blockers when ending a development session is generating a next.md snapshot. This file records your current branch state, open PRs, external blockers, and a ready-to-paste starter prompt for resuming.

How do I create a starter prompt to resume a Claude session later?

You can create a ready-to-paste starter prompt to resume a Claude session by running pause-session, which automatically generates the prompt inside the .development/next.md file alongside your project's current state and next actions.

Does the pause-session workflow commit the context file directly to my git history?

Yes, the pause-session workflow stages and commits the context file directly to your git history. It uses a one-line commit summary to keep the version history concise while preserving the session snapshot.

What should be included in a development session snapshot to reduce re-discovery overhead?

A development session snapshot should include what was done, current branch and uncommitted changes, open PRs or MRs, the next concrete action, external blockers, and a starter prompt. This reduces re-discovery overhead when you return.

Can I use pause-session for non-git projects to preserve context?

pause-session is designed for git workflows and commits the generated next.md file with a one-line summary. While the context capture mechanism may apply broadly, the staging and commit steps require a git repository to function properly.