gsd-runtime-resume

To resume an interrupted agent task, this Skill reconstructs the task state from on-disk runtime files and the latest handoffs. It enforces deterministic progression by validating the presence of runtime artifacts before proceeding.

Runtime state persistence for agent orchestration involves saving task progression to on-disk runtime files. This ensures continuity when execution is paused mid-runtime or handed to a new agent without relying on hidden conversation context.

Handing off a paused task to a new agent requires explicit next steps in a resume.md file. The Skill reconstructs the execution state from repository runtime directories and accepted handoffs to ensure seamless continuity.

Yes, explicit next steps in resume.md are required to continue a runtime task. The Skill enforces deterministic progression and mandates this documentation to validate runtime artifacts before safely proceeding.

Yes, you can use repository runtime files to reconstruct task state after a constraint shift. The Skill supports resumable execution by reading on-disk handoffs, reviews, and resume notes from the runtime task directory.

If runtime artifacts are missing when you try to resume work, the validation fails and prevents proceeding. The Skill requires these on-disk files and accepted handoffs to enforce deterministic progression for the interrupted task.