prototype

Validate unproven game concepts via throwaway prototypes with PROCEED/PIVOT/KILL verdicts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often waste weeks or months writing full game design documents, building production code, and allocating resources for unproven game concepts that fail to deliver fun or engaging core gameplay. This Skill eliminates that waste by enabling fast, low-cost validation of core ideas before any significant investment in full production.

Core Features & Use Cases

  • Multi-path prototype routing: Automatically selects the optimal prototype path (HTML for logic/puzzle games, engine for action/feel-focused games, paper for rule/strategy games) based on your game genre and hypothesis.
  • Structured verdict system: Produces a clear PROCEED, PIVOT, or KILL recommendation backed by playtest data to remove guesswork from go/no-go decisions.
  • Use Case: An indie developer with a new 2D platformer concept can run a 1-3 day engine prototype to test if the core movement feels fun, get a data-backed verdict, and avoid writing a 50-page GDD for an idea that doesn't work.

Quick Start

Invoke the prototype skill with your new game concept description to run a throwaway prototype and receive a PROCEED/PIVOT/KILL recommendation on whether to invest in full development.

Frequently Asked Questions about prototype

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

FAQPage Schema
How do I validate a game concept before writing a full design document?

You validate a game concept by running a fast throwaway prototype to test core fun and logic. This approach delivers a structured PROCEED, PIVOT, or KILL verdict backed by playtest data before you invest in full production.

What is the best way to prototype different game genres?

The best way to prototype different game genres is using tailored prototype paths based on genre needs: HTML for logic or puzzle games, engine prototypes for action or feel-focused games, and paper prototypes for rule-based strategy games.

How do I know if my indie game idea is worth full development?

You know if your indie game idea is worth full development by obtaining a formal prototype report with a PROCEED, PIVOT, or KILL recommendation. This verdict is backed by playtest data to remove guesswork from your go or no-go decision.

Can I test core game mechanics without building production code?

Yes, you can test core game mechanics without building production code by using throwaway prototypes. These fast, low-cost prototypes validate whether unproven ideas deliver engaging gameplay before you allocate significant development resources.

When should I use a paper prototype instead of an engine prototype?

You should use a paper prototype instead of an engine prototype when validating rule-based or strategy games. Engine prototypes are better suited for testing if core movement and action feel fun in feel-focused games.

How long does it take to run a game prototype for concept validation?

Running a game prototype for concept validation takes one to three days. This fast process tests core gameplay elements, generates playtest data, and delivers a formal report to inform your production decisions.