Before You Begin
Two things will define your experience with Stadium 8. Neither is technical.
Scope Creep
Section titled “Scope Creep”LLMs over-build. Ask Claude to paint the kitchen and it may want to replace the tiles, the cabinets, and the lights too. All reasonable. None of it what you asked for.
Counter this in two places:
In your requirements: say what you want, and say what you do not need yet. “Users can log in with email and password — no social login, no password reset for now” gives Claude a boundary to work within.
In your story review: this is the most important guardrail. Before any code is written, Claude proposes the stories for each epic. Read each one and ask: do I actually need this right now? Approving a story is a commitment — everything approved gets built, tested, and committed. Remove unnecessary stories before implementation starts.
The goal is to build exactly what is needed, not everything that could be built.
Epics and Stories
Section titled “Epics and Stories”All work is organised into epics and stories. An epic is a major feature area — user authentication, order management, admin panel. A story is one specific thing a user can do or notice within that epic.
A story is not a technical task and not an entire feature. It is one user-visible action: “A user can log in with their email and password.”
When you review Claude’s story proposals, your job is to confirm the scope is right — nothing missing, nothing unnecessary.
Ready? Start with What You Need.