gpd-pause-work

Create a .continue-here.md handoff capturing GPD session state.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-pause-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-pause-work
Source: https://github.com/CharlieGreenman/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-pause-work
Command: npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-pause-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pausing ongoing research mid-phase often leads to loss of context and misalignment on next steps. This Skill provides a structured handoff that captures current phase, derivation state, parameter values, intermediate results, decisions, blockers, and planned next steps to enable seamless resumption.

Core Features & Use Cases

  • Create a .continue-here.md handoff in the current phase directory containing all relevant state fields and context.
  • Append the persistent derivation state to .gpd/DERIVATION-STATE.md to prevent lossy context after resets.
  • Update .gpd/STATE.md with a Paused status and a resume target to guide the next session.
  • Commit WIP artifacts to preserve a trace of the pause for audit and rollback if needed.

Quick Start

Run the pause-work workflow to generate the .continue-here.md handoff, append the derivation state, update STATE.md, and commit WIP artifacts for seamless resumption.

Frequently Asked Questions about gpd-pause-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve research state when pausing a derivation workflow?

To preserve research state during a pause, generate a .continue-here.md handoff file capturing the current phase, parameter values, and planned next steps. This ensures seamless resumption by appending the derivation state to DERIVATION-STATE.md and updating STATE.md with a Paused status.

What is the best way to handle research handoff without losing intermediate results?

The best way to handle a research handoff is to commit WIP artifacts alongside a structured .continue-here.md file. This approach captures intermediate results, open questions, and blockers to prevent lossy context after resets.

How does phase detection work when managing a paused research session?

Phase detection identifies the exact derivation step and parameter capture state at the time of the pause. It records this context in STATE.md with a resume target, guiding the next session to the correct phase.

Can I resume work seamlessly after a system reset using derivation state files?

Yes, you can resume work seamlessly because persistent derivation state is appended to DERIVATION-STATE.md. This file prevents lossy context after resets by preserving the full state of the session for the next workflow run.

Why does updating STATE.md with a Paused status prevent misalignment on next steps?

Updating STATE.md with a Paused status prevents misalignment by explicitly defining a resume target and logging blockers. This structured handoff guarantees the next session aligns with the planned next actions.

When should I not use a structured pause-work workflow for research state management?

You should not use a structured pause-work workflow if your research phase lacks intermediate results, derivation steps, or parameter values to capture. It is designed for complex sessions requiring detailed handoff and audit traces.