Overview
Thepause-work command creates a comprehensive handoff file when you need to pause work mid-phase. It captures your complete work state, making it easy to resume later without losing context.
Syntax
How It Works
When you runpause-work, GSD:
- Detects your current phase from recent files in
.planning/ - Gathers complete state including:
- Current position in the phase
- Work completed so far
- Work remaining
- Decisions made
- Any blockers or open questions
- Creates
.continue-here.mdwith all context sections and timestamp - Commits to git as a WIP (work-in-progress) commit
- Provides resume instructions for your next session
What Gets Captured
The handoff file includes:- Phase identification - Which phase you’re working on
- Completion status - What percentage complete, what’s done
- Current position - Exactly where you left off
- Recent changes - Files modified in this session
- Decisions made - Any architectural or implementation choices
- Next steps - Clear list of what to do next
- Blockers - Any issues preventing progress
- Context notes - Important details to remember
Usage Examples
Basic pause
Resume later
When you’re ready to continue:.continue-here.md file and restores full context.
When to Use
Perfect for
- Switching tasks mid-phase
- End of day during active work
- Before taking a break during complex changes
- When you need to context-switch urgently
- Handing off work to another team member
Not needed for
- After completing a phase (state is already saved)
- At natural stopping points (after commits)
- When no work is in progress
Integration with Resume
Thepause-work and resume-work commands work together:
- Pause → Creates
.continue-here.mdwith full state - Resume → Detects checkpoint file and loads all context
- Seamless continuation → Pick up exactly where you left off
Files Created
Related Commands
resume-work- Resume from a pause checkpointprogress- Check project progress and next actions