Create context handoff when pausing work mid-phase
Scanned 9/2/2026
Install to Claude Code
npx -y skills add open-gsd/gsd-core --skill gsd-pause-work --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gsd Pause Work?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/open-gsd-gsd-pause-work)More formats (shields.io, HTML) on the badges page.
---
name: gsd-pause-work
description: "Create context handoff when pausing work mid-phase"
argument-hint: "[--report]"
allowed-tools:
- Read
- Write
- Bash
---
<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 as WIP
- Resume instructions
</objective>
<execution_context>
@~/.claude/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 $ARGUMENTS:
Read and execute `~/.claude/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>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...