gsd-pause-work

Pause current work and create a handoff file with git state.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-pause-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-pause-work
Source: https://github.com/optivent/gsd-kimi-cli/tree/main/skills/gsd-pause-work
Command: npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-pause-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pause current work and create a handoff file to resume later.

Core Features & Use Cases

  • Handoff artifact creation: Generates a structured handoff file at .planning/handoffs/YYYY-MM-DD-{slug}.continue-here that captures phase, plan, in-progress files, recent commits, blockers, and decisions.
  • State capture & commit: Collects current git status and staged changes to preserve the exact working state.
  • Resumption readiness: Provides a clear path to resume by referencing the saved context and next steps.
  • Use Case: End of a session, urgent context switch, or long-running operation that requires later continuation.

Quick Start

Run the slash command to pause and generate a handoff file for later resumption.

Frequently Asked Questions about gsd-pause-work

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

FAQPage Schema
How do I pause work and create a handoff file to resume later?

To pause work and create a handoff file, run the slash command to generate a structured context file capturing the current phase, plan, in-progress files, and blockers. It saves the handoff at .planning/handoffs/YYYY-MM-DD-{slug}.continue-here and commits staged changes.

What is context-switching workflow management for long-running tasks?

Context-switching workflow management for long-running tasks involves capturing the current working state, recent commits, and decisions into a structured handoff file. This ensures resumption readiness by providing a clear path with saved context and next steps when ending a session or handling urgent switches.

Does the handoff file capture git status and staged changes?

Yes, the handoff file captures git status and staged changes. It collects the exact working state during state capture and commit, preserving recent commits and in-progress files to ensure the precise context is available for later resumption.

When do I need to generate a session handoff file?

You need to generate a session handoff file when ending a work session, handling an urgent context switch, or managing long-running operations requiring later continuation. It preserves the exact working state, blockers, and plan for future resumption.

How do I resume work after a context switch using a handoff file?

To resume work after a context switch, reference the saved handoff file at .planning/handoffs/YYYY-MM-DD-{slug}.continue-here. It provides resumption readiness by detailing the captured phase, plan, in-progress files, and next steps required to continue.

Can I use this workflow planning tool without git dependencies?

This workflow planning tool collects current git status and commits staged changes to preserve the working state. While it creates a structured handoff file independently, its state capture and commit functionality relies on git to accurately record recent commits and in-progress files.