gsd-pause-work

Capture work state and create timestamped .continue-here.md handoff files.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-pause-work-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-pause-work
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-pause-work
Command: npx skills add https://github.com/rkz91/coco --skill gsd-pause-work-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pausing work mid-phase can cause loss of context, decisions, and progress. This Skill provides a structured handoff workflow to capture complete state, notes, and next steps to enable seamless resumption.

Core Features & Use Cases

  • Context capture: gathers phase, state, decisions, blockers, and remaining work.
  • Handoff file creation: writes a timestamped .continue-here.md with all context sections.
  • Git integration: commits WIP changes to track progress and enable resumption.
  • Use Case: When a long-running, multi-phase task needs to be paused and later resumed without losing context or history.

Quick Start

Prompt the system to run the pause-work workflow and generate a timestamped .continue-here.md handoff with complete state and resume instructions.

Frequently Asked Questions about gsd-pause-work

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

FAQPage Schema
How do I preserve git workflow context when pausing work mid-phase?

To preserve git workflow context when pausing work mid-phase, this Skill captures your current state, decisions, and blockers, then writes a timestamped .continue-here.md handoff file and commits WIP changes for seamless resumption.

What is a timestamped handoff file for session context transfer?

A timestamped handoff file for session context transfer is a generated .continue-here.md document that records your phase, state, decisions, blockers, and remaining work to prevent context loss during multi-step workflow pauses.

How do I create a state preservation checkpoint for a multi-phase development task?

You create a state preservation checkpoint for a multi-phase development task by prompting the pause-work workflow, which automatically gathers your progress context and generates a timestamped handoff file complete with resume instructions.

Does the pause-work handoff process require any specific git dependencies?

The pause-work handoff process requires no external dependencies, but it does need access to recent work state, version control, and a defined pause-work workflow to commit WIP changes and write the handoff file.

What's the best way to resume a long-running workflow after a context break?

The best way to resume a long-running workflow after a context break is using a structured handoff file that captures complete state, notes, and next steps, enabling seamless resumption without losing history or decisions.

When should I avoid using automated context handoff for pausing work?

You should avoid using automated context handoff for pausing work if your task is not a multi-step, phase-driven workflow, as the state capture mechanism requires a defined workflow and recent work state to generate accurate resumption guidance.