gsd-pause-work

Name: gsd-pause-work
Availability: InStock
Author: Pear

Generate a timestamped .continue-here.md handoff file with full GSD phase state.

Updated May 15, 2026

Search Tags:#workflow automation #developer productivity #phase management #context handoff #gsd #git wip #pause work

Ready to run

npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-pause-work-pear-commerce

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-pause-work
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-pause-work
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-pause-work-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When pausing GSD project work mid-phase, critical context about current progress, completed tasks, pending work, and key decisions is often lost, leading to slow, error-prone resume sessions and repeated work.

Core Features & Use Cases

Automated Handoff File Generation: Creates a standardized .continue-here.md file that captures all relevant work state for the current phase.
Complete State Preservation: Records phase position, completed work, remaining tasks, key decisions, blockers, and resume instructions.
Use Case: If you are halfway through implementing a new feature phase and need to switch to an urgent bug fix, this skill preserves all your context so you can resume the phase exactly where you left off without rework.

Quick Start

Use the gsd-pause-work skill to generate a context handoff file for your current mid-phase GSD work.

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 context when pausing mid-phase work in a GSD workflow?▼

To preserve context when pausing mid-phase work in a GSD workflow, generate a timestamped .continue-here.md handoff file capturing phase state, pending tasks, and key decisions, then commit it as a work-in-progress to version control.

What is a context handoff file and how does it help developer productivity?▼

A context handoff file is a standardized markdown document that records phase position, completed work, remaining tasks, and blockers. It helps developer productivity by preventing context loss across sessions, enabling rapid and error-free resume of in-progress work.

How do I hand off in-progress phase work to another team member?▼

Hand off in-progress phase work by generating a .continue-here.md file with full phase state and resume instructions, then committing it as a git work-in-progress. The receiving team member uses this file to continue development exactly where you paused.

Does the gsd-pause-work skill require specific dependencies to manage phase management?▼

No specific dependencies are required to manage phase management. The skill operates independently to generate the handoff file and commit work-in-progress state to your existing version control setup.

What is the best way to switch to an urgent bug fix without losing current feature progress?▼

The best way to switch to an urgent bug fix without losing progress is to pause your current phase using a context handoff. This saves your exact development state to a .continue-here.md file, preventing rework when you resume.