---
name: open-gsd-gsd-pause-work
description: "Create context handoff when pausing work mid-phase"
license: "MIT"
metadata:
  decimalai-skill-id: "590d1b13-0491-4841-b5ab-421092540b96"
  decimalai-version-id: "668b0653-1be0-46a8-8693-9d601217cbbe"
  decimalai-version: "4"
  decimalai-body-sha256: "6550a3147cdba83d55c362bd41a764bf89588f8230d2ad74c69b6270e11dc13e"
  decimalai-name: "open-gsd/gsd-pause-work"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/open-gsd-gsd-pause-work@4/SKILL.md"
---
Invoke this Pi skill with `/skill:gsd-pause-work`.

**Pi dispatch (fail closed).** Pi has no built-in subagent API; GSD provides the `gsd_dispatch` tool. Where a workflow step dispatches a named `gsd-*` role, call `gsd_dispatch` with `role` (the installed role name) and `task` (the full task text). A workflow that still writes the step as an `Agent(...)` call means the same: its `subagent_type` is the `role` and its `prompt` is the `task`. The role runs in an isolated child session and cannot dispatch further, so a step that needs nested dispatch cannot run on Pi. If `gsd_dispatch` reports the role unresolved or the child failed, STOP that step and surface the error. If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.

**Pi includes.** Pi does not expand `@path` references in a skill. Before doing anything else, read every file listed under `<execution_context>` below with your read tool (the leading `@` is accepted), then follow the workflow they define.



<arguments>(the text typed after the skill name)</arguments>

The text inside `<arguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.

<objective>
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 handoff
- Resume instructions
</objective>

<execution_context>
@__GSD_PI_ENGINE_ROOT__/gsd-core/workflows/pause-work.md
</execution_context>

<context>
State and phase progress are gathered in-workflow with targeted reads.
</context>

<process>
If `--report` is in the `<arguments>` block:
Read and execute `__GSD_PI_ENGINE_ROOT__/gsd-core/workflows/session-report.md` end-to-end.

**Follow the pause-work workflow**.

The workflow handles all logic including:
1. Phase directory detection
2. State gathering with user clarifications
3. Handoff file writing with timestamp
4. Git commit
5. Confirmation with resume instructions
</process>