vertical-slice

Guide pre-production game teams through an 8-phase vertical slice workflow with verdict reporting.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill vertical-slice-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vertical-slice
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/vertical-slice
Command: npx skills add https://github.com/MichaelSolati/mkai --skill vertical-slice-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often waste months of production time building full games that fail to engage players or are technically unfeasible to build on schedule. This Skill eliminates that risk by guiding teams to build a near-production vertical slice early in pre-production to validate the full core game loop before committing to full production.

Core Features & Use Cases

  • Structured Vertical Slice Workflow: Guides teams through 8 defined phases from scope definition to final verdict, including scope creep guardrails and sunk cost checkpoints to keep builds on track.
  • Playtesting & Debrief Protocols: Includes structured playtest questions and observation techniques (silent walkthroughs, think-aloud sessions, Wizard of Oz testing) to capture actionable player feedback.
  • Formal Verdict Reporting: Generates a detailed report with day-by-day velocity data, technical findings, and a PROCEED/PIVOT/KILL verdict to formally gate the pre-production to production transition.
  • Use Case: A game studio that has completed GDDs and architecture for a new title can use this Skill to test if the core loop is fun and buildable in 1-3 weeks before allocating a full team to 18+ months of production.

Quick Start

Use the vertical-slice skill to build and test a near-production vertical slice of your game to receive a clear go/no-go verdict for your production commitment.

Frequently Asked Questions about vertical-slice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a vertical slice in game development and when do I need one?

A vertical slice is a near-production build of your game's core loop used to validate feasibility and player engagement before committing to full production. You need it during pre-production after completing game design and architecture documents.

How do I validate if my core game loop is fun before starting full production?

Validate your core game loop by building a near-production vertical slice and running structured playtests using silent walkthroughs, think-aloud sessions, and Wizard of Oz testing to capture actionable player feedback.

Can I use this vertical slice workflow if my team only has a basic game concept?

No, this workflow requires completed game design documents, architecture specifications, and UX specifications. It is designed for pre-production teams ready to test a defined core loop within a 1-3 week build window.

How do I gate the transition from pre-production to full game production?

Gate the transition by generating a formal verdict report with day-by-day velocity data, technical findings, and a PROCEED, PIVOT, or KILL decision based on playtesting results from the vertical slice build.

What's the best way to prevent scope creep during a vertical slice build?

Prevent scope creep during a vertical slice build by applying structured scope definition guardrails and sunk cost checkpoints across the 8 defined phases from initial scope to final verdict reporting.

Why does my game development team waste months building features that are technically unfeasible?

Teams waste production time when they skip validating technical feasibility and player engagement early. Building a vertical slice in pre-production tests if the core loop is buildable and fun before allocating full team resources.