Menu
生成高烈度改局 planning branch proposal，只产出分支提案，不直接写正式 chapter planning 产物。
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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.
根据参考拆解结果编译 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 | booming |
| description | 生成高烈度改局 planning branch proposal，只产出分支提案，不直接写正式 chapter planning 产物。 |
| argument-hint | <project-id> [chapter-id] [brief] |
| disable-model-invocation | true |
用于章节规划阶段的高烈度改局分支。它只调用：
python app.py booming <project_id> --chapter-id <chapter_id> --brief "<强化要求>"
约束：
chapters/<chapter_id>/planning_branches/*.json。chapter_goal.json、chapter_outline.json 或正式 source assets。python app.py merge-planning-branch <project_id> --chapter-id <chapter_id> --branch-file <branch_file> 生成 chapter_planning proposal。projects/$0/published/effective_views/authoring_view.json、projects/$0/chapters/${1:-ch001}/chapter_plan_source.json、projects/$0/chapters/${1:-ch001}/chapter_goal.json。projects/$0/chapters/${1:-ch001}/planning_branches/*.json，状态为 proposal。chapter_goal.json、chapter_outline.json、scene_beats.json 或任何 source_assets/*；不要绕过 merge-planning-branch 和 confirm-stage。