菜单
根据 published views 与 chapter planning source 生成章节 proposal；必要时调用 discussion agents，并通过 confirm-stage chapter_planning 生效。Use when chapter_planning is ready or a chapter plan needs 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/.
生成 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.
生成高烈度改局 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.
为单张角色卡生成或修订 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 | chapter-room |
| description | 根据 published views 与 chapter planning source 生成章节 proposal；必要时调用 discussion agents，并通过 confirm-stage chapter_planning 生效。Use when chapter_planning is ready or a chapter plan needs revision. |
| argument-hint | <project-id> [chapter-id] [plan-source-path] [proposal-scope] |
| disable-model-invocation | false |
$0：project_id$1：可选，chapter_id，默认 ch001$2：可选，chapter_plan_source 路径；为空时默认使用 projects/$0/chapters/${1:-ch001}/chapter_plan_source.json$3：可选，proposal_scope，默认 bundle；可选 alignment / bundle / outline-patchpython app.py ensure-prereq "$0" chapter_planning --chapter-id "${1:-ch001}"。chapter-requirement-analyst 收口 user_intent_summary、must_hit_events、must_keep_constraints、ending_hook_options。chapter-architect 基于 story_view、progression_view、authoring_view、recent_summary 与需求摘要产出 proposal-only chapter_plan_source 字段；已有方案回修统一交给 plan-reviser 输出 field patch 与建议 proposal_scope。projects/$0/chapters/${1:-ch001}/chapter_plan_source.json，并保留 source_discussion_ref、revision_notes、planning_trace。python app.py chapter-room "$0" --chapter-id "${1:-ch001}" --plan-source "${2:-projects/$0/chapters/${1:-ch001}/chapter_plan_source.json}" --proposal-scope "${3:-bundle}" 生成章节 proposal。projects/$0/workflow/pending_confirmations/chapter_planning_${1:-ch001}.json，先核对 planning_manifest.json、chapter_plan_source.json 与 chapter_alignment_card.json，再核对 chapter_goal.json 与 chapter_outline.json；必须显式检查 proposal_scope、chapter_plan_source_ready、chapter_projector_primary_source、chapter_template_fallback_used。python app.py confirm-stage "$0" chapter_planning --chapter-id "${1:-ch001}" --scope "${3:-bundle}"。projects/$0/chapters/${1:-ch001}/planning_manifest.json、chapter_plan_source.json、chapter_goal.json 与 chapter_outline.json，确认 chapter contract 已进入正式态。/scene-room。projects/$0/published/effective_views/story_view.json、projects/$0/published/effective_views/progression_view.json、projects/$0/published/effective_views/authoring_view.json、projects/$0/logs/recent_summary.md、projects/$0/chapters/${1:-ch001}/chapter_plan_source.json 或用户提供的 plan source。projects/$0/workflow/pending_confirmations/chapter_planning_${1:-ch001}.json；只有在 confirm-stage 后，才正式落 projects/$0/chapters/${1:-ch001}/planning_manifest.json、chapter_plan_source.json、chapter_alignment_card.json、chapter_goal.json、chapter_outline.json。chapter_alignment_card.json 直接下正式章纲；不要让 discussion agents 直接写正式 chapter_goal.json 或 chapter_outline.json；不要把自由文本讨论直接当 canonical contract；只使用 story_view、progression_view、authoring_view、recent_summary 和 chapter planning source 规划本章；不要回退到 source_assets/story_setup/story_core_asset.json 或 source_assets/authoring_setup/*.json；不要在 chapter_plan_source 已给出结构化决策时再覆盖回固定模板；不要直接进入 /scene-room。