What the Workflow Produces
As Stadium 8 runs, it generates a set of files alongside your application code. These give you visibility into what was built, why decisions were made, and where things stand at any point.
The Project Brief
Section titled “The Project Brief”After Intake, Claude writes a project brief to generated-docs/specs/project-brief.md. This is the document you approved before planning started. It’s the agreed scope for the build and the reference point if anything is unclear later.
The Stories Folder
Section titled “The Stories Folder”As planning progresses, Claude writes structured story files to generated-docs/stories/. These reflect exactly what was approved: the epic list and the individual stories under each epic. You can open these at any time to see the full scope of what is being built.
The Decision Journal
Section titled “The Decision Journal”Every choice Claude makes autonomously — layout decisions, data flow approaches, interpretations of ambiguous requirements — is logged to generated-docs/context/journal.md. Entries are grouped by epic and written as decisions are made, not retrospectively.
If something was built in a way that doesn’t match what you wanted, check the journal first. It will tell you what Claude decided and why. If you disagree, raise it during your browser verification for that epic and Claude will revisit it before the epic merges.
The Dashboard
Section titled “The Dashboard”Claude generates a live dashboard at generated-docs/dashboard.html. Type /dashboard in Claude Code to open it. It shows the current stage, which stories are complete, which are in progress, and gate status.