Your Sign-Off Points
Stadium 8 stops and waits for you at four points. Between them, Claude works without interrupting you, unless it reaches a decision it must ask you about.
1. The project setup and epic plan
Section titled “1. The project setup and epic plan”After Intake, Claude shows you the project setup and the plan of epics together. The setup covers roles, sign-in, data source, compliance and styling. The plan lists every epic, what each one depends on, and which of your requirements it covers.
Claude opens the plan as a review page in your browser. You can rename, reorder, add or remove epics on the page, then click Approve. If you supplied design files, Claude also reads back what it understood from them, including anything it couldn’t work out.
Anything that blocks the plan, such as a requirement that doesn’t fit any epic, is raised and settled first. You can’t approve a plan that still has an open blocker.
2. The stories for each epic
Section titled “2. The stories for each epic”When an epic comes up, Claude proposes its stories and how each one will be checked. The same kind of review page opens in your browser, where you can edit, split, reorder or remove stories.
This is your main chance to shape a feature: add edge cases, split a story that’s too large, or cut scope that belongs in a later epic. Once you approve, the build starts.
3. The manual test
Section titled “3. The manual test”When the epic is built and its automated checks pass, Claude opens a check-off page in your browser. You use the running app the way a user would and tick off each test.
If something is wrong, describe it. Claude fixes it, re-runs the checks, and asks you to re-test only what the fix touched. See Manual Test Checklists.
4. The merge into main
Section titled “4. The merge into main”Claude opens a pull request and waits for the GitHub checks to pass. It then asks whether to merge the epic into main. You can merge now or hold off and merge later. Claude never merges without your confirmation.
How approvals work in the browser
Section titled “How approvals work in the browser”The review pages can’t write to your project directly. When you click Approve or Done, the page copies your response, including any edits, to the clipboard. Paste it into the chat to finish the approval. If you made no edits, you can type approved in the chat instead.
Open these pages in your normal web browser. The browser built into VS Code blocks copying to the clipboard, so the buttons don’t work there.
Optional: commits and pushes
Section titled “Optional: commits and pushes”The first time you run /start, Claude asks how to handle git commits and pushes. If you choose anything other than auto-approving both, Claude also asks before each commit or push you didn’t auto-approve. See How Claude Handles Git.