gsd-pause-work

To create a context handoff for pausing active work, you checkpoint the current phase, gather completed and remaining work state, and generate a resume-ready continue-here file. This ensures you return later with full session continuity and no lost progress.

A WIP commit supports session resume by checkpointing your current working state into version control before you stop. This pairs with a handoff file to preserve both code changes and contextual decisions for a smooth resume later.

You capture workflow state by detecting the current phase, clarifying remaining work with the user, and gathering completed tasks, decisions, and blockers into a structured handoff file for checkpointing and end-of-session reporting.

Yes, gsd-pause-work applies to development sessions at any phase that need checkpointing. It handles phase detection and user clarification to ensure the handoff file captures the exact state required for resume-ready continuity.

The best way to stop without losing track is to generate a context handoff file that records decisions, blockers, and remaining work, optionally paired with a WIP commit to secure code changes for the next session.

You should avoid using a session checkpoint when your development phase is fully complete with no remaining work or decisions to preserve. Checkpointing is designed for mid-phase interruptions where resume-ready state capture is required.