gsd-pause-work

To preserve context when pausing a development workflow, the Skill gathers current phase state, completed progress, remaining tasks, and blockers, then writes a structured `.continue-here.md` file. This ensures full session continuity for resuming work later.

The best way to create a work handoff is by capturing structured context including decisions and blockers. The Skill generates a handoff file and supports WIP git commits, allowing interrupted development workflows to restart safely without losing progress.

Yes, you can use WIP git commits to save progress during a pause. The Skill applies work-in-progress commit support alongside structured context capture, ensuring your decisions and completed tasks remain intact across session boundaries.

No specific dependencies or frameworks are required for context preservation. The Skill operates independently to detect your current phase and collect progress data, generating a markdown handoff file that works across any development environment.

You need to generate a resume file for session continuity whenever work must stop mid-phase during planning, implementation, or reporting. This structured handoff captures your exact working state so the next session can continue immediately.

A limitation of relying on a markdown handoff file is that it captures state only at the moment of pausing. It does not automatically track changes made after generation, so any subsequent manual edits to the codebase will not be reflected in the resume instructions.