pause

Automate pausing a GSE-One session by committing worktrees and saving checkpoints.

4|1|Updated Apr 11, 2026

Search Tags:#backlog #checkpoint #status #session #pause #git-worktree

Ready to run

npx skills add https://github.com/nicolasguelfi/gensem --skill pause-nicolasguelfi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pause
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/pause
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill pause-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pauses of GSE-One sessions can lead to lost progress or mismatched state. This Skill automates pausing by auto-committing active worktrees and saving a detailed session checkpoint to preserve context and enable seamless resumption.

Core Features & Use Cases

Auto-commit all active worktrees for current backlog tasks to preserve progress.
Save a structured checkpoint under .gse/checkpoints with status, backlog, and git state snapshots.
Update status.yaml to reflect session paused and expose a stable resume point.
Optional coach evaluation post-pause to surface sustainability and engagement insights.
Generate a concise pause report summarizing actions and outcomes for post-session reviews.

Quick Start

Pause the current GSE-One session to auto-commit worktrees and capture a checkpoint.

Frequently Asked Questions about pause

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

FAQPage Schema

How do I save a git worktree checkpoint before pausing a sprint session?▼

To save a git worktree checkpoint, this Skill auto-commits active worktrees and captures status.yaml, backlog.yaml, and git state into .gse/checkpoints to preserve session context. It ensures progress is not lost during sprint interruptions.

What is the best way to auto-commit active worktrees when interrupting a development task?▼

The best way to auto-commit active worktrees is using an automated pause workflow that commits current backlog tasks and writes a structured checkpoint. This synchronizes backlog state and git data to expose a stable resume point.

Does pausing a session automatically update status.yaml to reflect the interrupted backlog state?▼

Yes, pausing a session automatically updates status.yaml to reflect the paused state. It coordinates backlog data, worktree status, and git snapshots to generate a reliable resume point and a concise pause report.

How do I resume a paused development session from a saved checkpoint?▼

Resuming a paused session relies on the structured checkpoint saved under .gse/checkpoints. This snapshot contains the synchronized status.yaml, backlog.yaml, and git worktree state required to seamlessly continue the interrupted sprint task.

Can I trigger a coach evaluation after saving a session checkpoint?▼

Yes, you can optionally trigger a coach evaluation post-pause. This evaluation surfaces sustainability and engagement insights after the session checkpoint and git worktree auto-commit processes are fully completed.

What data is required to generate a valid session pause report for backlog tasks?▼

Generating a valid session pause report requires data from status.yaml, backlog.yaml, and git worktree states. The Skill enforces and captures these inputs to produce a reliable checkpoint summarizing all pause actions and outcomes.