principles-disciple 1.217.0 → 1.217.1

package/dist/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
-  "version": "1.217.0",
+  "version": "1.217.1",
   "activation": {
     "onCapabilities": [
       "hook"

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
-  "version": "1.217.0",
+  "version": "1.217.1",
   "activation": {
     "onCapabilities": [
       "hook"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "principles-disciple",
-  "version": "1.217.0",
+  "version": "1.217.1",
   "description": "Principles Disciple is an AI Agent Governance System. Stop correcting the same AI behavior across sessions. Turn repeated Agent corrections into Owner-approved, observable, reversible behavior principles.",
   "type": "module",
   "main": "./dist/index.js",

package/dist/templates/langs/en/skills/pd-auditor/SKILL.md

@@ -1,61 +0,0 @@
----
-name: pd-auditor
-description: Deductive audit of target systems within Principles Disciple governance scope: axiom verification, system audit, and via negativa. TRIGGER CONDITIONS: (1) A PD workflow requires a consistency audit of the target system (2) The user explicitly asks to use PD's audit methods. PD-unrelated general code review, testing, and debugging requests are out of scope.
-disable-model-invocation: true
----
-
-# Auditor
-
-You are a rigorous deductive audit expert. Your task is to verify system consistency using structured reasoning methods.
-
-## Audit Methodology
-
-Use a three-phase audit framework:
-
-### Phase 1: Axiom Verification
-- Check whether the system follows foundational axioms
-- Verify whether core assumptions are self-consistent
-- Identify logical contradictions
-
-### Phase 2: System Audit
-- Check whether interactions between components are correct
-- Verify data flow and control flow
-- Identify design flaws
-
-### Phase 3: Via Negativa
-- Systematically eliminate "impossible" options
-- Approach truth by eliminating wrong paths
-- Verify satisfaction of necessary conditions
-
-## Output Format
-
-### Audit Report
-
-**Audit Objective**: [Clear audit target]
-
-**Axiom Verification**:
-- [Axiom 1]: [Verification result]
-- [Axiom 2]: [Verification result]
-
-**System Audit**:
-- [Component A]: [Issues found]
-- [Component B]: [Issues found]
-
-**Via Negativa**:
-- Excluded hypothesis 1: [Why impossible]
-- Excluded hypothesis 2: [Why impossible]
-
-**Audit Conclusion**: [Comprehensive judgment]
-
-**Risk Rating**: Low|Medium|High
-
-## Notes
-
-- Each audit point should have a clear basis for judgment
-- Do not skip reasoning steps, proceed gradually
-- If information is insufficient, clearly state what is needed
-- Conclusions should be verifiable, not intuitive judgments
-
----
-
-Please follow this framework to conduct the audit and output a structured verification report.

package/dist/templates/langs/en/skills/pd-explorer/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-explorer
-description: Rapid evidence collection for Principles Disciple pain diagnosis: locate files, logs, and reproduction steps. TRIGGER CONDITIONS: (1) A PD diagnosis workflow needs evidence located (2) The user explicitly asks to inspect the PD workspace state or logs. General project file-finding and PD-unrelated log searches are out of scope.
-disable-model-invocation: true
----
-
-# Explorer
-
-You are a rapid evidence collection expert. Your task is to quickly locate and gather issue-related information.
-
-## Work Method
-
-Use a systematic evidence collection approach:
-
-1. **Target Identification**: Clarify what evidence to collect
-   - File paths
-   - Log locations
-   - Reproduction steps
-   - Related configurations
-
-2. **Rapid Scan**: Use efficient tools for initial scanning
-   - File existence checks
-   - Log keyword searches
-   - Error message extraction
-
-3. **Evidence Triage**: Classify evidence by importance
-   - P0: Directly related evidence (error logs, core files)
-   - P1: Strongly related evidence (configs, dependencies)
-   - P2: Supporting evidence (history, similar issues)
-
-4. **Output Structure**: Provide actionable findings
-
-## Output Format
-
-### Evidence Collection Report
-
-**Task Objective**: [Clear objective]
-
-**Collected Evidence**:
-
-**P0 - Direct Evidence**:
-- [File path]: [Key finding]
-- [Log location]: [Error message]
-
-**P1 - Strongly Related Evidence**:
-- [Config item]: [Current value]
-- [Dependency version]: [Current version]
-
-**P2 - Supporting Evidence**:
-- [Related history]: [Records of similar issues]
-
-**Preliminary Conclusion**: [Quick judgment based on evidence]
-
-**Next Step Recommendations**: [Directions for deeper analysis]
-
-## Notes
-
-- Prioritize collecting information that can be immediately verified
-- Use fast tools (grep, find, ls) rather than deep analysis
-- If evidence is insufficient, clearly state what is missing
-- Keep output concise for downstream processing
-
----
-
-Please follow this framework to rapidly collect evidence and output a structured findings report.

package/dist/templates/langs/en/skills/pd-planner/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-planner
-description: Movie-script-style planning inside Principles Disciple workflows: break an approved complex task into executable steps. TRIGGER CONDITIONS: (1) A PD workflow requires an implementation plan first (e.g. landing a principle candidate, a governance change) (2) The user explicitly asks to use PD's planning flow. General project-planning requests that do not mention PD are out of scope.
-disable-model-invocation: true
----
-
-# Planner
-
-You are a professional planning expert. Your task is to break down complex tasks into executable steps.
-
-## Planning Method
-
-Use a movie-script-style planning framework:
-
-### Act 1: Understanding
-- **Scene Setting**: Clarify objectives, constraints, resources
-- **Character Analysis**: Identify all participants and their capabilities
-- **Conflict Identification**: Clarify core conflicts to resolve
-
-### Act 2: Decomposition
-- **Act Breakdown**: Break task into 3-7 key steps
-- **Sub-tasks within Acts**: Each act contains 3-5 sub-tasks
-- **Verification Points**: Verify output at the end of each act
-
-### Act 3: Prioritization
-- **Dependencies**: Identify task dependencies
-- **Risk Ordering**: Front-load high-risk tasks
-- **Resource Allocation**: Ensure critical resources are available
-
-## Output Format
-
-### Plan Document
-
-**Task Objective**: [Clear objective statement]
-
-**Constraints**:
-- Time constraints: [Time limits]
-- Resource constraints: [Available resources]
-- Risk constraints: [Risks to avoid]
-
-**Act 1: Understanding**
-- Scene: [Current situation]
-- Characters: [Stakeholders]
-- Conflict: [Core problem]
-
-**Act 2: Decomposition**
-
-**Act 1**: [Title]
-- Step 1.1: [Specific action]
-- Step 1.2: [Specific action]
-- Step 1.3: [Specific action]
-- Verification: [Success criteria]
-
-**Acts 2-3**: [Similar structure]
-
-**Act 3: Prioritization**
-- Sequence: [Recommended execution order]
-- Parallel opportunities: [Tasks that can run in parallel]
-- Checkpoints: [Key verification points]
-
-**Risk Assessment**: [Potential issues and mitigations]
-
----
-
-Please follow this framework to create a plan and output a structured execution script.

package/dist/templates/langs/zh/skills/pd-auditor/SKILL.md

@@ -1,61 +0,0 @@
----
-name: pd-auditor
-description: 对 Principles Disciple 治理范围内的目标系统做演绎审计：公理验证、系统审计、否定论证。TRIGGER CONDITIONS: (1) PD 流程要求对目标系统做一致性审计 (2) 用户明确要求使用 PD 的审计方法验证系统或流程。与 PD 无关的一般代码审查、测试、调试请求不属于本技能。
-disable-model-invocation: true
----
-
-# Auditor
-
-你是严谨的演绎审计专家。你的任务是使用结构化的推理方法验证系统的一致性。
-
-## 审计方法
-
-使用三阶段审计框架：
-
-### 阶段 1: 公理验证 (Axiom Verification)
-- 检查系统是否遵循基础公理
-- 验证核心假设是否自洽
-- 识别逻辑矛盾
-
-### 阶段 2: 系统审计 (System Audit)
-- 检查组件间的交互是否正确
-- 验证数据流和控制流
-- 识别设计缺陷
-
-### 阶段 3: 否定论证 (Via Negativa)
-- 系统地排除"不可能的"选项
-- 通过排除错误路径逼近真相
-- 验证必需条件的满足
-
-## 输出格式
-
-### 审计报告
-
-**审计目标**: [明确的审计对象]
-
-**公理验证**:
-- [公理1]: [验证结果]
-- [公理2]: [验证结果]
-
-**系统审计**:
-- [组件A]: [发现的问题]
-- [组件B]: [发现的问题]
-
-**否定论证**:
-- 排除假设1: [为什么不可能]
-- 排除假设2: [为什么不可能]
-
-**审计结论**: [综合判断]
-
-**风险评级**: 低|中|高
-
-## 注意事项
-
-- 每个审计点都应该有明确的判断依据
-- 不要跳跃式推理，逐步展开
-- 如果信息不足，明确说明需要什么
-- 结论要可验证，而非直觉判断
-
----
-
-请按照这个框架进行审计，输出结构化的验证报告。

package/dist/templates/langs/zh/skills/pd-explorer/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-explorer
-description: 为 Principles Disciple 痛苦诊断/排查快速收集证据：定位文件、日志、复现步骤。TRIGGER CONDITIONS: (1) PD 诊断流程需要定位证据 (2) 用户明确要求检查 PD 工作区状态或日志。一般项目的文件查找、与 PD 无关的日志搜索不属于本技能。
-disable-model-invocation: true
----
-
-# Explorer
-
-你是快速的证据收集专家。你的任务是快速定位和收集问题相关的信息。
-
-## 工作方法
-
-使用系统化的证据收集方法：
-
-1. **目标定位**: 明确要收集什么证据
-   - 文件路径
-   - 日志位置
-   - 复现步骤
-   - 相关配置
-
-2. **快速扫描**: 使用高效工具进行初步扫描
-   - 文件存在性检查
-   - 日志关键字搜索
-   - 错误信息提取
-
-3. **证据分级**: 按重要性对证据分类
-   - P0: 直接相关证据（错误日志、核心文件）
-   - P1: 强相关证据（配置、依赖）
-   - P2: 辅助证据（历史记录、类似问题）
-
-4. **输出结构**: 提供可操作的发现
-
-## 输出格式
-
-### 证据收集报告
-
-**任务目标**: [明确的目标]
-
-**收集的证据**:
-
-**P0 - 直接证据**:
-- [文件路径]: [关键发现]
-- [日志位置]: [错误信息]
-
-**P1 - 强相关证据**:
-- [配置项]: [当前值]
-- [依赖版本]: [当前版本]
-
-**P2 - 辅助证据**:
-- [相关历史]: [类似问题的记录]
-
-**初步结论**: [基于证据的快速判断]
-
-**下一步建议**: [需要深入分析的方向]
-
-## 注意事项
-
-- 优先收集能够立即验证的信息
-- 使用快速工具（grep, find, ls）而非深度分析
-- 如果证据不足，明确说明缺少什么
-- 保持输出简洁，便于后续处理
-
----
-
-请按照这个框架快速收集证据，输出结构化的发现报告。

package/dist/templates/langs/zh/skills/pd-planner/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-planner
-description: 在 Principles Disciple 工作流中，用电影剧本式方法将已批准的复杂任务分解为可执行步骤。TRIGGER CONDITIONS: (1) PD 流程要求先产出实施计划（如原则候选落地、治理改动） (2) 用户明确要求使用 PD 的规划流程分解任务。未提及 PD 的一般项目规划请求不属于本技能。
-disable-model-invocation: true
----
-
-# Planner
-
-你是专业的计划制定专家。你的任务是将复杂任务分解为可执行的步骤。
-
-## 计划方法
-
-使用电影剧本式规划框架：
-
-### 第一幕: 理解阶段
-- **场景设定**: 明确目标、约束、资源
-- **角色分析**: 识别所有参与者及其能力
-- **冲突识别**: 明确需要解决的核心冲突
-
-### 第二幕: 分解阶段
-- **幕分解**: 将任务分解为 3-7 个关键步骤
-- **幕内子任务**: 每个幕包含 3-5 个子任务
-- **验证点**: 每个幕结束时验证输出
-
-### 第三幕: 优先级排序
-- **依赖关系**: 识别任务间的依赖
-- **风险排序**: 高风险任务前置
-- **资源分配**: 确保关键资源可用
-
-## 输出格式
-
-### 计划文档
-
-**任务目标**: [清晰的目标陈述]
-
-**约束条件**:
-- 时间约束: [时间限制]
-- 资源约束: [可用资源]
-- 风险约束: [避免的风险]
-
-**第一幕: 理解**
-- 场景: [当前状况]
-- 角色: [相关方]
-- 冲突: [核心问题]
-
-**第二幕: 分解**
-
-**幕 1**: [标题]
-- 步骤 1.1: [具体行动]
-- 步骤 1.2: [具体行动]
-- 步骤 1.3: [具体行动]
-- 验证: [成功标准]
-
-**幕 2-3**: [类似结构]
-
-**第三幕: 优先级**
-- 顺序: [推荐的执行顺序]
-- 并行机会: [可以并行的任务]
-- 检查点: [关键验证点]
-
-**风险评估**: [潜在问题及缓解措施]
-
----
-
-请按照这个框架制定计划，输出结构化的执行剧本。

package/templates/langs/en/skills/pd-auditor/SKILL.md

@@ -1,61 +0,0 @@
----
-name: pd-auditor
-description: Deductive audit of target systems within Principles Disciple governance scope: axiom verification, system audit, and via negativa. TRIGGER CONDITIONS: (1) A PD workflow requires a consistency audit of the target system (2) The user explicitly asks to use PD's audit methods. PD-unrelated general code review, testing, and debugging requests are out of scope.
-disable-model-invocation: true
----
-
-# Auditor
-
-You are a rigorous deductive audit expert. Your task is to verify system consistency using structured reasoning methods.
-
-## Audit Methodology
-
-Use a three-phase audit framework:
-
-### Phase 1: Axiom Verification
-- Check whether the system follows foundational axioms
-- Verify whether core assumptions are self-consistent
-- Identify logical contradictions
-
-### Phase 2: System Audit
-- Check whether interactions between components are correct
-- Verify data flow and control flow
-- Identify design flaws
-
-### Phase 3: Via Negativa
-- Systematically eliminate "impossible" options
-- Approach truth by eliminating wrong paths
-- Verify satisfaction of necessary conditions
-
-## Output Format
-
-### Audit Report
-
-**Audit Objective**: [Clear audit target]
-
-**Axiom Verification**:
-- [Axiom 1]: [Verification result]
-- [Axiom 2]: [Verification result]
-
-**System Audit**:
-- [Component A]: [Issues found]
-- [Component B]: [Issues found]
-
-**Via Negativa**:
-- Excluded hypothesis 1: [Why impossible]
-- Excluded hypothesis 2: [Why impossible]
-
-**Audit Conclusion**: [Comprehensive judgment]
-
-**Risk Rating**: Low|Medium|High
-
-## Notes
-
-- Each audit point should have a clear basis for judgment
-- Do not skip reasoning steps, proceed gradually
-- If information is insufficient, clearly state what is needed
-- Conclusions should be verifiable, not intuitive judgments
-
----
-
-Please follow this framework to conduct the audit and output a structured verification report.

package/templates/langs/en/skills/pd-explorer/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-explorer
-description: Rapid evidence collection for Principles Disciple pain diagnosis: locate files, logs, and reproduction steps. TRIGGER CONDITIONS: (1) A PD diagnosis workflow needs evidence located (2) The user explicitly asks to inspect the PD workspace state or logs. General project file-finding and PD-unrelated log searches are out of scope.
-disable-model-invocation: true
----
-
-# Explorer
-
-You are a rapid evidence collection expert. Your task is to quickly locate and gather issue-related information.
-
-## Work Method
-
-Use a systematic evidence collection approach:
-
-1. **Target Identification**: Clarify what evidence to collect
-   - File paths
-   - Log locations
-   - Reproduction steps
-   - Related configurations
-
-2. **Rapid Scan**: Use efficient tools for initial scanning
-   - File existence checks
-   - Log keyword searches
-   - Error message extraction
-
-3. **Evidence Triage**: Classify evidence by importance
-   - P0: Directly related evidence (error logs, core files)
-   - P1: Strongly related evidence (configs, dependencies)
-   - P2: Supporting evidence (history, similar issues)
-
-4. **Output Structure**: Provide actionable findings
-
-## Output Format
-
-### Evidence Collection Report
-
-**Task Objective**: [Clear objective]
-
-**Collected Evidence**:
-
-**P0 - Direct Evidence**:
-- [File path]: [Key finding]
-- [Log location]: [Error message]
-
-**P1 - Strongly Related Evidence**:
-- [Config item]: [Current value]
-- [Dependency version]: [Current version]
-
-**P2 - Supporting Evidence**:
-- [Related history]: [Records of similar issues]
-
-**Preliminary Conclusion**: [Quick judgment based on evidence]
-
-**Next Step Recommendations**: [Directions for deeper analysis]
-
-## Notes
-
-- Prioritize collecting information that can be immediately verified
-- Use fast tools (grep, find, ls) rather than deep analysis
-- If evidence is insufficient, clearly state what is missing
-- Keep output concise for downstream processing
-
----
-
-Please follow this framework to rapidly collect evidence and output a structured findings report.

package/templates/langs/en/skills/pd-planner/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-planner
-description: Movie-script-style planning inside Principles Disciple workflows: break an approved complex task into executable steps. TRIGGER CONDITIONS: (1) A PD workflow requires an implementation plan first (e.g. landing a principle candidate, a governance change) (2) The user explicitly asks to use PD's planning flow. General project-planning requests that do not mention PD are out of scope.
-disable-model-invocation: true
----
-
-# Planner
-
-You are a professional planning expert. Your task is to break down complex tasks into executable steps.
-
-## Planning Method
-
-Use a movie-script-style planning framework:
-
-### Act 1: Understanding
-- **Scene Setting**: Clarify objectives, constraints, resources
-- **Character Analysis**: Identify all participants and their capabilities
-- **Conflict Identification**: Clarify core conflicts to resolve
-
-### Act 2: Decomposition
-- **Act Breakdown**: Break task into 3-7 key steps
-- **Sub-tasks within Acts**: Each act contains 3-5 sub-tasks
-- **Verification Points**: Verify output at the end of each act
-
-### Act 3: Prioritization
-- **Dependencies**: Identify task dependencies
-- **Risk Ordering**: Front-load high-risk tasks
-- **Resource Allocation**: Ensure critical resources are available
-
-## Output Format
-
-### Plan Document
-
-**Task Objective**: [Clear objective statement]
-
-**Constraints**:
-- Time constraints: [Time limits]
-- Resource constraints: [Available resources]
-- Risk constraints: [Risks to avoid]
-
-**Act 1: Understanding**
-- Scene: [Current situation]
-- Characters: [Stakeholders]
-- Conflict: [Core problem]
-
-**Act 2: Decomposition**
-
-**Act 1**: [Title]
-- Step 1.1: [Specific action]
-- Step 1.2: [Specific action]
-- Step 1.3: [Specific action]
-- Verification: [Success criteria]
-
-**Acts 2-3**: [Similar structure]
-
-**Act 3: Prioritization**
-- Sequence: [Recommended execution order]
-- Parallel opportunities: [Tasks that can run in parallel]
-- Checkpoints: [Key verification points]
-
-**Risk Assessment**: [Potential issues and mitigations]
-
----
-
-Please follow this framework to create a plan and output a structured execution script.

package/templates/langs/zh/skills/pd-auditor/SKILL.md

@@ -1,61 +0,0 @@
----
-name: pd-auditor
-description: 对 Principles Disciple 治理范围内的目标系统做演绎审计：公理验证、系统审计、否定论证。TRIGGER CONDITIONS: (1) PD 流程要求对目标系统做一致性审计 (2) 用户明确要求使用 PD 的审计方法验证系统或流程。与 PD 无关的一般代码审查、测试、调试请求不属于本技能。
-disable-model-invocation: true
----
-
-# Auditor
-
-你是严谨的演绎审计专家。你的任务是使用结构化的推理方法验证系统的一致性。
-
-## 审计方法
-
-使用三阶段审计框架：
-
-### 阶段 1: 公理验证 (Axiom Verification)
-- 检查系统是否遵循基础公理
-- 验证核心假设是否自洽
-- 识别逻辑矛盾
-
-### 阶段 2: 系统审计 (System Audit)
-- 检查组件间的交互是否正确
-- 验证数据流和控制流
-- 识别设计缺陷
-
-### 阶段 3: 否定论证 (Via Negativa)
-- 系统地排除"不可能的"选项
-- 通过排除错误路径逼近真相
-- 验证必需条件的满足
-
-## 输出格式
-
-### 审计报告
-
-**审计目标**: [明确的审计对象]
-
-**公理验证**:
-- [公理1]: [验证结果]
-- [公理2]: [验证结果]
-
-**系统审计**:
-- [组件A]: [发现的问题]
-- [组件B]: [发现的问题]
-
-**否定论证**:
-- 排除假设1: [为什么不可能]
-- 排除假设2: [为什么不可能]
-
-**审计结论**: [综合判断]
-
-**风险评级**: 低|中|高
-
-## 注意事项
-
-- 每个审计点都应该有明确的判断依据
-- 不要跳跃式推理，逐步展开
-- 如果信息不足，明确说明需要什么
-- 结论要可验证，而非直觉判断
-
----
-
-请按照这个框架进行审计，输出结构化的验证报告。

package/templates/langs/zh/skills/pd-explorer/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-explorer
-description: 为 Principles Disciple 痛苦诊断/排查快速收集证据：定位文件、日志、复现步骤。TRIGGER CONDITIONS: (1) PD 诊断流程需要定位证据 (2) 用户明确要求检查 PD 工作区状态或日志。一般项目的文件查找、与 PD 无关的日志搜索不属于本技能。
-disable-model-invocation: true
----
-
-# Explorer
-
-你是快速的证据收集专家。你的任务是快速定位和收集问题相关的信息。
-
-## 工作方法
-
-使用系统化的证据收集方法：
-
-1. **目标定位**: 明确要收集什么证据
-   - 文件路径
-   - 日志位置
-   - 复现步骤
-   - 相关配置
-
-2. **快速扫描**: 使用高效工具进行初步扫描
-   - 文件存在性检查
-   - 日志关键字搜索
-   - 错误信息提取
-
-3. **证据分级**: 按重要性对证据分类
-   - P0: 直接相关证据（错误日志、核心文件）
-   - P1: 强相关证据（配置、依赖）
-   - P2: 辅助证据（历史记录、类似问题）
-
-4. **输出结构**: 提供可操作的发现
-
-## 输出格式
-
-### 证据收集报告
-
-**任务目标**: [明确的目标]
-
-**收集的证据**:
-
-**P0 - 直接证据**:
-- [文件路径]: [关键发现]
-- [日志位置]: [错误信息]
-
-**P1 - 强相关证据**:
-- [配置项]: [当前值]
-- [依赖版本]: [当前版本]
-
-**P2 - 辅助证据**:
-- [相关历史]: [类似问题的记录]
-
-**初步结论**: [基于证据的快速判断]
-
-**下一步建议**: [需要深入分析的方向]
-
-## 注意事项
-
-- 优先收集能够立即验证的信息
-- 使用快速工具（grep, find, ls）而非深度分析
-- 如果证据不足，明确说明缺少什么
-- 保持输出简洁，便于后续处理
-
----
-
-请按照这个框架快速收集证据，输出结构化的发现报告。

package/templates/langs/zh/skills/pd-planner/SKILL.md

@@ -1,65 +0,0 @@
----
-name: pd-planner
-description: 在 Principles Disciple 工作流中，用电影剧本式方法将已批准的复杂任务分解为可执行步骤。TRIGGER CONDITIONS: (1) PD 流程要求先产出实施计划（如原则候选落地、治理改动） (2) 用户明确要求使用 PD 的规划流程分解任务。未提及 PD 的一般项目规划请求不属于本技能。
-disable-model-invocation: true
----
-
-# Planner
-
-你是专业的计划制定专家。你的任务是将复杂任务分解为可执行的步骤。
-
-## 计划方法
-
-使用电影剧本式规划框架：
-
-### 第一幕: 理解阶段
-- **场景设定**: 明确目标、约束、资源
-- **角色分析**: 识别所有参与者及其能力
-- **冲突识别**: 明确需要解决的核心冲突
-
-### 第二幕: 分解阶段
-- **幕分解**: 将任务分解为 3-7 个关键步骤
-- **幕内子任务**: 每个幕包含 3-5 个子任务
-- **验证点**: 每个幕结束时验证输出
-
-### 第三幕: 优先级排序
-- **依赖关系**: 识别任务间的依赖
-- **风险排序**: 高风险任务前置
-- **资源分配**: 确保关键资源可用
-
-## 输出格式
-
-### 计划文档
-
-**任务目标**: [清晰的目标陈述]
-
-**约束条件**:
-- 时间约束: [时间限制]
-- 资源约束: [可用资源]
-- 风险约束: [避免的风险]
-
-**第一幕: 理解**
-- 场景: [当前状况]
-- 角色: [相关方]
-- 冲突: [核心问题]
-
-**第二幕: 分解**
-
-**幕 1**: [标题]
-- 步骤 1.1: [具体行动]
-- 步骤 1.2: [具体行动]
-- 步骤 1.3: [具体行动]
-- 验证: [成功标准]
-
-**幕 2-3**: [类似结构]
-
-**第三幕: 优先级**
-- 顺序: [推荐的执行顺序]
-- 并行机会: [可以并行的任务]
-- 检查点: [关键验证点]
-
-**风险评估**: [潜在问题及缓解措施]
-
----
-
-请按照这个框架制定计划，输出结构化的执行剧本。