Managing Changes

Changes are a normal part of development. Stadium 8 has a structured approach for handling them depending on when they occur and what kind of change it is.

Changes During an Active Story

If Stadium 8 is currently developing a story and you spot something that needs to change, describe the adjustment in the foreground chat. Claude is available there during building.

This is the lowest-friction point to make a change. The story is still in progress. The adjustment gets folded in cleanly before tests are written and committed.

Changes After a Feature Is Complete

When Stadium 8 has finished a full workflow for a feature and a review introduces new requirements, don't make ad hoc changes directly. Instead:

1. Collect all the changes: gather every piece of feedback and every requested change from the review before touching anything.

2. Spec them out: write the changes down clearly. Work through them conversationally with Claude if that helps refine the wording, but get them into written form.

3. Bundle related changes together: group changes that belong to the same area or flow into a coherent set of specs rather than addressing them one by one.

4. Describe to Claude in chat and use /continue: share the bundled specs and ask Claude to add epics or stories for the changes, then type /continue to resume the planning and build workflow. This keeps the full Stadium 8 workflow active: structured planning, automated commits, and quality gate checks all apply.

Routing post-review changes through Claude as new stories ensures that Stadium 8's guardrails stay in place. Skipping this and making direct edits bypasses the automated checks that Stadium 8 is designed to enforce.

Cosmetic Changes: The Exception

For purely cosmetic changes (adjustments that affect appearance only, with no change to behaviour, logic, or data), it is acceptable to prompt Claude directly without going through the full workflow.

Cosmetic (direct prompt is fine):

• Move a button from the bottom-left to the bottom-right

• Change the primary action button colour from blue to green

• Update a field label from "Submit" to "Save & Continue"

Functional (describe to Claude and add stories):

• Changing what happens when a button is clicked

• Adding or removing a field from a form

• Altering validation rules or business logic

• Changing what data is displayed or how it is filtered

If you're not sure, use the Stadium 8 workflow. Staying within the structured process keeps all quality gates and automated checks active.