One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill vertical-slice-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vertical-slice
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/vertical-slice
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill vertical-slice-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of committing to full game production without validating that the full game loop can be built at production quality and on schedule, preventing wasted development effort on unviable game concepts.

Core Features & Use Cases

  • End-to-End Vertical Slice Build: Guides the creation of a 3–5 minute near-production-quality build demonstrating a complete start → challenge → resolution game loop.
  • Data-Driven Production Gate: Produces a structured PROCEED/PIVOT/KILL verdict to control the transition from Pre-Production to Production, backed by playtest observations and build velocity data.
  • Use Case: For a 90s F1-style racing game, run this Skill after GDDs, architecture, and UX specs are complete to confirm the full race loop is achievable before allocating the full team to production.

Quick Start

Use the vertical-slice skill to validate your game's full loop feasibility after all design and architecture documents are finalized.

Frequently Asked Questions about vertical-slice

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

FAQPage Schema
How do I validate game loop feasibility before full production?

Use a vertical slice to validate game loop feasibility by building a 3–5 minute near-production-quality build demonstrating a complete start to challenge to resolution cycle before committing to full production.

What is a vertical slice in game development pre-production?

A vertical slice in game development pre-production is a structured validation workflow that tests player experience, content pipeline capability, and development velocity to produce a data-driven PROCEED, PIVOT, or KILL production verdict.

When do I need to run a vertical slice playtest for my game?

You need to run a vertical slice playtest after game design documents, technical architecture, and UX specifications are complete, providing structured validation of the player experience before allocating your full team to production sprints.

How do I track development velocity during a vertical slice build?

Track development velocity during a vertical slice build by documenting day-by-day velocity metrics alongside playtest observations, producing data that directly informs production sprint planning and the final production gate decision.

Can I use a vertical slice to decide whether to pivot or kill a game concept?

Yes, a vertical slice produces a structured PROCEED, PIVOT, or KILL verdict backed by documented playtest observations and build velocity data, allowing you to confidently control the transition from pre-production to production.

What are the limitations of vertical slice validation for game production?

Vertical slice validation is limited to pre-production workflows where game design documents, technical architecture, and UX specifications are already complete, requiring a time-boxed 1–3 week commitment to produce a near-production-quality build.