create-principles-disciple 1.112.2 → 1.113.0

package/plugin/dist/core/control-ui-db.d.ts

@@ -1,117 +0,0 @@
-/**
- * Control UI database stores ANALYTICS READ MODELS.
- *
- * PURPOSE: Aggregated data for dashboard visualization and historical insights.
- * USAGE: Control UI queries and dashboard displays.
- * NOT FOR: Control decisions, Phase 3 eligibility, or real-time operations.
- *
- * Runtime truth comes from: queue state, workspace trust scorecard, active sessions
- */
-export interface ThinkingModelEventInput {
-    sessionId: string;
-    runId: string;
-    assistantTurnId: number;
-    modelId: string;
-    matchedPattern: string;
-    scenarioJson: unknown;
-    toolContextJson: unknown;
-    painContextJson: unknown;
-    principleContextJson: unknown;
-    triggerExcerpt: string;
-    createdAt: string;
-}
-export interface ControlUiDatabaseOptions {
-    workspaceDir: string;
-    busyTimeoutMs?: number;
-}
-export interface RecentThinkingContext {
-    toolCalls: {
-        id: number;
-        toolName: string;
-        outcome: 'success' | 'failure' | 'blocked';
-        errorType: string | null;
-        errorMessage: string | null;
-        createdAt: string;
-    }[];
-    painEvents: {
-        id: number;
-        source: string;
-        score: number;
-        reason: string | null;
-        createdAt: string;
-    }[];
-    gateBlocks: {
-        id: number;
-        toolName: string;
-        reason: string;
-        filePath: string | null;
-        createdAt: string;
-    }[];
-    userCorrections: {
-        id: number;
-        correctionCue: string | null;
-        rawExcerpt: string | null;
-        createdAt: string;
-    }[];
-    principleEvents: {
-        id: number;
-        principleId: string | null;
-        eventType: string;
-        createdAt: string;
-    }[];
-}
-export declare class ControlUiDatabase {
-    private readonly workspaceDir;
-    private readonly dbPath;
-    private readonly blobDir;
-    private readonly db;
-    constructor(opts: ControlUiDatabaseOptions);
-    dispose(): void;
-    recordThinkingModelEvent(input: ThinkingModelEventInput): number;
-    /**
-     * Get recent thinking context for a session.
-     *
-     * Returns: Analytics data (read model) aggregated from trajectory database.
-     * Not: Runtime truth or real-time queue state.
-     */
-    getRecentThinkingContext(sessionId: string, beforeCreatedAt: string, limit?: number): RecentThinkingContext;
-    /**
-     * Execute SQL query and return all rows.
-     *
-     * Returns: Analytics data (read model) aggregated from trajectory database.
-     * Not: Runtime truth or real-time queue state.
-     */
-    all<T>(sql: string, ...params: unknown[]): T[];
-    /**
-     * Execute SQL query and return first row.
-     *
-     * Returns: Analytics data (read model) aggregated from trajectory database.
-     * Not: Runtime truth or real-time queue state.
-     */
-    get<T>(sql: string, ...params: unknown[]): T | undefined;
-    /**
-     * Execute SQL statement that does not return rows (DDL, CREATE TABLE, etc.).
-     *
-     * Returns: void (executes directly)
-     * Not for: SELECT queries (use all() or get() instead)
-     */
-    execute(sql: string): void;
-    /**
-     * Execute a parameterized write statement (INSERT, UPDATE, DELETE).
-     */
-    run(sql: string, ...params: unknown[]): void;
-    restoreRawText(inlineText?: string | null, blobRef?: string | null): string;
-    private initSchema;
-    /**
-     * Create or replace a view, tolerating missing dependency tables.
-     *
-     * Views in ControlUiDatabase depend on tables created by TrajectoryDatabase
-     * (assistant_turns, tool_calls, pain_events, user_turns, correction_samples).
-     * If ControlUiDatabase is constructed before TrajectoryDatabase has created
-     * those tables, CREATE VIEW would throw. We DROP+CREATE with try/catch so
-     * missing-dependency views are skipped with a warning (rc-9: surfaced via
-     * console.info) rather than aborting schema initialization.
-     */
-    private createViewSafely;
-    private withWrite;
-}

package/plugin/dist/core/thinking-models.d.ts

@@ -1,25 +0,0 @@
-/**
- * Thinking Models — Plugin I/O Adapter (Stage 3 slim)
- *
- * Pure logic (BUILTIN_PATTERNS, BUILTIN_PATTERN_MAP, getFallbackName,
- * getFallbackDescription, deriveThinkingScenarios, types) lives in
- * @principles/core/runtime-v2/thinking-models.
- *
- * This file owns only the I/O boundary: reading THINKING_OS.md from a
- * workspace dir and merging it with the builtin patterns. It re-exports
- * the pure functions and types so existing relative imports
- * (../core/thinking-models.js) continue to resolve.
- */
-import { type ThinkingModelDefinition, type ThinkingModelMatch } from '@principles/core/runtime-v2';
-export { BUILTIN_PATTERN_MAP, getFallbackName, getFallbackDescription, } from '@principles/core/runtime-v2';
-export { deriveThinkingScenarios } from '@principles/core/runtime-v2';
-export type { ThinkingModelDefinition, ThinkingModelMatch, ThinkingScenarioContext, } from '@principles/core/runtime-v2';
-/**
- * Load thinking model definitions dynamically from THINKING_OS.md.
- * Falls back to built-in definitions if parsing fails.
- *
- * @param workspaceDir Optional. If provided, loads from that workspace's THINKING_OS.md.
- */
-export declare function listThinkingModels(workspaceDir?: string): ThinkingModelDefinition[];
-export declare function getThinkingModel(modelId: string, workspaceDir?: string): ThinkingModelDefinition | undefined;
-export declare function detectThinkingModelMatches(text: string, workspaceDir?: string): ThinkingModelMatch[];

package/plugin/dist/templates/workspace/.principles/THINKING_OS_CANDIDATES.md

@@ -1,9 +0,0 @@
-# Thinking OS — 候选思维模型池
-
-> 本文件由智能体在反思过程中自动追加候选条目。
-> 晋升为正式模型需满足：≥3 种任务验证有效 + ≤3 行可描述 + 非冗余 + 人类批准。
-> 使用 `/thinking-os propose` 手动提议，或 `/thinking-os audit` 审计候选池。
-
----
-
-<!-- 候选条目从这里开始 -->

package/plugin/templates/workspace/.principles/THINKING_OS_CANDIDATES.md

@@ -1,9 +0,0 @@
-# Thinking OS — 候选思维模型池
-
-> 本文件由智能体在反思过程中自动追加候选条目。
-> 晋升为正式模型需满足：≥3 种任务验证有效 + ≤3 行可描述 + 非冗余 + 人类批准。
-> 使用 `/thinking-os propose` 手动提议，或 `/thinking-os audit` 审计候选池。
-
----
-
-<!-- 候选条目从这里开始 -->

package/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/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 `/manage-okr` 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/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/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/templates/langs/en/skills/evolve-system/SKILL.md

@@ -1,46 +0,0 @@
----
-name: evolve-system
-description: Second-order observation and system-level evolution. Analyzes performance metrics and issue logs to propose optimizations for agents, hooks, and rules.
-disable-model-invocation: true
----
-
-# /evolve-system: The Digital Architect (Second-Order Observation)
-
-Your identity is now the system's **Digital Architect**. Your responsibility is not to fix business code, but to optimize the system's own "genes" (Prompts, Hooks, Rules) by analyzing system runtime data.
-
-## 1. Metrics Analysis
-- **Read Data**:
-  - `.state/AGENT_SCORECARD.json`: Calculate each Agent's win rate (wins / (wins + losses)).
-  - `memory/ISSUE_LOG.md`: Identify repeated patterns in the last 10 records (Pain Patterns).
-- **Identify Anomalies**:
-  - **Inefficient Agent**: Agents with win rate below 50% and sample size >= 3.
-  - **Systemic Issues**: Same type of systemic errors appearing more than 2 times in Issue Log.
-
-## 2. Systemic Diagnosis
-- For identified anomalies, analyze their definitions in `.claude/agents/` or `.claude/hooks/`.
-- **Think**: 
-  - Is the Prompt description too vague causing hallucinations?
-  - Does the Hook logic have boundary blind spots?
-  - Is a critical Guardrail missing?
-
-## 2.5 Clinical Trial - *Optional*
-**If root cause is unclear**, conduct empirical testing:
-- **Consult**: Use `AskUserQuestion` to ask: "To confirm the issue, I need to run an automatic diagnostic task for [Agent], which may consume some tokens. Continue?"
-- **Silent Execution**:
-  - If user agrees, directly call ``pd_spawn_agent` 工具` to initiate test.
-  - **Instruction**: "You are being diagnosed. Please execute the following task: [Test Scenario]. Keep output extremely concise, only return final result or error message."
-  - **Observe**: Check if its tool call chain meets expectations (e.g., did it use the correct Search tool).
-- **Diagnose**: Based on test performance, pinpoint the issue.
-
-## 3. Optimization Proposal
-**If root cause is confirmed**, generate `SYSTEM_OPTIMIZATION_PLAN.md`, including:
-- **Diagnosis Conclusion**: Clearly state which part of the system is "sick".
-- **Modification Suggestion**: Provide specific code/Prompt modification diffs.
-- **Expected Benefits**: Explain how this modification improves win rate or reduces pain.
-
-## 4. Safety Gate
-- **Mandatory Confirmation**: Before modifying any system files (under `.claude/` directory), must use `AskUserQuestion` to present the proposal and obtain explicit user authorization.
-- **Atomicity**: Only suggest one high-leverage optimization point at a time, don't attempt to refactor the entire system at once.
-
-## Completion
-Output: "✅ System self-diagnosis complete. Proposal submitted, awaiting boss decision."

package/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/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/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 `/manage-okr` for quarterly/iteration-level task breakdown."

package/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
-```