If a Session Is Interrupted

You can resume a Stadium 8 build at any point. If a session ends unexpectedly, such as from a closed window, a lost connection or a crash, you don’t lose your progress.

How to resume

Open the project in Claude Code again.
Make sure you’re on the epic’s branch. If you aren’t, check it out:
```
git checkout epic/<slug>
```
Type /continue.

Claude reads the epic’s progress from generated-docs/epics/<slug>/state.json and picks up at the stage it reached. It first brings the branch up to date with main, in case another epic or project change landed in the meantime.

Type /status at any time to see where the current epic stands.

If Claude can’t find the epic

What Claude says	What it means
Not on an epic branch	You’re on `main` or another branch. Check out the epic’s branch, or type `/start` to begin a new epic.
The branch has no `state.json`	The branch wasn’t created by the workflow. Type `/start` to set it up.

What’s preserved

Committed work: everything committed is in git, and nothing is lost.
The epic’s progress: state.json records the stage and each story’s status.
The journal: it’s up to date as of the last commit.
Generated tests: tests that were already written aren’t regenerated.

Work that wasn’t committed when the session ended may need redoing. Claude picks up the story that was in progress and finishes it.

If the epic was waiting to merge

If you chose to hold off on the merge, or the session ended while the pull request was open, the epic stays at the ready-to-merge stage. Type /continue on the epic’s branch to return to the merge step.

You can also merge it yourself on GitHub, or with this command. Use a merge commit, not a squash:

gh pr merge --merge