| name | gsd-pause-work |
| description | Create context handoff when pausing work mid-phase |
<cursor_skill_adapter>
A. Skill Invocation
- This skill is invoked when the user mentions
gsd-pause-work or describes a task matching this skill.
- Treat all user text after the skill mention as
{{GSD_ARGS}}.
- If no arguments are present, treat
{{GSD_ARGS}} as empty.
B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers
C. Tool Usage
Use these Cursor tools when executing GSD workflows:
Shell for running commands (terminal operations)
StrReplace for editing existing files
Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed
D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use
Task(subagent_type="generalPurpose", ...)
- The
model parameter maps to Cursor's model options (e.g., "fast")
</cursor_skill_adapter>
Create `.continue-here.md` handoff file to preserve complete work state across sessions.
Routes to the pause-work workflow which handles:
- Current phase detection from recent files
- Complete state gathering (position, completed work, remaining work, decisions, blockers)
- Handoff file creation with all context sections
- Git commit as WIP
- Resume instructions
<execution_context>
@/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/workflows/pause-work.md
</execution_context>
State and phase progress are gathered in-workflow with targeted reads.
If `--report` is in {{GSD_ARGS}}:
Read and execute `/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/workflows/session-report.md` end-to-end.
Follow the pause-work workflow.
The workflow handles all logic including:
- Phase directory detection
- State gathering with user clarifications
- Handoff file writing with timestamp
- Git commit
- Confirmation with resume instructions