菜单
生成 authoring_setup proposal，并通过 scoped publish 更新 project_playbook、input_policy、output_policy、failure_mode_policy 或 planning_branch_modes。Use when authoring contract needs setup or revision.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
拆解参考作品、提炼节奏、情绪、场景结构与禁用模式。Use when benchmarking imported novels from projects/<project-id>/references/raw/ and writing v2 outputs into source_assets/reference_analysis/.
生成高烈度改局 planning branch proposal，只产出分支提案，不直接写正式 chapter planning 产物。
根据参考拆解结果编译 style_dna、scene_formulas、reader_hook_map、banned_patterns 和 prose_constraints。Use when source_assets/reference_analysis/reference_summary.json and reports/ already exist.
根据 published views 与 chapter planning source 生成章节 proposal；必要时调用 discussion agents，并通过 confirm-stage chapter_planning 生效。Use when chapter_planning is ready or a chapter plan needs revision.
为单张角色卡生成或修订 proposal，并通过 scoped confirm-stage materialize。Use when a character card needs creation, revision, lifecycle change, or reactivation.
检索 effective views 与章节归档，并生成当前章节的 published compiled packs。Use when scene beats, context_permission_source, and context_query are ready.
| name | authoring-room |
| description | 生成 authoring_setup proposal，并通过 scoped publish 更新 project_playbook、input_policy、output_policy、failure_mode_policy 或 planning_branch_modes。Use when authoring contract needs setup or revision. |
| argument-hint | <project-id> [scope] |
| disable-model-invocation | true |
$0：project_id$1：可选 scope，默认为 bundle；可选值为 bundle、playbook、input-policy、output-policy、failure-mode-policy、branch-registrypython app.py ensure-prereq "$0" authoring_setup，确认 story setup 或 bootstrap seed 已可支撑 authoring proposal。playbook-architect、input-policy-designer、output-contract-designer、failure-mode-policy-designer、branch-mode-designer；增量字段修订统一交给 asset-reviser。python app.py authoring-room "$0" --scope "${1:-bundle}"，生成 workflow/pending_confirmations/authoring_setup.json。project_playbook_asset.json、input_interpretation_policy.json、output_sidecar_contract.json、failure_mode_policy.json、planning_branch_registry.json 中本 scope 的预览内容是否成立。python app.py confirm-stage "$0" authoring_setup --scope "${1:-bundle}"。projects/$0/source_assets/authoring_setup/authoring_setup_manifest.json、projects/$0/published/effective_views/authoring_view.json、projects/$0/workflow/view_readiness_report.json，确认 authoring contract 已进入 consumer-ready 状态。/chapter-room、/scene-room、/compile-context、/review-chapter 或 /finalize-chapter。--scope bundle--scope playbook--scope input-policy--scope output-policy--scope failure-mode-policy--scope branch-registryprojects/$0/source_assets/story_setup/story_setup_brief.json、projects/$0/source_assets/story_setup/story_core_asset.json、source_assets/authoring_setup/project_playbook_asset.json、source_assets/authoring_setup/input_interpretation_policy.json、source_assets/authoring_setup/output_sidecar_contract.json、source_assets/authoring_setup/failure_mode_policy.json、source_assets/authoring_setup/planning_branch_registry.json、projects/$0/published/effective_views/authoring_view.json。projects/$0/workflow/pending_confirmations/authoring_setup.json；只有在 confirm-stage 后，才正式落 projects/$0/source_assets/authoring_setup/project_playbook_asset.json、input_interpretation_policy.json、output_sidecar_contract.json、failure_mode_policy.json、planning_branch_registry.json、authoring_setup_manifest.json，并刷新 published/effective_views/authoring_view.json。confirm-stage 直接把 proposal 当正式 authoring asset；不要直接手写 published/effective_views/authoring_view.json；不要直接改正文、章纲、beats、review 或 finalize 报告；discussion agents 只能输出 proposal-only 结果，不能 materialize 正式 source assets。