| name | gamespec-creator |
| description | Create, refine, or validate a Markdown GameSpec from offline game materials such as rules, wikis, video transcripts, replays, input records, or existing adapters. Use when adapting a new game or revising its stable world model. Do not use for live play, runtime strategy changes, or immediate input generation. |
GameSpec Creator
Build a candidate GameSpec that another Agent can inspect and validate before a game session. Keep rules and observable facts separate from runtime Strategy and Action decisions.
Choose the operation
create: start from a minimal game identity and offline sources.refine: incorporate new sources or evidence into an existing GameSpec without losing provenance.validate: inspect schema, references, unsupported claims, contradictions, and the GameSpec/Strategy/Action boundary without rewriting unless requested.
Read generation contract before creating or refining a GameSpec. Read it during validation when checking document structure or evidence status.
Workflow
- Identify the stable game identity, compatible version range, intended interaction modes, and source set. Do not create separate GameSpecs for MCP, visual, platform, or resolution variants of the same ruleset.
- Separate directly supported facts from cross-source inferences and hypotheses that require online validation.
- Generate
GAMESPEC.md. Put rules, goals, information boundaries, observable concepts, control meanings, and compatibility in GameSpec.
- Keep tactics in Strategy documents. Keep executable cursor, keyboard, controller, or MCP programs in Action documents. GameSpec may name semantic controls but must not contain arbitrary executable code.
- Set generated GameSpecs to
candidate. Use the Game Agent MCP validate_gamespec tool when available; otherwise validate against the bundled schema and contract. Report unresolved hypotheses explicitly.
- Never replace a Published GameSpec used by an active session. A runtime contradiction becomes a sourced proposal for a later offline
refine operation.
Return the created or changed paths, validation result, and remaining hypotheses. Do not claim that a candidate is published or behaviorally verified merely because its Markdown is schema-valid.
