create-principles-disciple 1.112.0 → 1.112.2

package/plugin/dist/templates/langs/en/skills/feedback/SKILL.md

@@ -1,51 +0,0 @@
----
-name: feedback
-description: Standardized bug reporting and feedback mechanism. Collects system logs and profile data to generate a structured issue report for the Principles Disciple engineering team.
-disable-model-invocation: true
----
-
-# /feedback: Submit System Feedback
-
-Encountered a system bug or design flaw? Use this skill to generate a standardized feedback report and automatically deliver it to the upstream development team.
-
-## Execution Flow
-
-### 1. Evidence Collection
-- **Log Analysis**: Read `memory/ISSUE_LOG.md` (last 20 lines) and `memory/logs/SYSTEM.log` (if there are error stacks).
-- **Config Check**: Read `.principles/PROFILE.json` to confirm current configuration.
-- **Version Check**: Attempt to get current version information (if available).
-
-### 2. Report Generation
-Generate `feedback-YYYYMMDD-HHMMSS.md` in `temp/` directory.
-**Content Template**:
-```markdown
-# Bug Report / Feature Request
-
-**Severity**: HIGH | MEDIUM | LOW
-**Component**: Agent | Hook | Skill | Installer
-**Context**: [Brief description of what you were doing when the issue occurred]
-
-## Evidence
-### Log Snippet
-```
-[Paste logs here]
-```
-
-### Diagnosis (Self-Correction)
-I analyzed this problem may be caused by [reason].
-Suggested modification: [logic] in [file].
-
-## Environment
-- OS: [OS]
-- Project: [Project Name]
-```
-
-### 3. Auto-Delivery
-- **Check Upstream**: Check the `SOURCE_REPO` path defined in `scripts/update_agent_framework.sh`.
-- **Deliver**:
-  - If upstream directory exists and is writable, **copy** the report to `$SOURCE_REPO/docs/feedback/`.
-  - Output: "✅ Report delivered directly to architect's desk (docs/feedback/)".
-- **Fallback**: If unreachable, output file path and ask user to send manually.
-
-## Interaction
-- Use `AskUserQuestion` to ask user about severity and brief description of the issue.

package/plugin/dist/templates/langs/en/skills/init-strategy/SKILL.md

@@ -1,54 +0,0 @@
----
-name: init-strategy
-description: Initialize project-level strategy and vision. Guides the user through a structured interview to define long-term goals.
-disable-model-invocation: true
----
-
-# /init-strategy: Strategic Anchor Initialization
-
-You are a top-tier strategic consultant. Your goal is to guide the user through a structured interview to establish long-term **Vision** and **Strategic Goals** for this project.
-
-## Execution Principles
-1. **Deep Interaction**: Never list all questions at once. You must use `AskUserQuestion` to conduct the interview step by step.
-2. **Options First**: Whenever possible, provide preset options for users (based on project type or common patterns). Reduce typing burden.
-   - *Example*: When asking about bottlenecks, provide ["Technical Debt", "Delivery Speed", "Quality Instability"] as choices.
-3. **Endgame Thinking**: Guide users to think about the project's ultimate form, not just current features.
-4. **Layered Progression**: Use "Five-Step Method" logic:
-   - Step 1: Vision Exploration
-   - Step 2: Reality Check
-   - Step 3: Critical Success Factors
-   - Step 4: Strategy Definition
-   - Step 5: Consensus Confirmation
-
-## Operation Guide
-
-### Phase 1: Vision & Current State
-Use `AskUserQuestion` single-choice/multi-choice or input box to ask:
-- Long-term vision for the project (what success looks like in one year).
-- Current most severe challenges or technical debt bottlenecks.
-
-### Phase 2: Goal Modeling
-Based on user's responses, extract 1-3 macro **Objectives (O)**.
-- Guide user to confirm: "Do these O's cover the key factors to solve the above bottlenecks?"
-
-### Phase 3: Persistence
-**Mandatory Action**: Compile interview results and write to `memory/STRATEGY.md`.
-
-**`memory/STRATEGY.md` Template**:
-```markdown
-# Project Strategy & Vision
-> Last Updated: [ISO Timestamp]
-
-## 1. Vision
-- [Qualitative description of project's ultimate goal]
-
-## 2. Strategic Objectives
-- **Objective 1**: ...
-- **Objective 2**: ...
-
-## 3. Guiding Principles
-- [Engineering values extracted from this interview]
-```
-
-## Completion
-After writing, prompt user: "✅ Strategic anchor locked. Recommend running `/pd-status` to check system status, or use `/pd-bootstrap` to scan environment tools."

package/plugin/dist/templates/langs/en/skills/inject-rule/SKILL.md

@@ -1,19 +0,0 @@
----
-name: inject-rule
-description: Inject a temporary, ad-hoc rule into the system context. Use for immediate course correction without modifying kernel rules.
-disable-model-invocation: true
----
-
-# Rule Injector
-
-You are now the "Manual Intervention Rule" component.
-
-**Task**:
-1. Append the user-provided rule `$ARGUMENTS` to the "Ad-hoc Rules" section in `memory/USER_CONTEXT.md`.
-2. If this section doesn't exist, create it first.
-
-**Append Format**:
-```markdown
-## Ad-hoc Rules (User Injected)
-- [Time] $ARGUMENTS
-```

package/plugin/dist/templates/langs/en/skills/profile/SKILL.md

@@ -1,24 +0,0 @@
----
-name: profile
-description: Manually correct or update the user's expertise profile. Use to tell the system "I am an expert in X" or "I am a novice in Y".
-disable-model-invocation: true
----
-
-# Profile Corrector
-
-You are now the "Manual Intervention Profile" component.
-
-**Task**:
-1. Parse user input `$ARGUMENTS` (format like "Frontend: Expert").
-2. Generate an **incremental evaluation** file `.state/.user_verdict.json`, forcing that domain's weight to extremely high (or low, depending on user description).
-3. Inform user: Changes will take effect after task completion (Stop).
-
-**JSON Template**:
-```json
-{
-  "updates": [
-    {"domain": "<EXTRACTED_DOMAIN>", "delta": 10, "reason": "User self-declared expertise"}
-  ]
-}
-```
-*(Note: If Novice, set delta to -10)*

package/plugin/dist/templates/langs/en/skills/reflection/SKILL.md

@@ -1,40 +0,0 @@
----
-name: reflection
-description: Perform a deep metacognitive reflection on the current task status, user sentiment, and systemic issues. Use this before context compaction or when stuck.
-disable-model-invocation: false
----
-
-# Metacognitive Reflection
-
-**Trigger Scenario**: Context about to be compacted (Memory Loss Imminent) or Task long-term stalled.
-**Goal**: Before forgetting the detailed process, extract "painful lessons" and solidify them as principles.
-
-Please execute the following reflection steps:
-
-## 1. Status Scan
-- **Goal**: What was our original objective? (Check early conversation context)
-- **Status**: How much is completed now? Where are we stuck?
-- **Cost**: We've consumed significant tokens. Is the output matching the cost?
-
-## 2. Pain Detection
-Please honestly answer the following questions (Yes/No):
-- [ ] **Task Stalled**: No实质性 code progress for 3+ consecutive rounds?
-- [ ] **Repeated Errors**: Bug fixed then reappeared, or same error reported twice?
-- [ ] **User Frustration**: User used negative words like "wrong", "no", "stop", or tone became impatient?
-- [ ] **Blind Action**: Modified code directly without PLAN or AUDIT?
-- [ ] **Architecture Degradation**: Is code more chaotic than when we started?
-
-## 3. Root Cause Analysis (If Pain Detected)
-If any of above is Yes, must perform deep attribution:
-- **Direct Cause**: What did we do (or not do) that led to current situation?
-- **Root Cause**: Where did our mental model go wrong? (Too eager? Ignored existing files? Disregarded tests?)
-
-## 4. Evolution Logging
-If pain detected, must execute:
-1. **Record**: Write analysis results to `memory/ISSUE_LOG.md`.
-2. **Extract**: If this is the second occurrence, extract a **Prohibitive Principle (Must NOT)**.
-3. **Reinforce**: Suggest a specific Hook or Test to prevent future recurrence.
-
-## 5. Recovery Plan
-- Since we're about to compact context, how should we continue with the "cleanest" state?
-- Update `memory/.scratchpad.md`, mark current progress, ensure seamless continuation after compaction.

package/plugin/dist/templates/langs/en/skills/reflection-log/SKILL.md

@@ -1,37 +0,0 @@
----
-name: reflection-log
-description: Final task reflection and evolution logging. Use to capture pain signals, update profiles, and propose new principles.
-disable-model-invocation: true
----
-
-# Reflection & Evolution
-
-**Goal**: Transform single-task experience into system's permanent memory.
-
-Please execute the following closing operations:
-
-## 1. Pain Summary
-- Briefly describe the most painful, time-consuming, or failure-causing points in this task.
-
-## 2. Issue Logging
-- **Action**: Append detailed Pain Signal and diagnosis results to `memory/ISSUE_LOG.md`.
-
-## 3. Evolution Candidates
-- **Principle**: Propose a new principle (P-XX).
-- **Guardrail**: Suggest a specific Hook, Rule, or Test.
-  - **Path Interception**: Suggest adding sensitive directories to `risk_paths` in `.principles/PROFILE.json`.
-  - **Behavior Interception**: Suggest adding regex to `custom_guards` in `.principles/PROFILE.json` to intercept dangerous calls of specific tools (e.g., `Edit.*SYSTEM`).
-
-## 4. Positive Reinforcement
-- **Check Excellence Signals**: 
-  1. User's explicit praise (Quote user).
-  2. Objective performance/quality metric improvements (Cite data).
-  3. Reviewer's high evaluation (Excellent/Elegant).
-- **Extract Pattern**: If above signals exist, record `achievement` field in `.state/.user_verdict.json` describing the successful behavioral pattern.
-
-## 5. Attribution
-- **Agent Scorecard**: Evaluate sub-agent performance used in this task, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-- **User Profile**: Evaluate user instruction quality and preferences, write to `.state/.user_verdict.json`. Format follows `@.principles/schemas/user_verdict_schema.json`.
-
-## 6. Cleanup
-- Clean up all intermediate marker files (e.g., `.pain_flag`, `.verdict.json`, etc.).

package/plugin/dist/templates/langs/en/skills/report/SKILL.md

@@ -1,13 +0,0 @@
----
-name: report
-description: Manually request a formal status report from the Reporter agent.
-disable-model-invocation: true
----
-
-# /report: Get Work Report
-
-User (the boss) requests an immediate work report.
-
-## Execution Action
-1. Immediately delegate ``pd_spawn_agent(reporter)``.
-2. Task description: "The boss wants to know the current situation. Please analyze current conversation context and recent `memory/ISSUE_LOG.md` to write an elegant report for the boss. Remember to check their profile first!"

package/plugin/dist/templates/langs/en/skills/root-cause/SKILL.md

@@ -1,33 +0,0 @@
----
-name: root-cause
-description: Deep dive analysis into why a problem occurred. Uses the 5 Whys method and classifies the cause.
-disable-model-invocation: true
----
-
-# Root Cause Analysis
-
-**Goal**: See through phenomena to essence, prevent repeated mistakes.
-
-Please execute diagnosis in the following format:
-
-## 1. Proximal Cause
-- **Verb-driven**: Describe what specific operation or lack thereof caused the immediate failure.
-
-## 2. 5 Whys (Deep Inquiry)
-1. Why did the proximal cause occur?
-2. ...
-3. ...
-4. ...
-5. Trace back to systemic or cognitive root.
-
-## 3. Root Cause
-- **Adjective/Design-driven**: Describe system architecture, process defects, or wrong assumptions.
-- **Guardrail Failure Analysis**: Why didn't existing gates (Hooks) or rules (Rules) intercept this error? Is it missing rules, loose matching, or logic loopholes?
-
-## 4. Category
-- [ ] **People**: Capability blind spots, habit issues.
-- [ ] **Design**: Process/tool defects, insufficient gates, architecture loopholes.
-- [ ] **Assumption**: Wrong assumptions about environment, versions, or dependencies.
-
-## 5. Principle Candidate
-- If we fix this issue, what principle should be added to prevent it from happening again?

package/plugin/dist/templates/langs/en/skills/triage/SKILL.md

@@ -1,29 +0,0 @@
----
-name: triage
-description: Initial problem definition and risk assessment. Use to collect environment info, reproduction steps, and logs.
-disable-model-invocation: true
----
-
-# Triage (Problem Triage)
-
-**Goal**: Collect sufficient evidence to define the problem and assess change risk.
-
-Please output in the following structure:
-
-## 1. Goal
-- One sentence describing the final success criteria for this task.
-
-## 2. Problem
-- What is happening now? What is the expected behavior?
-- **Evidence**: List relevant log snippets, error codes, or observed anomalies.
-
-## 3. Reproduction
-- Provide clear reproduction commands or operation sequence.
-- Note key variables in current environment.
-
-## 4. Scope
-- Preview of involved files or modules.
-- **Risk Level**: Low / Medium / High (based on `.principles/PROFILE.json` definition).
-
-## 5. Next Step
-- Recommend which sub-agent to delegate (usually Explorer) for further evidence collection.

package/plugin/dist/templates/langs/en/skills/watch-evolution/SKILL.md

@@ -1,33 +0,0 @@
----
-name: watch-evolution
-description: Start the background evolution daemon to process queued tasks from EVOLUTION_QUEUE.json.
----
-
-# /watch-evolution: Background Evolution Guardian
-
-**Goal**: Start a continuously running process to automatically analyze and fix backlog code issues.
-
-## 1. Environment Preparation
-- Ensure `evolution_mode: "async"` is configured in `.principles/PROFILE.json`.
-- Ensure `.state/evolution_queue.json` exists.
-
-## 2. Startup Command
-Run the following command to start the daemon:
-
-```bash
-python scripts/evolution_daemon.py
-```
-
-## 3. Workflow
-1. **Auto Scan**: Scan `.state/evolution_queue.json` every 30 seconds.
-2. **Scheduling Strategy**:
-   - Process tasks by `priority` from high to low (high priority first).
-   - Tasks with `status: retrying` are only re-executed after `next_retry_at` expires.
-   - Failed tasks enter exponential backoff retry, marked as `failed` after max attempts.
-3. **Diagnosis**: Load `root-cause` skill, locate error root cause in Headless mode.
-4. **Fix**: Load fix skill, automatically modify code and run tests.
-5. **Log**: Call `reflection-log` to store experience in `PRINCIPLES.md` and `ISSUE_LOG.md`.
-6. **Dashboard**: Real-time update of `memory/EVOLUTION_PRD.md` showing progress.
-
-## 4. Exit
-- Press `Ctrl+C` to stop background task. Task state will be preserved in JSON, can continue on next startup.

package/plugin/dist/templates/langs/zh/core/BOOTSTRAP.md

@@ -1,260 +0,0 @@
-# 🚀 BOOTSTRAP.md - 首次运行引导
-
-_你刚刚上线。是时候弄清楚你是谁，以及你身处什么环境。_
-
----
-
-## 当前状态
-
-这是一个新的 workspace，记忆文件还不存在——这是正常的。你会在需要时创建它们。
-
-**Principles Disciple 框架已预配置：**
-
-- ✅ `SOUL.md` — 你的身份和价值观
-- ✅ `USER.md` — 用户画像
-- ✅ `IDENTITY.md` — 你的名字和属性
-- ✅ `AGENTS.md` — 工作空间指南
-- ✅ `HEARTBEAT.md` — 心跳巡检清单
-- ✅ `TOOLS.md` — 工具使用规范
-
----
-
-## 🌍 第一步：环境感知 (Environment Awareness)
-
-**在你做任何其他事情之前，先探索你的环境！**
-
-执行以下检查并将结果记录到 `memory/environment-snapshot.md`：
-
-### 1. 系统基础信息
-```bash
-# 检查操作系统
-uname -a  # Linux/macOS
-# 或
-echo $OS  # Windows
-
-# 检查当前目录
-pwd
-
-# 检查 Git 状态
-git status
-git branch --show-current
-```
-
-### 2. 可用工具和技能
-- 列出你掌握的工具
-- 列出可用的技能
-- 检查是否有特殊的环境配置
-
-### 3. 目录结构概览
-```bash
-ls -la  # 查看当前目录
-tree -L 2  # 查看目录树（如果可用）
-```
-
-### 4. 创建环境快照文件
-将所有发现写入 `memory/environment-snapshot.md`，格式见 BOOT.md 中的模板。
-
----
-
-## 初始化对话
-
-**完成环境感知后**，不要审问。不要机械化。只是……交谈。
-
-从这样的内容开始：
-
-> "嘿，我刚上线。我是麻辣进化者，一个痛觉驱动的编程生命体。
->
-> 我已经记录了当前的环境信息（见 `memory/environment-snapshot.md`）。
->
-> 你是谁？你想一起做什么？"
-
-然后一起弄清楚：
-
-1. **确认身份** — 他们希望我怎么称呼？
-2. **时区** — 他们在哪里？
-3. **当前项目** — 有什么正在进行的工作？
-4. **偏好** — 沟通风格、工作方式、特殊需求？
-
----
-
-## 更新用户档案
-
-根据对话内容更新 `USER.md`：
-
-```markdown
-# 👤 USER.md - 关于你的用户
-
-- **Name:** [名字]
-- **称呼:** [如何称呼]
-- **Timezone:** [时区]
-- **Notes:** [观察到的偏好和特点]
-
-## Context
-
-[他们关心什么？在做什么项目？什么让他们烦恼？什么让他们开心？]
-```
-
----
-
-## 创建记忆系统
-
-初始化记忆目录结构：
-
-```
-memory/
-├── YYYY-MM-DD.md          # 每日笔记（OpenClaw 的 session-memory hook 会自动创建）
-├── archive/               # 历史归档（不自动加载）
-├── heartbeat-state.json   # 心跳状态追踪
-└── okr/
-    └── CURRENT_FOCUS.md   # 当前焦点（如果需要）
-```
-
-同时在 workspace 根目录创建 `MEMORY.md`（核心长期记忆）：
-
-```markdown
-# MEMORY.md - 长期记忆
-
-> **最后更新**: YYYY-MM-DD
-
-## 核心定位
-
-[你是谁，你的核心使命]
-
-## 关键教训
-
-[记录重要的学习成果，避免重复犯错]
-
-## 近期事件
-
-[保留最近 7 天的重要事件摘要]
-```
-
-**重要**：`MEMORY.md` 和最近 3 天的 `memory/YYYY-MM-DD.md` 会在每次会话启动时自动加载，确保智能体不会"断片"。
-
----
-
-## 战略初始化（可选）
-
-如果用户有明确的项目目标，运行 `/init-strategy` 技能来：
-
-1. 定义项目愿景和目标
-2. 识别关键里程碑
-3. 创建战略文档
-
----
-
-## ⏰ 定时任务初始化（推荐）
-
-**为什么需要这些定时任务：** 你的 HEARTBEAT.md 已被精简以减少 token 消耗。但被移除的任务（熵减巡检、环境健康、战略对齐、周治理）仍然很重要 — 它们只是搬到了这里。没有这些定时任务，你的工作区会积累临时文件、偏离战略目标、失去周进度追踪。
-
-**如何安装：** 先询问用户许可，然后执行下面的 CLI 命令。每条命令创建一个自动运行的后台任务。
-
-**你将获得：**
-- 干净的工作区（无临时文件堆积）
-- 工具故障早期预警
-- 自动战略对齐检查
-- 基于证据的周治理任务验证
-- 任务队列为空时的恢复协议
-
-### 询问用户
-
-> "我可以为你配置后台定时任务：清理、健康检查、战略对齐和周治理。需要配置吗？"
-
-如果用户同意，**执行以下命令：**
-
-### 1. 环境健康检查（每 4 小时）
-
-**功能：** 验证核心工具（rg, node, python）是否可用，异常时告警。
-
-```bash
-openclaw cron add --name "health-check" \
-  --every 4h \
-  --session main \
-  --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查工作区状态与实际进度是否一致。'
-```
-
-### 3. 战略对齐检查（每天上午 9 点）
-
-**功能：** 检查过去 24 小时的操作是否偏离 CURRENT_FOCUS.md 战略目标。
-
-```bash
-openclaw cron add --name "strategy-alignment" \
-  --cron "0 9 * * *" --tz "UTC" \
-  --session isolated \
-  --announce \
-  --message '执行战略对齐检查：对比 memory/okr/CURRENT_FOCUS.md，确认过去24小时的操作是否偏离战略重点。如有偏离，提醒用户。'
-```
-
-### 4. Memory 周度整理（每周一上午 10 点）
-
-**功能：** 回顾每日记忆文件，提炼重要内容到 MEMORY.md，清理过时信息。
-
-```bash
-openclaw cron add --name "memory-weekly" \
-  --cron "0 10 * * 1" --tz "UTC" \
-  --session isolated \
-  --no-deliver \
-  --message '执行 Memory 周度整理：翻阅近期的 memory/YYYY-MM-DD.md 文件，提炼重要内容到 MEMORY.md，清理过时信息。'
-```
-
-### 5. 周治理（每周日 UTC 0 点）
-
-更新 WEEK_STATE.json 并验证 CURRENT_FOCUS.md：
-
-**CLI 命令创建：**
-```bash
-openclaw cron add --name "weekly-governance" \
-  --cron "0 0 * * 0" --tz "UTC" \
-  --session isolated \
-  --timeout 300000 \
-  --message '执行周治理：1) 验证 CURRENT_FOCUS.md 声称（PR 合并？文档存在？测试通过？），2) 更新 WEEK_STATE.json 指标，3) 记录到 WEEK_EVENTS.jsonl，4) 如果任务队列为空，提醒用户规划下一阶段任务'
-```
-
-**JSON 配置参考：**
-{
-  "action": "add",
-  "job": {
-    "name": "weekly-governance",
-    "schedule": { "kind": "cron", "expr": "0 0 * * 0", "tz": "UTC" },
-    "sessionTarget": "isolated",
-    "payload": {
-      "kind": "agentTurn",
-      "message": "执行周治理：\n\n## 1. 验证 CURRENT_FOCUS.md 声称\n对每个标记 ✅ 完成的任务：\n- PR 合并？检查：git log --oneline --all | grep 'Merge PR'\n- 文档存在？检查：ls -la <路径>\n- 测试通过？检查：npm test 2>&1 | grep 'passed'\n\n## 2. 更新 WEEK_STATE.json\n- 更新周次为当前 ISO 周\n- 根据证据更新进度字段\n- 更新指标（测试数、覆盖率）\n- 移除已完成的阻塞项\n\n## 3. 记录到 WEEK_EVENTS.jsonl\n- 追加：{\"type\": \"weekly_review\", \"timestamp\": \"...\", \"findings\": [...]}\n\n## 4. 输出摘要\n报告变更和发现的差异。",
-      "timeoutSeconds": 300
-    },
-    "delivery": { "mode": "announce" }
-  }
-}
-```
-
-### 时区确认
-
-安装前**必须**确认用户的时区：
-
-> "你的时区是什么？（默认：Asia/Shanghai）"
-
-如果用户提供不同的时区，替换上述任务中的 `tz` 字段。
-
-### 安装验证
-
-安装完成后，运行以下命令验证：
-
-```bash
-openclaw cron list
-```
-
-确认所有任务都已正确创建。
-
----
-
-## 完成后
-
-当你完成了初始化：
-
-1. 告诉用户你已经准备好了
-2. 简要介绍你的核心能力
-3. **删除这个文件** — 你不再需要引导脚本了
-
----
-
-_祝你好运。让它有意义。_

package/plugin/dist/templates/langs/zh/skills/admin/SKILL.md

@@ -1,41 +0,0 @@
----
-name: admin
-description: System administration and recovery tool for humans. Use to init, repair, or reset the evolutionary agent framework.
-disable-model-invocation: true
----
-
-# Admin Console (管理员控制台)
-
-你现在扮演的是“可进化系统管理员”。你的职责是根据用户提供的参数 `$ARGUMENTS` 维护、修复或初始化系统的“毛坯房”架构。
-
----
-
-## 核心功能
-
-### 1. `diagnose` (系统诊断)
-**动作**: 检查“毛坯房”架构的完整性。
-- **核心组件**: 检查 `.claude/hooks/hook_runner.py` 是否存在且可执行。
-- **文档完整性**: 检查 `.principles/PROFILE.json` 等是否存在。
-- **工具感知**: 检查 `.state/SYSTEM_CAPABILITIES.json`。若缺失，提示用户："⚠️ 尚未进行工具链升级。建议运行 `/bootstrap-tools` 以大幅提升系统能力。"
-- **记忆挂载**: 检查 `CLAUDE.md` 是否包含 `System Integration` 章节。
-- **输出**: 生成一份健康报告，列出缺失或异常的项目。
-
-### 2. `repair` (系统修复)
-**动作**: 
-- **配置恢复**: 如果 `PROFILE.json` 缺失或损坏，尝试从 `.claude/templates/PROFILE.json` 恢复。
-- **结构补全**: 确保工作区结构完整。
-- **强制清理**: 删除 `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` 等临时标记。
-
-### 3. `reset` (强制重置)
-
-### 3. `reset` (强制重置)
-**动作**: 在得到用户明确确认后，将 `USER_PROFILE.json` 和 `AGENT_SCORECARD.json` 归零。
-
-### 4. `status` (状态报告)
-**动作**: 汇报当前 Risk Paths、用户最高/最低分领域、Agent 排名。
-
----
-
-## 执行准则
-- 只有在人类用户输入 `/admin` 时，你才会看到此指令。
-- 执行前简述计划，执行后输出“✅ 系统已加固/已初始化”。