The Workflow at a Glance

Stadium 8 works in three stages: Intake, Plan and Build. Intake runs once, when you set up the project. Plan and Build run once for every epic: you plan an epic, Claude builds it, you sign it off, and the next one begins.

Stage 1: Intake

Intake turns your materials into a project setup and a plan of epics. It runs the first time you type /start.

What happens	Who
Reads everything in `documentation/`, including any design files	Claude
Asks three short questions: user roles, sign-in method, and whether your backend is running	Claude
Runs a connection test against your backend, if it’s already running	Claude
Writes the project setup to `generated-docs/project.md`	Claude
Breaks your requirements into epics, maps how they depend on each other, and checks that every requirement belongs to an epic	Claude
Raises anything that blocks the plan, one question at a time	Claude asks, you answer
Approve the project setup and the epic plan	You approve

The project setup holds the facts that stay the same across every epic: roles, sign-in, data source, compliance and styling. You settle them once and every epic inherits them.

Stage 2: Plan

Plan breaks one epic into stories. It runs as each epic comes up for building, or earlier if you plan ahead with /plan.

What happens	Who
Proposes the epic’s stories and how each one will be checked	Claude
Approve the stories	You approve

Stage 3: Build

Build turns the approved stories into working, tested code on the epic’s own branch.

What happens	Who
Writes failing tests for every story in the epic	Claude
For each story: writes the code that makes its tests pass, runs a quick check, and commits	Claude
Runs the full quality gates, a code review of the whole epic, and the end-to-end browser tests	Claude
Work through the manual test checklist in your browser	You confirm
Opens a pull request and waits for the GitHub checks to pass	Claude
Merge the epic into `main`	You confirm

If a check fails during Build, Claude fixes the problem and tries again, up to three times. After that it stops and asks you.

When the epic has merged, type /start to build the next one.

The flow for each epic

You describe what you want
        ↓
Intake: project setup and epic plan            ← you approve (once per project)
        ↓
For each epic:
        ↓
  Plan: the epic's stories                     ← you approve
        ↓
  Build: tests, then code, story by story      (automatic)
        ↓
  Quality gates, code review, browser tests    (automatic)
        ↓
  Manual test in your browser                  ← you confirm
        ↓
  Pull request, GitHub checks, merge           ← you confirm the merge
        ↓
The next epic begins

Nothing gets built until you approve the plan. Nothing reaches main until you’ve tested the epic and confirmed the merge.