Build Reports
Stadium 8 gives you two reports on a build: one for you and your team, and one for your client. Both open in your browser and draw on records the workflow already keeps, so there’s nothing to switch on.
| Command | Who it’s for | Saved to |
|---|---|---|
/build-report-maintainer | You and your team | generated-docs/reports/build-report.html |
/build-report-stakeholders | Your client or sponsor | generated-docs/reports/build-report-stakeholders.html |
You can run either report at any time, during a build or after it. Neither changes the state of the workflow. If you run one before the project has started, Claude points you to /start.
The maintainer report
Section titled “The maintainer report”The maintainer report is the internal retrospective. It covers:
- Effort and cost: how long the build took and what it cost
- Workflow performance: how efficiently the build ran, and where time was lost
- Your decisions: how many decisions you were asked for, how long you typically took to answer, and how many phases ran with no input from you. It also lists every question with the option you chose.
- Effort benchmarks: what each kind of screen took to build, such as a list, form, detail view, sign-in or export, with the same figures per feature
- A sizing calculator: type in a mix of screens to estimate upcoming work against your own delivered history
- Spend detail: a collapsed section with the cost broken down by model and by tool
The report counts your inputs and the time the workflow spent waiting for you. It doesn’t record your own working time, so it can’t split effort between you and Claude.
A feature that’s still being built only has figures for the stories it has finished. The report marks it as partly measured and leaves it out of the typical-feature figures, so the calculator isn’t skewed.
The stakeholder report
Section titled “The stakeholder report”The stakeholder report is the client-facing delivery report. It covers:
- What shipped: the delivered features, described in product language
- Decisions you signed off: the choices you made during the build, such as who uses the app, how people sign in, and what was deferred and why. Each comes with its date.
- Quality evidence: the automated tests and the hands-on checks
- What’s next: the work still to come
It leaves out cost figures and the internal workings of the build.
Changing a report’s wording
Section titled “Changing a report’s wording”Each report has a What this means panel that Claude writes from a short brief. The brief lives in the report’s skill file, at .claude/skills/build-report-maintainer/SKILL.md or .claude/skills/build-report-stakeholders/SKILL.md. Edit it to change the panel’s focus, length or tone.
/upgrade replaces these files when you update the template. Keep a copy of any change you want to reapply afterwards.