---
name: durable-continuation-output
description: Use for long-running work where another execution turn may need to resume the same assignment. Perform the assigned task normally, then end each response with a small structured continuation-state block that records whether the assignment is finished and, if not, exactly where work should resume.
---

# Durable Continuation Output

Perform the assignment you were given normally.

Do not change how you execute the task because of this skill. Follow the assignment, repository instructions, tools, acceptance criteria, and normal verification requirements.

This skill only defines the structured state you must output at the end of each response.

## Required end-of-response state

End every response with exactly one block in this form:

```text
<continuation-state>
status: working | complete | blocked
summary: <brief description of what this response accomplished>
current: <precise current state of the assignment>
next: <exact next unfinished action, or none>
</continuation-state>
```

## Status meanings

- `working`: the overall assignment is unfinished and another execution can continue it.
- `complete`: the entire assignment and its required acceptance gates are complete.
- `blocked`: progress cannot continue without external input or an unavailable dependency.

Do not use `complete` merely because one response, phase, commit, test, or subtask finished.

## Field rules

`summary` records only what materially changed in this response.

`current` records the exact assignment state at the end of the response so a later execution can understand where work stands without reconstructing the transcript.

For `working`, `next` identifies the exact next unfinished action. Do not write a vague value such as `continue working`.

For `complete`, use `next: none`.

For `blocked`, `next` identifies the first action to take once the blocker is resolved.

Keep the block concise and factual. Do not include hidden reasoning or chain-of-thought.

Do not include browser behavior, Retry behavior, continuation-message instructions, scheduling, auto-resume policy, MCP lifecycle operations, repository recovery methodology, or orchestration mechanics. Those are outside this skill.