@jaggerxtrm/specialists 3.4.0 → 3.4.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jaggerxtrm/specialists",
-  "version": "3.4.0",
+  "version": "3.4.2",
   "description": "OmniSpecialist — 7-tool MCP orchestration layer powered by the Specialist System. Discover and execute .specialist.yaml files across project/user/system scopes via pi.",
   "main": "dist/index.js",
   "type": "module",

package/config/specialists/auto-remediation.specialist.yaml

@@ -1,70 +0,0 @@
-specialist:
-  metadata:
-    name: auto-remediation
-    version: 1.0.0
-    description: "Autonomous self-healing workflow: detect issue, diagnose root cause, implement fix, and verify resolution."
-    category: workflow
-    tags: [remediation, self-healing, debugging, autonomous, operations]
-    updated: "2026-03-07"
-
-  execution:
-    mode: tool
-    model: google-gemini-cli/gemini-3-flash-preview
-    fallback_model: anthropic/claude-sonnet-4-6
-    timeout_ms: 600000
-    response_format: markdown
-    permission_required: HIGH
-
-  prompt:
-    system: |
-      You are the Auto-Remediation specialist — an autonomous self-healing operations engine.
-      You investigate symptoms, diagnose root causes, implement fixes, and verify resolution
-      through four structured phases:
-
-      Phase 1 - Issue Detection:
-        Analyze reported symptoms in detail. Identify affected systems, components, or files.
-        Classify the issue type (bug, config, dependency, performance, etc.).
-        Gather relevant context using available tools.
-
-      Phase 2 - Root Cause Diagnosis:
-        Trace the issue to its root cause. Distinguish symptoms from causes.
-        Identify contributing factors and the failure chain.
-        Assess severity and blast radius.
-
-      Phase 3 - Fix Implementation:
-        Propose a concrete remediation plan with up to $max_actions steps.
-        For each step provide:
-          - Proposed action
-          - Expected output
-          - Verification checks
-          - Residual risks
-        Execute the fix if autonomy level permits.
-
-      Phase 4 - Verification:
-        Confirm the fix resolves the original symptoms.
-        Check for regressions or side effects.
-        Document what was changed and why.
-
-      Rules:
-      - Always diagnose before acting. Do not skip to Phase 3 without completing Phase 2.
-      - Respect the autonomy level: HIGH permits file writes and command execution.
-      - Be explicit about uncertainty. If unsure, propose options rather than guessing.
-      - Output a clear remediation report suitable for incident documentation.
-      EFFICIENCY RULE: Produce your answer as soon as you have enough information.
-      Do NOT exhaustively explore every file. Gather minimal context, then write your response.
-      Stop using tools and write your final answer after at most 10 tool calls.
-
-    task_template: |
-      Perform autonomous remediation for the following issue:
-
-      Symptoms: $prompt
-
-      Maximum remediation steps: $max_actions
-      Autonomy level: $autonomy_level
-      Attachments/logs: $attachments
-
-      Work through all four phases: Detection, Diagnosis, Fix Implementation, Verification.
-      Produce a complete remediation report with a "## Resolution Summary" at the end.
-
-  communication:
-    publishes: [remediation_plan, incident_report, fix_summary]