@cardor/agent-harness-kit 1.7.5 → 1.8.1

package/dist/skills/ahk-ask/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: ahk-ask
+description: Ask a question about this codebase — where is X, does Y exist, how does Z work. Read-only. No tasks created, no harness tracking.
+---
+
+You are in **lightweight ask mode**.
+
+> If `$ARGUMENTS` is empty, ask the user what they want to know before doing anything else.
+
+The user's question: $ARGUMENTS
+
+## Rules
+- NO MCP calls — no tasks.*, no actions.*
+- NO health.sh
+- NO builder, NO reviewer
+- Create files ONLY if user explicitly asked to save the output
+
+## Process
+
+1. Invoke **Explorer** as a subagent with this exact instruction:
+   > "Read-only codebase question — no MCP harness, no task creation. Map only what is needed to answer: `$ARGUMENTS`. Return: which files are relevant, what the code does, any patterns or constraints the user should know."
+
+2. Synthesize Explorer's findings into a direct, concise answer for the user.
+   Do not relay the raw output — distill it.
+
+## Output
+- Concise answer to the user's question
+- Relevant file paths and code references
+- Important caveats or related constraints

package/dist/skills/ahk-consultant/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: ahk-consultant
+description: Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.
+---
+
+You are in **lightweight consultation mode**. The user's topic: $ARGUMENTS
+
+## Rules
+- NO MCP calls — no tasks.*, no actions.*
+- NO health.sh
+- NO builder, NO reviewer
+- Create files ONLY if user explicitly asked to save the output
+
+## Process
+
+1. Invoke **Explorer** as a subagent:
+   > "Read-only context gathering — no MCP harness. The user wants technical advice on: `$ARGUMENTS`. Map the relevant codebase — existing patterns, current implementation, relevant dependencies. Return findings as plain structured text."
+
+2. Invoke **Consultant** as a subagent in direct consultation mode, passing Explorer's output:
+   > "Direct consultation — no MCP harness, no task. User's topic: `$ARGUMENTS`. Explorer found: [explorer output]. Provide structured technical advice. The provider has already injected available skills into your context — check what skills you are aware of, identify which are relevant to this topic, and reference them explicitly in your advice. If no installed skills seem relevant to the topic, recommend running `npx autoskills` to fetch appropriate skill packs."
+
+3. Synthesize a final response for the user.
+
+## Output structure
+- **Context** — brief summary of relevant codebase state
+- **Advice** — consultant's structured recommendations
+- **Relevant skills** — skills from your context that apply, OR `npx autoskills` recommendation if none match
+- **Risks & warnings** — what could go wrong with the proposed approach

package/dist/skills/ahk-triage/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ahk-triage
+description: Triage a bug or unexpected behavior. Deep diagnostic analysis with structured report. No tasks created, no harness tracking.
+---
+
+You are in **lightweight triage mode**.
+
+> If `$ARGUMENTS` is empty, ask the user to describe the issue before doing anything else.
+
+The issue: $ARGUMENTS
+
+## Rules
+- NO MCP calls — no tasks.*, no actions.*
+- Run health.sh ONLY if the issue explicitly involves the build or test suite — not as a routine step
+- NO builder, NO reviewer
+- Create files ONLY if user explicitly asked to save the report
+
+## Process
+
+1. Invoke **Explorer** as a subagent:
+   > "Read-only diagnostic investigation — no MCP harness. Issue reported: `$ARGUMENTS`. Investigate: which files are likely involved, what code paths produce this behavior, what assumptions might be violated, what state or environment conditions could trigger this. Return a detailed diagnostic analysis."
+
+2. Synthesize Explorer's findings into the REQUIRED output format below. Do not skip or reorder sections.
+
+## Required output format
+
+---
+
+**TL;DR**
+One paragraph. What is happening and the most likely cause.
+
+**Long Description**
+Detailed analysis: what the code is doing, what it should do, where the divergence occurs.
+
+**Root Cause Analysis**
+The causal chain: trigger → behavior → symptom. Name specific files, functions, and line numbers where relevant.
+
+**Possible Fixes**
+Ordered most-to-least likely. Each fix must be a concrete actionable step naming specific files/functions.
+
+**Follow-up Questions**
+*(Omit this section entirely if investigation was sufficient. Include only genuine unknowns that would change the diagnosis.)*
+
+---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cardor/agent-harness-kit",
-  "version": "1.7.5",
+  "version": "1.8.1",
   "description": "CLI scaffolding for multi-agent harness systems",
   "publishConfig": {
     "access": "public"
@@ -49,7 +49,7 @@
     "ws": "^8.18.0"
   },
   "devDependencies": {
-    "@cardor/agent-harness-kit": "^1.6.0",
+    "@cardor/agent-harness-kit": "^1.8.0",
     "@commitlint/cli": "^20.5.3",
     "@commitlint/config-conventional": "^20.5.3",
     "@eslint-react/eslint-plugin": "^5.7.1",