scaffold-review-prototype

Auditing a game prototype for scope discipline requires reading prototype files and design documents to verify question clarity. This process prevents wasted effort on overly broad experimental designs by checking that the prototype's focus is manageable.

Prototype scope enforcement in game development scaffolds is the process of identifying and flagging issues with the Build and Skip scopes. It maintains focus on the core experimental question and prevents uncontrolled feature expansion during the design phase.

To verify Architecture Decision Records (ADR) follow-through for a game prototype, read all ADRs and check that design impacts from the prototype are properly documented. This ensures completeness and consistency across the project's architecture decisions.

You need to review a prototype file within a game development scaffold before investing significant time in a new feature experiment. This ensures the prototype adheres to project constraints and design principles before implementation begins.

Yes, you can use a design audit to check if a prototype adheres to project constraints. The audit reads index files, system indexes, and ADRs to verify completeness, ensuring the prototype design aligns with established project boundaries.

The limitations of automated prototype review include relying entirely on the content within prototype files, index files, and ADRs. It cannot assess undocumented design intentions or evaluate gameplay feel outside the scaffold's textual artifacts.