Practical guide · 实用指南

How to adapt a novel into a game candidate

如何用 Novel to Game 把小说改编成游戏候选版本

Source checked 2026-09-12 · 源码核对日期

Start with a novel you own or are authorized to adapt, install the seven skills, and give the agent a small target experience. Lock the product brief before building, then ask for one complete runtime verification. A folder of design documents or a successful build alone is not a playable-game result.

从你拥有或获准改编的小说开始，安装七个 skills，并给 Agent 一个范围较小的目标体验。构建前先锁定产品简报，之后要求一次完整的运行验证。只有设计文档，或只有构建成功，都不能算作游戏已经可玩。

Novel to Game Source on GitHub

Before you start · 开始之前

A novel file, directory or link, plus an explicit rights/asset boundary. Do not treat access to a text as permission to adapt it.
A configured agent host. The installation table distinguishes Claude Code /novel-to-game, Codex $novel-to-game and Kimi Code /skill:novel-to-game; use the matching adapter.
An available engine and target runtime, or a documented plan for obtaining them. Model, media and tool services may require separate configuration or cost approval.

小说文件、目录或链接，以及明确的改编与素材使用边界。能访问文本不等于已经获准改编。
已配置的 Agent 宿主。安装表区分 Claude Code 的 /novel-to-game、Codex 的 $novel-to-game 与 Kimi Code 的 /skill:novel-to-game，请选择对应适配器。
可用的引擎和目标运行环境，或明确的准备计划。模型、媒体与工具服务可能需要另行配置或费用授权。

Steps · 操作步骤

Install and choose a mode Use the source README installation row for your host. quick recommends defaults and continues; director lets you choose the concept; resume reads the existing workspace and resumes from the earliest incomplete handoff.
Set the product brief Ask for PRODUCT_BRIEF.md: scope, language, experience type, platform, engine, target runtime, tested runtime, input/display requirements, content limits and rights/asset boundaries. Ordinary assumptions can be recorded; material or safety-sensitive decisions require resolution.
Ground the adaptation Review analysis/SOURCE_BIBLE.md for actual source evidence and concepts/CONCEPT.md for the chosen concept and trade-offs. If you want an interactive story, say so explicitly instead of letting a systems-game format be assumed.
Design and build a small candidate Follow design/GAME_DESIGN.md, a risk-matched whitebox where needed, design/ART_DIRECTION.md and build/BUILD_BRIEF.md. Keep the first candidate small enough to exercise a complete loop rather than expanding its feature list.
Verify in the chosen runtime Run the commands recorded in the build brief and collect launch, render, input, coreLoop, outcome and restart evidence from one complete run. A substitute runtime does not establish target-platform compatibility.
Resume honestly Read qa/verification.json, evidence files and _progress.md. Fix the earliest failed handoff and rerun verification; do not convert missing tooling or untested behavior into PASS.

安装并选择模式 使用源码 README 中对应宿主的安装行。quick 推荐默认值并继续；director 让你选择概念；resume 读取现有工作区，从最早未完成的交接处恢复。
确定产品简报 要求建立 PRODUCT_BRIEF.md，明确范围、语言、体验类型、平台、引擎、目标运行环境、实际测试环境、输入与显示要求、内容尺度及权利/素材边界。普通假设可以记录；实质分支或安全敏感决策必须解决。
让改编有原文依据 检查 analysis/SOURCE_BIBLE.md 的原文证据，以及 concepts/CONCEPT.md 中选定的概念与取舍。想做互动故事时要明确说出，不要默认接受系统型游戏形式。
设计并构建小范围候选版本 依次依据 design/GAME_DESIGN.md、按需的风险匹配白盒、design/ART_DIRECTION.md 与 build/BUILD_BRIEF.md 推进。先把范围控制到能验证完整循环，而不是不断增加功能。
在选定环境中验证 运行构建简报记录的命令，用同一次完整运行收集 launch、render、input、coreLoop、outcome 和 restart 证据。替代运行环境通过不代表目标平台兼容。
如实恢复工作 读取 qa/verification.json、证据文件和 _progress.md，先修复最早失败的交接，再重新验证；工具缺失或行为未测试不能改写成 PASS。

Example · 示例

Terminal — install the Claude Code adapter:
npx skills add zenstory-ai/novel-to-game -g -y -a claude-code -s '*'

Then ask in Claude Code (replace the source path):
/novel-to-game quick
Use /ABS/my-authorized-novel.txt to create a small interactive-story candidate.
Draft PRODUCT_BRIEF.md first and record the target and tested runtimes.
Keep one complete loop, outcome and restart in scope.
Report missing tools and untested behavior rather than marking them PASS.

终端——安装 Claude Code 适配器：
npx skills add zenstory-ai/novel-to-game -g -y -a claude-code -s '*'

然后在 Claude Code 中请求（替换小说路径）：
/novel-to-game quick
用 /ABS/my-authorized-novel.txt 制作小范围的互动故事候选版本。
先写 PRODUCT_BRIEF.md，记录目标与实际测试运行环境。
范围内保留完整循环、设计结果和重开。
如实报告工具缺失或未测试行为，不把它们标为 PASS。

Expected files · 预期文件

Scope: PRODUCT_BRIEF.md; source evidence: analysis/SOURCE_BIBLE.md; selected concept: concepts/CONCEPT.md.
Design: design/GAME_DESIGN.md and design/ART_DIRECTION.md; build instructions: build/BUILD_BRIEF.md; candidate: build/app/.
Runtime record: qa/verification.json plus its referenced evidence; progress and next handoff: _progress.md.

范围：PRODUCT_BRIEF.md；原文证据：analysis/SOURCE_BIBLE.md；选定概念：concepts/CONCEPT.md。
设计：design/GAME_DESIGN.md 与 design/ART_DIRECTION.md；构建说明：build/BUILD_BRIEF.md；候选产物：build/app/。
运行记录：qa/verification.json 及其引用的证据；进度与下一交接：_progress.md。

Verify the result · 验证结果与边界

The QA record uses NOT_RUN, FAIL or PASS. The six required checks are launch, render, input, coreLoop, outcome and restart; collect their evidence in one complete run rather than stitching unrelated partial successes together.
A PASS is limited to the recorded runtime, build and checked behavior. It does not certify fun, balance, commercial readiness or rights clearance.
Missing tools, provider access or an untested target remain explicit limitations. A validator fixture checks the record format; it is not evidence that your adaptation runs.

QA 记录使用 NOT_RUN、FAIL 或 PASS。六项必检为 launch、render、input、coreLoop、outcome、restart；证据应来自同一次完整运行，不能拼接彼此无关的局部成功。
PASS 仅覆盖所记录的运行环境、构建与已检查行为，不认证趣味性、平衡性、商业发布准备程度或权利已清理。
工具、服务权限不足或目标环境未测试必须保留为明确限制。验证器样例只检查记录契约，不证明你的改编能够运行。