game-prototype
AlterLab GameForge -- Hypothesis-Driven Prototyping
A prototype is an experiment, not a demo. Every prototype exists to answer one question, usually "is this worth building?", and the moment you start polishing it you have stopped prototyping and started building, possibly the wrong thing. This workflow enforces the discipline: name the question, write a hypothesis that can fail, build the cheapest thing that tests it, watch real players, and make a binary kill-or-promote call on the evidence.
Coding agents changed the cost of the build step, not the discipline. An agent can produce a playable throwaway in an hour, which makes it tempting to skip the question and "just build it." Cheap builds make a clear question more important, not less: without one you get ten prototypes and no answers.
Continuity through files. Read .gameforge/project.json (pillars, phase), design/concept.md,
earlier reports in design/prototypes/, and production/session-state/active.md. Each prototype
lives in prototypes/<name>/ with a QUESTION.md; the report goes to
design/prototypes/<name>-report.md; active.md gets the decision and the next step. If the
project's phase is still concept or pre-production, offer to set it to prototype.