vertical-slice

A vertical slice validates a game loop by building a 3–5 minute, near-production-quality gameplay cycle to test if the start-to-challenge-to-resolution loop is fun and achievable within realistic schedule constraints before full production commitment.

A vertical slice in game development is a polished, production-quality 3–5 minute segment demonstrating one complete gameplay cycle. You need one during pre-production after GDDs, architecture, and UX specs are complete to validate feasibility.

Manage scope by enforcing strict 3–5 minute slice discipline and track velocity by capturing day-by-day progress to inform sprint planning. This process yields a PROCEED, PIVOT, or KILL verdict gated by structured playtest debriefs.

Yes, you can re-run vertical slice validation after game design document or architecture pivots. The process supports repeated re-runs during pre-production to re-evaluate whether the updated end-to-end game loop remains achievable and fun.

The creative director verdict workflow for playtest debriefs is a final review process gated by CD-PLAYTEST in full mode. It uses generated session reports and checkpoint data to deliver a definitive PROCEED, PIVOT, or KILL production decision.

A limitation of vertical slice production validation is its strict scope discipline of a 3–5 minute gameplay cycle, meaning it does not evaluate full game length, narrative breadth, or content variety, only the core loop's fun and schedule feasibility.