Starter Adaptation
$490+
For solo builders and consultants testing the workflow in a real project.
- single-buyer commercial path
- basic onboarding pack
- one target adaptation pass
Structured gameplay design for builders who need clear execution
IDEA IN. SYSTEM OUT.
A structured workflow that takes raw game concepts, locks direction, keeps stage order, controls scope, and lands on a gameplay package your AI coding stack can actually continue from.
10 coordinated skills
1 orchestrator-first entry
validated gyro-battle example
spec, plan, runner, and adapter path
Workflow Overview
LOCK DIRECTION
CUT SCOPE
HAND OFF CLEANLY
GAMEPLAY-DESIGN-ORCHESTRATOR
FUN-SOURCE JUDGMENT
PACING PRESSURE
MVP KEEP / CUT
CODING HANDOFF
VALIDATED EXAMPLE
GAMEPLAY-DESIGN-ORCHESTRATOR
FUN-SOURCE JUDGMENT
PACING PRESSURE
MVP KEEP / CUT
CODING HANDOFF
VALIDATED EXAMPLE
The pipeline is the product
One controlled chain from idea to execution handoff.
The value is workflow ownership. One orchestrator. Ordered stages. Explicit loop-backs. Downstream-ready packaging that continues into spec expansion, execution-plan compilation, and runner-managed task coordination.
Current highlighted stage
Input Normalizer
Converts fuzzy input into usable design constraints, target player, emotional goal, platform bounds, and production pressure before the rest of the pipeline begins.
Validated example
Gyro-battle web game, from direction lock to full spec.
gyro-battle/final-package
chosen direction: Arena knock-out combat
strongest promise: land one perfect hit and swing the round
biggest scope risk: unreadable physics becomes random noise
loop-back count: 2
output: package + review notes + spec + execution plan
validation: package passed / spec passed / plan passed / runner path checked
Why this example matters
It proves the workflow can survive contact with a real game concept.
The included gyro-battle sample is not just a pretty mockup. It shows candidate direction selection, pacing corrections, scope cuts, system indexes, prototype acceptance, and downstream chapter-level tasking.
Candidate A vs B
Arena combat won. Deep parts/economy lost for scope reasons.
Revision pressure
Pacing and system stages forced loop-backs before the spec layer.
Downstream packaging
The result carries scenes, UI, rules, tasks, QA, and delivery mapping.
Positioning
Built for teams and operators who need a repeatable workflow.
Generic prompt packs
- start with vibes and genre labels
- no owner for stage order
- easy to bloat scope
- beautiful prose, weak handoff
- no proof beyond screenshots
VS
Gameplay Design Skill Suite
- orchestrator owns the workflow
- downstream stages stay ordered
- MVP keep / cut stays visible
- coding handoff is part of the chain
- spec, execution-plan, and runner checks included
Commercial path
Public showcase outside. Paid leverage inside.
This repo is positioned as a source-available showcase with a commercial path for teams that want onboarding, adaptation, and rollout support.
Team Enablement
$2.4K+
For small studios that want an internal AI-assisted pre-production pipeline.
- team commercial license path
- terminology alignment
- custom example package
Custom Pipeline Build
$8K+
For studios and agencies that want genre-specific, branded, or white-label variants.
- custom skill edits
- revised validators
- deployment and rollout support
FAQ
Questions about product scope and workflow usage.
Is this open source?
No. It is public for evaluation and discovery, but commercial reuse and redistribution are intentionally protected.
Can I trigger the stage skills one by one?
Normally, no. The correct operating model is orchestrator-first. Stage skills are designed as controlled internal steps.
Does this automatically make a shippable game?
No. It compresses pre-production ambiguity and produces stronger handoff materials. It does not replace implementation, tuning, or production judgment.
Why is the final spec in Chinese?
Because the current downstream production target is a Chinese execution format. The workflow logic itself is broader than the language target.
Next Step
Review the example, validate the outputs, and adapt the workflow to your own production stack.
Use the repository as a practical reference for orchestrator-first gameplay design, execution planning, and worker-facing handoff.