principles-disciple 1.209.3 → 1.209.5

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