What the Workflow Produces
Stadium 8 writes a set of files into generated-docs/ as it works. They record what you approved, what Claude decided, and where each epic stands. You can open any of them at any time.
Project files
Section titled “Project files”These files describe the whole project and live on main.
| File | What it holds |
|---|---|
generated-docs/project.md | The project setup: roles, sign-in, data source and backend connection, compliance and styling. Every epic reads it. |
generated-docs/epic-plan.md | The approved plan: every epic, what it depends on, and which requirements it covers |
generated-docs/architecture.md | Shared components, conventions and known gaps that later epics build on |
generated-docs/design/digest.md | What Claude read from your design files, plus the design decisions you’ve made since. Present only if you supplied a design. |
generated-docs/specs/api-spec.yaml | The API spec Claude works from, when it created or extended one |
Files for each epic
Section titled “Files for each epic”Each epic has its own folder at generated-docs/epics/<slug>/.
| File | What it holds |
|---|---|
brief.md | The epic’s requirements |
stories/story-<N>-<title>.md | One file per story: its summary, acceptance criteria and manual test checklist |
journal.md | A plain-language record of the decisions Claude made while building the epic |
state.json | Where the epic is in the workflow. /continue reads it to resume. |
While an epic is being built, its folder is on the epic’s branch. After the merge, the folder stays on main as a permanent record of the epic.
The journal
Section titled “The journal”Each epic’s journal.md explains the choices Claude made that you’d want to know about. Examples include a component it decided to share, or a field it found the brief needed.
If something was built in a way you didn’t expect, check the journal first. If you disagree with a decision, raise it at the manual test and Claude changes it before the epic merges.
Review pages
Section titled “Review pages”Claude generates web pages for your approvals and opens them in your browser:
| Page | Used for |
|---|---|
generated-docs/epic-plan-review.html | Approving the epic plan |
generated-docs/epics/<slug>/stories-review.html | Approving an epic’s stories |
generated-docs/epics/<slug>/manual-tests.html | Working through an epic’s manual tests |
Claude regenerates these pages when needed, so they aren’t committed to git.
The dashboard
Section titled “The dashboard”Type /dashboard to open generated-docs/dashboard.html. It shows progress across every epic: those in progress on their own branches, and those already merged. It shows the whole project, whichever branch you have checked out.
Build reports
Section titled “Build reports”Two reports summarise how the build went, one for your team and one for your client. Both are saved to generated-docs/reports/. See Build Reports.