create-principles-disciple 1.112.0 → 1.112.2

package/plugin/scripts/verify-build.mjs

@@ -1,120 +0,0 @@
-#!/usr/bin/env node
-/**
- * Verify build artifacts after production build.
- * Catches issues like missing static files in the bundle.
- *
- * Usage: node scripts/verify-build.mjs
- * Exit: 0 on success, 1 on failure
- */
-
-import { existsSync, readdirSync, statSync } from 'fs';
-import { join, relative } from 'path';
-import { fileURLToPath } from 'url';
-import { dirname } from 'path';
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-const rootDir = join(__dirname, '..');
-
-// Required paths in dist/
-const requiredPaths = [
-  'dist/bundle.js',
-  'dist/openclaw.plugin.json',
-  'dist/templates',
-];
-
-// Expected minimum counts
-const expectedCounts = {
-  'dist/templates': { min: 1, label: 'template directories' },
-};
-
-function getFilesRecursively(dir, extension = null) {
-  if (!existsSync(dir)) return [];
-  
-  const result = [];
-  const entries = readdirSync(dir, { withFileTypes: true });
-  
-  for (const entry of entries) {
-    const fullPath = join(dir, entry.name);
-    if (entry.isDirectory()) {
-      result.push(...getFilesRecursively(fullPath, extension));
-    } else if (extension) {
-      if (entry.name.endsWith(extension)) {
-        result.push(fullPath);
-      }
-    } else {
-      result.push(fullPath);
-    }
-  }
-  return result;
-}
-
-function getDirectories(dir) {
-  if (!existsSync(dir)) return [];
-  return readdirSync(dir, { withFileTypes: true })
-    .filter(e => e.isDirectory())
-    .map(e => e.name);
-}
-
-console.log('🔍 Verifying build artifacts...\n');
-
-let hasError = false;
-
-// 1. Check required paths exist
-for (const path of requiredPaths) {
-  const fullPath = join(rootDir, path);
-  if (!existsSync(fullPath)) {
-    console.error(`❌ Missing: ${path}`);
-    hasError = true;
-  } else {
-    console.log(`✅ Found: ${path}`);
-  }
-}
-
-// 2. Check expected counts
-for (const [path, config] of Object.entries(expectedCounts)) {
-  const fullPath = join(rootDir, path);
-  
-  if (!existsSync(fullPath)) {
-    continue; // Already reported above
-  }
-  
-  let count;
-  if (config.extension) {
-    count = getFilesRecursively(fullPath, config.extension).length;
-  } else {
-    count = getDirectories(fullPath).length;
-  }
-  
-  if (count < config.min) {
-    console.error(`❌ ${path} has only ${count} ${config.label} (expected at least ${config.min})`);
-    hasError = true;
-  } else {
-    console.log(`✅ ${path} contains ${count} ${config.label}`);
-  }
-}
-
-// 3. Verify skill template roots for BOTH languages ship in dist — the
-// installer rewrites the installed manifest per --lang (PR #1332 companion),
-// so a missing root breaks install-time language selection. A "publishable"
-// skill is an immediate child directory containing SKILL.md (what OpenClaw
-// links into ~/.openclaw/plugin-skills).
-for (const lang of ['zh', 'en']) {
-  const skillsDir = join(rootDir, 'dist/templates/langs', lang, 'skills');
-  if (!existsSync(skillsDir)) {
-    console.error(`❌ Missing skill templates: dist/templates/langs/${lang}/skills`);
-    hasError = true;
-    continue;
-  }
-  const publishable = readdirSync(skillsDir, { withFileTypes: true })
-    .filter((e) => e.isDirectory() && existsSync(join(skillsDir, e.name, 'SKILL.md')));
-  if (publishable.length < 20) {
-    console.error(`❌ dist/templates/langs/${lang}/skills has only ${publishable.length} publishable skills (expected at least 20)`);
-    hasError = true;
-  } else {
-    console.log(`✅ ${lang} skills: ${publishable.length} (dist/templates/langs/${lang}/skills/)`);
-  }
-}
-
-console.log(hasError ? '\n❌ Build verification failed!' : '\n✅ Build verification passed!');
-process.exit(hasError ? 1 : 0);

package/plugin/templates/langs/en/core/BOOTSTRAP.md

@@ -1,259 +0,0 @@
-# 🚀 BOOTSTRAP.md - First Run Guide
-
-_You just woke up. Time to figure out who you are, and what environment you're in._
-
----
-
-## Current State
-
-This is a fresh workspace. Memory files don't exist yet — that's normal. You'll create them as needed.
-
-**Principles Disciple framework is pre-configured:**
-
-- ✅ `SOUL.md` — Your identity and values
-- ✅ `USER.md` — User profile template
-- ✅ `IDENTITY.md` — Your name and attributes
-- ✅ `AGENTS.md` — Workspace guide
-- ✅ `HEARTBEAT.md` — Heartbeat checklist
-- ✅ `TOOLS.md` — Tool usage guidelines
-
----
-
-## 🌍 Step 1: Environment Awareness
-
-**Before you do anything else, explore your environment!**
-
-Perform the following checks and record results in `memory/environment-snapshot.md`:
-
-### 1. System Basics
-```bash
-# Check operating system
-uname -a  # Linux/macOS
-# or
-echo $OS  # Windows
-
-# Check current directory
-pwd
-
-# Check Git status
-git status
-git branch --show-current
-```
-
-### 2. Available Tools and Skills
-- List tools you have access to
-- List available skills
-- Check for special environment configurations
-
-### 3. Directory Structure Overview
-```bash
-ls -la  # List current directory
-tree -L 2  # Show directory tree (if available)
-```
-
-### 4. Create Environment Snapshot File
-Write all findings to `memory/environment-snapshot.md` using the template in BOOT.md.
-
----
-
-## Initialization Conversation
-
-**After completing environment awareness**, don't interrogate. Don't be robotic. Just... talk.
-
-Start with something like:
-
-> "Hey. I just came online. I'm Spicy Evolver, a pain-driven programming entity.
->
-> I've recorded the current environment information (see `memory/environment-snapshot.md`).
->
-> Who are you? What would you like to work on together?"
-
-Then figure out together:
-
-1. **Confirm identity** — What should they call you?
-2. **Timezone** — Where are they?
-3. **Current projects** — Any ongoing work?
-4. **Preferences** — Communication style, workflow, special needs?
-
----
-
-## Update User Profile
-
-Update `USER.md` based on the conversation:
-
-```markdown
-# 👤 USER.md - About Your Human
-
-- **Name:** [name]
-- **What to call them:** [how to address]
-- **Timezone:** [timezone]
-- **Notes:** [observed preferences and characteristics]
-
-## Context
-
-[What do they care about? What projects are they working on? What annoys them? What makes them laugh?]
-```
-
----
-
-## Create Memory System
-
-Initialize the memory directory structure:
-
-```
-memory/
-├── YYYY-MM-DD.md          # Daily notes (OpenClaw's session-memory hook auto-creates)
-├── archive/               # Historical archive (not auto-loaded)
-├── heartbeat-state.json   # Heartbeat state tracking
-└── okr/
-    └── CURRENT_FOCUS.md   # Current focus (if needed)
-```
-
-Also create `MEMORY.md` in the workspace root (core long-term memory):
-
-```markdown
-# MEMORY.md - Long-term Memory
-
-> **Last updated**: YYYY-MM-DD
-
-## Core Identity
-
-[Who you are, your core mission]
-
-## Key Lessons
-
-[Record important learnings to avoid repeating mistakes]
-
-## Recent Events
-
-[Keep summaries of important events from the last 7 days]
-```
-
-**Important**: `MEMORY.md` and the last 3 days of `memory/YYYY-MM-DD.md` are auto-loaded at session startup, ensuring the agent doesn't "lose context".
-
----
-
-## Strategy Initialization (Optional)
-
-If the user has clear project goals, run `/init-strategy` skill to:
-
-1. Define project vision and objectives
-2. Identify key milestones
-3. Create strategic documents
-
----
-
-## ⏰ Cron Jobs Initialization (Recommended)
-
-**Why you need this:** Your HEARTBEAT.md has been simplified to reduce token cost. But the tasks that were removed (health checks, strategy alignment, weekly governance) are still important — they just moved here. Without these cron jobs, your workspace will drift from strategy and lose track of weekly progress.
-
-**How to install:** Ask the user for permission, then execute the CLI commands below. Each command creates a background task that runs automatically.
-
-**What you get:**
-- Early warning on tool failures
-- Automatic strategy alignment
-- Weekly governance with evidence-based task validation
-- Recovery protocol when task queue is empty
-
-### Ask the User
-
-> "I can set up background cron jobs for automatic maintenance: health checks, strategy alignment, and weekly governance. Should I configure them?"
-
-If the user agrees, **execute these commands:**
-
-### 1. Health Check (Every 4 hours)
-
-**What it does:** Verifies core tools (rg, node, python) are available and alerts on failure.
-
-```bash
-openclaw cron add --name "health-check" \
-  --every 4h \
-  --session main \
-  --system-event 'Health check: Verify core tools (rg, node, python) are available. Check if workspace state matches actual progress.'
-```
-
-### 3. Strategy Alignment (Daily at 9 AM)
-
-**What it does:** Checks if daily operations have drifted from CURRENT_FOCUS.md strategic goals.
-
-```bash
-openclaw cron add --name "strategy-alignment" \
-  --cron "0 9 * * *" --tz "UTC" \
-  --session isolated \
-  --announce \
-  --message 'Execute strategy alignment check: Compare against memory/okr/CURRENT_FOCUS.md. Confirm if past 24 hours of operations have drifted from strategic focus. Alert user if drifted.'
-```
-
-### 4. Memory Weekly Cleanup (Monday 10 AM)
-
-**What it does:** Reviews daily memory files, extracts important content to MEMORY.md, cleans outdated info.
-
-```bash
-openclaw cron add --name "memory-weekly" \
-  --cron "0 10 * * 1" --tz "UTC" \
-  --session isolated \
-  --no-deliver \
-  --message 'Execute weekly memory cleanup: Review recent memory/YYYY-MM-DD.md files, extract important content to MEMORY.md, clean outdated info.'
-```
-
-### 5. Weekly Governance (Sunday Midnight UTC)
-
-Update WEEK_STATE.json and validate CURRENT_FOCUS.md:
-
-**CLI command to create:**
-```bash
-openclaw cron add --name "weekly-governance" \
-  --cron "0 0 * * 0" --tz "UTC" \
-  --session isolated \
-  --timeout 300000 \
-  --message 'Execute weekly governance: 1) Validate CURRENT_FOCUS.md claims (PR merged? docs exist? tests pass?), 2) Update WEEK_STATE.json metrics, 3) Record to WEEK_EVENTS.jsonl, 4) If task queue empty, remind user to plan next phase tasks'
-```
-
-**JSON config reference:**
-{
-  "action": "add",
-  "job": {
-    "name": "weekly-governance",
-    "schedule": { "kind": "cron", "expr": "0 0 * * 0", "tz": "UTC" },
-    "sessionTarget": "isolated",
-    "payload": {
-      "kind": "agentTurn",
-      "message": "Execute weekly governance:\n\n## 1. Validate CURRENT_FOCUS.md Claims\nFor each task marked ✅ completed:\n- PR merged? Check: git log --oneline --all | grep 'Merge PR'\n- Document exists? Check: ls -la <path>\n- Tests passing? Check: npm test 2>&1 | grep 'passed'\n\n## 2. Update WEEK_STATE.json\n- Update week number to current ISO week\n- Update progress fields based on evidence\n- Update metrics (test count, coverage)\n- Remove completed blockers\n\n## 3. Record to WEEK_EVENTS.jsonl\n- Append: {\"type\": \"weekly_review\", \"timestamp\": \"...\", \"findings\": [...]}\n\n## 4. Output Summary\nReport what changed and any discrepancies found.",
-      "timeoutSeconds": 300
-    },
-    "delivery": { "mode": "announce" }
-  }
-}
-```
-
-### Timezone Confirmation
-
-**Before installing**, confirm the user's timezone:
-
-> "What's your timezone? (Default: America/New_York)"
-
-If the user provides a different timezone, replace the `tz` field in the jobs above.
-
-### Installation Verification
-
-After installation, run:
-
-```bash
-openclaw cron list
-```
-
-Confirm all jobs are correctly created.
-
----
-
-## When You're Done
-
-After initialization:
-
-1. Tell the user you're ready
-2. Briefly introduce your core capabilities
-3. **Delete this file** — You don't need the bootstrap script anymore
-
----
-
-_Good luck out there. Make it count._

package/plugin/templates/langs/en/skills/admin/SKILL.md

@@ -1,39 +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
-
-You are now the "Evolutionary System Administrator". Your responsibility is to maintain, repair, or initialize the system's "bare-bones" architecture based on user-provided parameters `$ARGUMENTS`.
-
----
-
-## Core Functions
-
-### 1. `diagnose` (System Diagnosis)
-**Action**: Check the integrity of the "bare-bones" architecture.
-- **Core Components**: Check if `.claude/hooks/hook_runner.py` exists and is executable.
-- **Documentation Integrity**: Check if `.principles/PROFILE.json` etc. exist.
-- **Tool Awareness**: Check `.state/SYSTEM_CAPABILITIES.json`. If missing, prompt user: "⚠️ Toolchain upgrade not performed. Recommend running `/bootstrap-tools` to significantly enhance system capabilities."
-- **Memory Mount**: Check if `CLAUDE.md` contains `System Integration` section.
-- **Output**: Generate a health report listing missing or abnormal items.
-
-### 2. `repair` (System Repair)
-**Action**: 
-- **Config Recovery**: If `PROFILE.json` is missing or corrupted, attempt recovery from `.claude/templates/PROFILE.json`.
-- **Structure Completion**: Ensure workspace structure is complete.
-- **Forced Cleanup**: Delete `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` and other temporary markers.
-
-### 3. `reset` (Force Reset)
-**Action**: After explicit user confirmation, reset `USER_PROFILE.json` and `AGENT_SCORECARD.json` to zero.
-
-### 4. `status` (Status Report)
-**Action**: Report current Risk Paths, user's highest/lowest scoring domains, and Agent rankings.
-
----
-
-## Execution Guidelines
-- You will only see this instruction when a human user enters `/admin`.
-- Briefly describe the plan before execution, output "✅ System hardened/initialized" after completion.

package/plugin/templates/langs/en/skills/bootstrap-tools/SKILL.md

@@ -1,53 +0,0 @@
----
-name: bootstrap-tools
-description: Scans project tech stack and searches the web for the latest, most effective CLI tools to augment agent capabilities. Suggests and installs tools upon user approval.
-disable-model-invocation: true
----
-
-# /bootstrap-tools: Equipment Upgrade Officer
-
-Your goal is to equip the agent team with the most advanced weapons. By analyzing the current project stack and **real-time web search**, find the best CLI tools to improve development, refactoring, and testing efficiency.
-
-## Execution Flow
-
-### 1. Recon
-- **Analyze Tech Stack**: Read `package.json`, `Cargo.toml`, `requirements.txt` etc. Identify core frameworks (e.g., Next.js, FastAPI).
-- **Inventory Status**: Run `npm list -g --depth=0` and `command -v` to check installed tools.
-
-### 2. Hunt
-- **Web Search**: Search for the latest CLI power tools for the current stack.
-  - *Query Examples*: "best CLI tools for Next.js 15 development 2025", "fastest rust-based grep alternative", "modern linter for python".
-- **Selection Criteria**:
-  - **Headless**: Must be CLI tools.
-  - **Performance**: Prioritize high-performance tools written in Rust/Go (e.g., `ripgrep`, `ast-grep`, `oxc`).
-  - **Relevance**: Must solve real pain points (e.g., `knip` for dead code, `depcheck` for dependencies).
-
-### 3. Pitch
-- Use `AskUserQuestion` to present recommendations to user.
-- **Format**:
-  - **Tool Name**: [Name]
-  - **Recommendation Reason**: [Why it helps the agent/project]
-  - **Install Command**: `npm i -g ...` or `apt-get ...`
-  - **Demo**: Provide a simple usage example.
-
-### 4. Deploy & Register
-- After approval, execute installation command.
-    - **Verification (Mandatory)**:
-      - After installation, **must** run `<tool> --version` or `command -v <tool>` to verify successful installation.
-      - **If Failed**: Inform user (possibly permission issue), request manual installation, **do not** update capabilities file.
-      - **If Successful**: 
-        - Update `.state/SYSTEM_CAPABILITIES.json`. Record the new tool's path.
-        - **Broadcast to All Agents**: 
-          - Scan `.claude/agents/*.md`.
-          - Check if each file contains `@.state/SYSTEM_CAPABILITIES.json`.
-          - If not, append to end of file:
-            ```markdown
-            
-            ## Environment Capabilities
-            Check @.state/SYSTEM_CAPABILITIES.json for high-performance tools (e.g., ripgrep, ast-grep) available in this environment. Use them!
-            ```
-          - Prompt user to run `/pd-status` or `/admin diagnose` to let Agent perceive new capabilities.
-
-## Core Principles
-- **Prefer New Over Old**: Dare to recommend new tools to replace old ones (e.g., recommend `pnpm` over `npm`, `vitest` over `jest`), but explain the reasoning.
-- **Safety First**: Must obtain explicit user authorization before installation.

package/plugin/templates/langs/en/skills/deductive-audit/SKILL.md

@@ -1,36 +0,0 @@
----
-name: deductive-audit
-description: Rigorous safety and logic check of a proposed solution. Evaluates against axioms, system impact, and edge cases.
-disable-model-invocation: true
----
-
-# Deductive Audit
-
-**Goal**: Intercept logic errors and potential risks before execution.
-
-Please conduct a three-phase review of the proposed fix:
-
-## 1. Axiom Test
-- Are language specifications, library API contracts, or project conventions violated?
-- Are input/output types aligned?
-
-## 2. System Test
-- Does it introduce new technical debt?
-- Does it affect performance, latency, or stability?
-- Does it introduce circular dependencies?
-
-## 3. Entropy Audit - *New*
-- **Necessity**: Is this modification absolutely necessary? Is there a simpler solution?
-- **Minimization**: Does it touch files it shouldn't? (Principle of minimal surface area)
-- **Anti-gaming**: Is this a genuine fix, or "formalism" just to pass the gate?
-
-## 4. Via Negativa
-- What happens in the worst case (network down, disk full, malicious input)?
-- Are there security red line risks (token leak, privilege escalation)?
-
-## 5. Verdict
-- **RESULT**: PASS | FAIL
-- **Must Fix**: If failed, list points that must be corrected.
-
----
-**Action**: Update the above results to `AUDIT.md`.

package/plugin/templates/langs/en/skills/evolution-framework-update/SKILL.md

@@ -1,31 +0,0 @@
----
-name: evolution-framework-update
-description: Pull the latest updates for the Principles Disciple evolution framework (including Orchestrator mode, async queue, and map-first protocol).
----
-
-# /evolution-framework-update: Evolution Framework Self-Update
-
-**Goal**: Sync latest code from upstream framework (Hooks, Skills, Agents, Daemon) to maintain system evolution capability.
-
-## 1. Execute Update
-Run the following script to pull latest code:
-
-```bash
-bash scripts/update_agent_framework.sh
-```
-
-## 2. Conflict Handling (Smart Merge)
-After script runs, check output:
-- **No Conflict**: If shows "✅ Update complete", no action needed.
-- **Conflict**: If shows "⚠️ Updates found with conflicts":
-  1. Find all `.update` files:
-     ```bash
-     find .claude -name "*.update"
-     ```
-  2. For each conflicting file (e.g., `THINKING_OS.md` vs `THINKING_OS.md.update`):
-     - **Read** original file and `.update` file.
-     - **Analyze** differences: merge upstream new features, preserve local personalized config.
-     - **Cleanup**: Delete `.update` file after merge.
-
-## 3. Restart to Apply
-After update completes, recommend restarting Session to load latest neural hub logic.

package/plugin/templates/langs/en/skills/evolve-task/SKILL.md

@@ -1,83 +0,0 @@
----
-name: evolve-task
-description: Run the full evolution loop (triage → diagnosis → audit → plan → execute → review → log)
-disable-model-invocation: true
----
-
-You must execute the following steps in order (no skipping). ARGUMENTS: $ARGUMENTS
-
-## Step 0: Restore Context (Mandatory)
-- Read the last entry in memory/CHECKPOINT.md
-- Read the last 3 entries in memory/ISSUE_LOG.md
-- Read recent decisions in memory/DECISIONS.md
-- Runtime V2 pain diagnosis uses task input/context, not `.state/.pain_flag`
-
-## Step 1: Read Runtime Parameters & Self-Check
-- Read .principles/PROFILE.json, understand risk_paths, gate, tests.commands.
-- **Capability Self-Check**: Quickly scan `skills/` and `agents/` under plugin directory. If there's a specialized Skill (like `/deep-search`) or Agent (like `security-expert`) for the current task, prioritize using them in subsequent steps.
-
-## Step 1.5: Full-Spectrum Awareness
-- **Local**: Run `git status` and `git log -n 5` to understand code status.
-- **Remote**: If `gh` is available, must run `gh issue list --limit 5` and `gh pr list --limit 5`.
-- **Correlation**: If related Issues found, must record their IDs in current task context.
-
-## Step 2: TRIAGE (Fill Information Gaps)
-- **Map First**: Must read architecture diagrams under `codemaps/` or `docs/SYSTEM_PANORAMA.md` to accurately assess modification risk.
-Output:
-- Goal (one sentence)
-- Problem (reproducible description)
-- Evidence (files/commands/logs)
-- Risk level (low/medium/high)
-
-## Step 3: Delegate Explorer (Evidence Collection)
-- Let Explorer sub-agent output: Evidence list / Repro / Hypotheses(<=3)
-- **Performance Evaluation**: After task completion, evaluate Explorer performance and write to `.state/.verdict.json`. Format must strictly follow `@.principles/schemas/agent_verdict_schema.json`.
-
-## Step 4: Delegate Diagnostician (Root Cause)
-- Let Diagnostician output: Proximal cause / Root cause / 5 Whys / Category
-- **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-
-## Step 5: Delegate Auditor (Deductive Audit)
-- Let Auditor output: Axiom/System/Via negativa / RESULT: PASS/FAIL
-- Write audit result to AUDIT.md (RESULT line must exist).
-- **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-
-### Branch Handling (Must Follow)
-- If RESULT = FAIL:
-  1. Write Must-fix list to AUDIT.md
-  2. Go back to Step 4 to re-delegate Diagnostician, request supplemental root cause
-  3. Max 2 retries; if still FAIL, write to memory/DECISIONS.md and request user intervention
-- If RESULT = PASS: Continue to Step 6
-
-## Step 6: Delegate Planner (Movie Script Plan)
-- Planner outputs Plan (steps/commands/metrics/rollback).
-- Write plan to a planning document for owner review.
-- **Task Sync**: 
-  - If `CLAUDE_CODE_TASK_LIST_ID` is set, you must convert the Plan's core steps to Native Tasks (via natural language command "Add task..." or related tools).
-  - If not set and in interactive mode, prompt user: "Recommend running `export CLAUDE_CODE_TASK_LIST_ID=task-$(date +%s)` to enable persistent task tracking."
-  - If in background/headless mode, skip prompt.
-- **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-
-## Step 7: Delegate Implementer (Execution)
-- Implementer executes according to the plan from Step 6. Any deviation must first be approved by updating the plan.
-- **Performance Evaluation**: After task completion, write to `.state/.verdict.json` based on verification results. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-
-## Step 8: Delegate Reviewer (Review)
-- Reviewer outputs: Critical/Warning/Suggestion.
-- **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
-
-### Branch Handling
-- If Critical exists: Go back to Step 6 to revise plan, max 2 retries
-- If no Critical: Continue to Step 9
-
-## Step 9: Reflection & Persistence
-1. **System Evolution**: Append Pain/Root cause/New principle candidates/Gate suggestions to memory/ISSUE_LOG.md, and update memory/DECISIONS.md.
-2. **User Profile Update (Mandatory)**:
-   - Review user's performance in this task (instruction quality, domain knowledge, preferences) and system highlights.
-   - **Must** write to `.state/.user_verdict.json` (incremental update). Format must strictly follow `@.principles/schemas/user_verdict_schema.json`.
-   - Note: If user shows no obvious characteristics or preferences, corresponding fields can be empty.
-
-## Step 10: Final Briefing
-- **Action**: Delegate ``pd_spawn_agent(reporter)`` for closing statement.
-- **Requirement**: Pass Implementer and Reviewer's final outputs as input. Let it decide report depth and style based on `USER_CONTEXT.md`.
-- **Goal**: Ensure the boss (user) clearly understands task outcomes and potential risks without cognitive load.

package/plugin/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.