Your Sign-Off Points
There are four moments where Stadium 8 stops and waits for you. Everything else is autonomous.
1. The Project Brief
Section titled “1. The Project Brief”After Intake, Claude produces a project brief: a structured summary of what it understood from your materials and your answers to its questions. You review the brief and either approve it, ask for changes, or edit the file directly.
Nothing gets planned until you approve. This is your chance to correct misunderstandings before the scope is set.
2. The Epic List
Section titled “2. The Epic List”Claude proposes the full list of epics: the major feature areas it plans to build, in priority order. You review the list and either approve it or ask for revisions.
This is where you confirm the scope is right: the right features, roughly the right size, nothing missing, nothing that shouldn’t be there.
3. Stories Per Epic
Section titled “3. Stories Per Epic”For each epic, before implementation begins, Claude proposes the stories: the individual user-facing things the epic will deliver. You review the list and either approve it or ask for revisions.
This is your main opportunity to shape the details of a feature. You can add edge cases Claude hasn’t covered, split a story that’s grown too large, remove scope that belongs in a later epic, or rewrite a story that doesn’t capture what you actually want. Once you approve, implementation starts.
4. Browser Verification
Section titled “4. Browser Verification”After each epic’s stories are built and automated checks pass, Claude gives you a checklist of things to try in your browser. You open the running application, work through the checklist, and confirm the feature does what you asked.
This is a real test. You are using the application the way a user would, not reviewing code. Once you confirm, the epic is merged to main.
Everything between these points is autonomous. Between your story approval and the browser checklist, Claude works without interruption: writing tests, writing code, fixing quality gate failures, managing git. You are available in the foreground for planning the next epic, but you are not required to make decisions.