القائمة
根据章节合同、effective views 与 scene planning source 生成场景 proposal；必要时调用 discussion agents，并通过 confirm-stage scene_planning 生效。Use when scene_planning is ready or an existing scene 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.
根据 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.
| name | scene-room |
| description | 根据章节合同、effective views 与 scene planning source 生成场景 proposal；必要时调用 discussion agents，并通过 confirm-stage scene_planning 生效。Use when scene_planning is ready or an existing scene plan needs revision. |
| argument-hint | <project-id> [chapter-id] [plan-source-path] [revision-mode] |
| disable-model-invocation | false |
$0：project_id$1：可选，chapter_id，默认 ch001$2：可选，scene_plan_source 路径；为空时默认使用 projects/$0/chapters/${1:-ch001}/scene_plan_source.json$3：可选，revision_mode，默认 bundle；可选 bundle / beat-patchpython app.py ensure-prereq "$0" scene_planning --chapter-id "${1:-ch001}"。scene-architect 收口 beat_strategy、reveal_budget、permission_intent、query_focus。beat-designer 基于 chapter_goal、chapter_outline、authoring_view 和 effective views 产出 proposal-only beat_candidates；已有方案回修统一交给 plan-reviser 输出 field patch，并建议 revision_mode 是 bundle 还是 beat-patch。projects/$0/chapters/${1:-ch001}/scene_plan_source.json，并保留 source_discussion_ref、revision_notes、planning_trace。python app.py scene-room "$0" --chapter-id "${1:-ch001}" --plan-source "${2:-projects/$0/chapters/${1:-ch001}/scene_plan_source.json}" --revision-mode "${3:-bundle}" 生成场景 proposal。projects/$0/workflow/pending_confirmations/scene_planning_${1:-ch001}.json，核对 planning_manifest.json、scene_plan_source.json、scene_beats.json、context_permission_source.json 与 context_query.json 是否一致；必须显式检查 proposal_scope、scene_plan_source_ready、scene_projector_primary_source、scene_template_fallback_used。python app.py confirm-stage "$0" scene_planning --chapter-id "${1:-ch001}" --scope "${3:-bundle}"。planning_manifest.json、scene_plan_source.json、scene_beats.json、context_permission_source.json、context_query.json，确认可进入上下文编译。/compile-context。projects/$0/chapters/${1:-ch001}/chapter_goal.json、projects/$0/chapters/${1:-ch001}/chapter_outline.json、projects/$0/published/effective_views/story_view.json、projects/$0/published/effective_views/authoring_view.json、projects/$0/published/effective_views/thread_view.json、projects/$0/published/effective_views/character_view.json、projects/$0/published/effective_views/world_view.json、projects/$0/chapters/${1:-ch001}/scene_plan_source.json 或用户提供的 plan source。projects/$0/workflow/pending_confirmations/scene_planning_${1:-ch001}.json；只有在 confirm-stage 后，才正式落 projects/$0/chapters/${1:-ch001}/planning_manifest.json、scene_plan_source.json、scene_beats.json、context_permission_source.json、context_query.json。context_permission_source.json 写回其他文件名；不要跳过确认门直接进入 compiled pack 阶段；不要让 discussion agents 直接 materialize scene_beats.json、context_permission_source.json 或 context_query.json；不要把自由文本讨论直接塞进 canonical query；只使用当前章节合同、effective views、authoring_view 与 scene planning source 生成 beats；不要回退到 source_assets/story_setup/story_core_asset.json 或 source_assets/authoring_setup/*.json；不要在 scene_plan_source 已给出结构化策略时再覆盖回固定模板。