@heyai-rules/pilo-masterkit 2.1.0 → 3.1.0

package/.agent/workflows/harness-audit.md

@@ -1,73 +1,73 @@
-# Harness Audit Command
-
-Run a deterministic repository harness audit and return a prioritized scorecard.
-
-## Usage
-
-`/harness-audit [scope] [--format text|json] [--root path]`
-
-- `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents`
-- `--format`: output style (`text` default, `json` for automation)
-- `--root`: audit a specific path instead of the current working directory
-
-## Deterministic Engine
-
-Always run:
-
-```bash
-node scripts/harness-audit.js <scope> --format <text|json> [--root <path>]
-```
-
-This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points.
-
-Rubric version: `2026-03-30`.
-
-The script computes 7 fixed categories (`0-10` normalized each):
-
-1. Tool Coverage
-2. Context Efficiency
-3. Quality Gates
-4. Memory Persistence
-5. Eval Coverage
-6. Security Guardrails
-7. Cost Efficiency
-
-Scores are derived from explicit file/rule checks and are reproducible for the same commit.
-The script audits the current working directory by default and auto-detects whether the target is the ECC repo itself or a consumer project using ECC.
-
-## Output Contract
-
-Return:
-
-1. `overall_score` out of `max_score` (70 for `repo`; smaller for scoped audits)
-2. Category scores and concrete findings
-3. Failed checks with exact file paths
-4. Top 3 actions from the deterministic output (`top_actions`)
-5. Suggested ECC skills to apply next
-
-## Checklist
-
-- Use script output directly; do not rescore manually.
-- If `--format json` is requested, return the script JSON unchanged.
-- If text is requested, summarize failing checks and top actions.
-- Include exact file paths from `checks[]` and `top_actions[]`.
-
-## Example Result
-
-```text
-Harness Audit (repo): 66/70
-- Tool Coverage: 10/10 (10/10 pts)
-- Context Efficiency: 9/10 (9/10 pts)
-- Quality Gates: 10/10 (10/10 pts)
-
-Top 3 Actions:
-1) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json)
-2) [Tool Coverage] Sync commands/harness-audit.md and .opencode/commands/harness-audit.md. (.opencode/commands/harness-audit.md)
-3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/)
-```
-
-## Arguments
-
-$ARGUMENTS:
-- `repo|hooks|skills|commands|agents` (optional scope)
-- `--format text|json` (optional output format)
+# Harness Audit Command
+
+Run a deterministic repository harness audit and return a prioritized scorecard.
+
+## Usage
+
+`/harness-audit [scope] [--format text|json] [--root path]`
+
+- `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents`
+- `--format`: output style (`text` default, `json` for automation)
+- `--root`: audit a specific path instead of the current working directory
+
+## Deterministic Engine
+
+Always run:
+
+```bash
+node scripts/harness-audit.js <scope> --format <text|json> [--root <path>]
+```
+
+This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points.
+
+Rubric version: `2026-03-30`.
+
+The script computes 7 fixed categories (`0-10` normalized each):
+
+1. Tool Coverage
+2. Context Efficiency
+3. Quality Gates
+4. Memory Persistence
+5. Eval Coverage
+6. Security Guardrails
+7. Cost Efficiency
+
+Scores are derived from explicit file/rule checks and are reproducible for the same commit.
+The script audits the current working directory by default and auto-detects whether the target is the ECC repo itself or a consumer project using ECC.
+
+## Output Contract
+
+Return:
+
+1. `overall_score` out of `max_score` (70 for `repo`; smaller for scoped audits)
+2. Category scores and concrete findings
+3. Failed checks with exact file paths
+4. Top 3 actions from the deterministic output (`top_actions`)
+5. Suggested ECC skills to apply next
+
+## Checklist
+
+- Use script output directly; do not rescore manually.
+- If `--format json` is requested, return the script JSON unchanged.
+- If text is requested, summarize failing checks and top actions.
+- Include exact file paths from `checks[]` and `top_actions[]`.
+
+## Example Result
+
+```text
+Harness Audit (repo): 66/70
+- Tool Coverage: 10/10 (10/10 pts)
+- Context Efficiency: 9/10 (9/10 pts)
+- Quality Gates: 10/10 (10/10 pts)
+
+Top 3 Actions:
+1) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json)
+2) [Tool Coverage] Sync commands/harness-audit.md and .opencode/commands/harness-audit.md. (.opencode/commands/harness-audit.md)
+3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/)
+```
+
+## Arguments
+
+$ARGUMENTS:
+- `repo|hooks|skills|commands|agents` (optional scope)
+- `--format text|json` (optional output format)

package/.agent/workflows/init-docs.md

@@ -1,46 +1,46 @@
----
-description: Tự động khởi tạo cấu trúc thư mục tài liệu cho dự án Pilo Masterkit.
----
-
-# Workflow: Khởi tạo Thư mục Tài liệu (Documentation Init)
-
-Quy trình này tự động tạo các thư mục cần thiết để quản lý tài liệu, báo cáo và nhiệm vụ theo chuẩn Pilo Masterkit.
-
-## Các bước thực hiện:
-
-1. **Kiểm tra và Tạo Thư mục**:
-   Tạo thư mục `docs/` ở thư mục gốc của dự án (nếu chưa có), sau đó tạo 8 thư mục con bên trong `docs/`:
-   - `docs/lessons/`: Lưu trữ bài học kinh nghiệm.
-   - `docs/reports/`: Lưu trữ báo cáo tiến độ và audit.
-   - `docs/plans/`: Lưu trữ kế hoạch triển khai.
-   - `docs/status/`: Lưu trữ trạng thái dự án.
-   - `docs/tasks/`: Lưu trữ danh sách nhiệm vụ chi tiết.
-   - `docs/logs/`: Lưu trữ nhật ký hoạt động của Agent.
-   - `docs/walkthroughs/`: Lưu trữ hướng dẫn thực hiện.
-   - `docs/producs/`: Lưu trữ đặc tả sản phẩm (specs, PRD).
-
-2. **Khởi tạo File mẫu (Tùy chọn)**:
-   Trong mỗi thư mục, tạo một file `README.md` ngắn gọn mô tả mục đích của thư mục đó.
-
-## Lệnh thực thi (Dành cho Agent):
-
-// turbo
-```pwsh
-$docsDir = "docs"
-if (-not (Test-Path $docsDir)) {
-    New-Item -ItemType Directory -Path $docsDir -Force
-    Write-Host "Created base directory: $docsDir"
-}
-
-$dirs = @("lessons", "reports", "plans", "status", "tasks", "logs", "walkthroughs", "producs")
-foreach ($dir in $dirs) {
-    $targetPath = Join-Path $docsDir $dir
-    if (-not (Test-Path $targetPath)) {
-        New-Item -ItemType Directory -Path $targetPath -Force
-        Write-Host "Created directory: $targetPath"
-    }
-}
-```
-
-## Báo cáo kết quả:
-Sau khi hoàn thành, báo cáo danh sách các thư mục đã được khởi tạo thành công.
+---
+description: Tự động khởi tạo cấu trúc thư mục tài liệu cho dự án Pilo Masterkit.
+---
+
+# Workflow: Khởi tạo Thư mục Tài liệu (Documentation Init)
+
+Quy trình này tự động tạo các thư mục cần thiết để quản lý tài liệu, báo cáo và nhiệm vụ theo chuẩn Pilo Masterkit.
+
+## Các bước thực hiện:
+
+1. **Kiểm tra và Tạo Thư mục**:
+   Tạo thư mục `docs/` ở thư mục gốc của dự án (nếu chưa có), sau đó tạo 8 thư mục con bên trong `docs/`:
+   - `docs/lessons/`: Lưu trữ bài học kinh nghiệm.
+   - `docs/reports/`: Lưu trữ báo cáo tiến độ và audit.
+   - `docs/plans/`: Lưu trữ kế hoạch triển khai.
+   - `docs/status/`: Lưu trữ trạng thái dự án.
+   - `docs/tasks/`: Lưu trữ danh sách nhiệm vụ chi tiết.
+   - `docs/logs/`: Lưu trữ nhật ký hoạt động của Agent.
+   - `docs/walkthroughs/`: Lưu trữ hướng dẫn thực hiện.
+   - `docs/producs/`: Lưu trữ đặc tả sản phẩm (specs, PRD).
+
+2. **Khởi tạo File mẫu (Tùy chọn)**:
+   Trong mỗi thư mục, tạo một file `README.md` ngắn gọn mô tả mục đích của thư mục đó.
+
+## Lệnh thực thi (Dành cho Agent):
+
+// turbo
+```pwsh
+$docsDir = "docs"
+if (-not (Test-Path $docsDir)) {
+    New-Item -ItemType Directory -Path $docsDir -Force
+    Write-Host "Created base directory: $docsDir"
+}
+
+$dirs = @("lessons", "reports", "plans", "status", "tasks", "logs", "walkthroughs", "producs")
+foreach ($dir in $dirs) {
+    $targetPath = Join-Path $docsDir $dir
+    if (-not (Test-Path $targetPath)) {
+        New-Item -ItemType Directory -Path $targetPath -Force
+        Write-Host "Created directory: $targetPath"
+    }
+}
+```
+
+## Báo cáo kết quả:
+Sau khi hoàn thành, báo cáo danh sách các thư mục đã được khởi tạo thành công.

package/.agent/workflows/instinct-export.md

@@ -1,66 +1,66 @@
----
-name: instinct-export
-description: Export instincts from project/global scope to a file
-command: /instinct-export
----
-
-# Instinct Export Command
-
-Exports instincts to a shareable format. Perfect for:
-- Sharing with teammates
-- Transferring to a new machine
-- Contributing to project conventions
-
-## Usage
-
-```
-/instinct-export                           # Export all personal instincts
-/instinct-export --domain testing          # Export only testing instincts
-/instinct-export --min-confidence 0.7      # Only export high-confidence instincts
-/instinct-export --output team-instincts.yaml
-/instinct-export --scope project --output project-instincts.yaml
-```
-
-## What to Do
-
-1. Detect current project context
-2. Load instincts by selected scope:
-   - `project`: current project only
-   - `global`: global only
-   - `all`: project + global merged (default)
-3. Apply filters (`--domain`, `--min-confidence`)
-4. Write YAML-style export to file (or stdout if no output path provided)
-
-## Output Format
-
-Creates a YAML file:
-
-```yaml
-# Instincts Export
-# Generated: 2025-01-22
-# Source: personal
-# Count: 12 instincts
-
----
-id: prefer-functional-style
-trigger: "when writing new functions"
-confidence: 0.8
-domain: code-style
-source: session-observation
-scope: project
-project_id: a1b2c3d4e5f6
-project_name: my-app
----
-
-# Prefer Functional Style
-
-## Action
-Use functional patterns over classes.
-```
-
-## Flags
-
-- `--domain <name>`: Export only specified domain
-- `--min-confidence <n>`: Minimum confidence threshold
-- `--output <file>`: Output file path (prints to stdout when omitted)
-- `--scope <project|global|all>`: Export scope (default: `all`)
+---
+name: instinct-export
+description: Export instincts from project/global scope to a file
+command: /instinct-export
+---
+
+# Instinct Export Command
+
+Exports instincts to a shareable format. Perfect for:
+- Sharing with teammates
+- Transferring to a new machine
+- Contributing to project conventions
+
+## Usage
+
+```
+/instinct-export                           # Export all personal instincts
+/instinct-export --domain testing          # Export only testing instincts
+/instinct-export --min-confidence 0.7      # Only export high-confidence instincts
+/instinct-export --output team-instincts.yaml
+/instinct-export --scope project --output project-instincts.yaml
+```
+
+## What to Do
+
+1. Detect current project context
+2. Load instincts by selected scope:
+   - `project`: current project only
+   - `global`: global only
+   - `all`: project + global merged (default)
+3. Apply filters (`--domain`, `--min-confidence`)
+4. Write YAML-style export to file (or stdout if no output path provided)
+
+## Output Format
+
+Creates a YAML file:
+
+```yaml
+# Instincts Export
+# Generated: 2025-01-22
+# Source: personal
+# Count: 12 instincts
+
+---
+id: prefer-functional-style
+trigger: "when writing new functions"
+confidence: 0.8
+domain: code-style
+source: session-observation
+scope: project
+project_id: a1b2c3d4e5f6
+project_name: my-app
+---
+
+# Prefer Functional Style
+
+## Action
+Use functional patterns over classes.
+```
+
+## Flags
+
+- `--domain <name>`: Export only specified domain
+- `--min-confidence <n>`: Minimum confidence threshold
+- `--output <file>`: Output file path (prints to stdout when omitted)
+- `--scope <project|global|all>`: Export scope (default: `all`)

package/.agent/workflows/instinct-import.md

@@ -1,114 +1,114 @@
----
-name: instinct-import
-description: Import instincts from file or URL into project/global scope
-command: true
----
-
-# Instinct Import Command
-
-## Implementation
-
-Run the instinct CLI using the plugin root path:
-
-```bash
-python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" import <file-or-url> [--dry-run] [--force] [--min-confidence 0.7] [--scope project|global]
-```
-
-Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
-
-```bash
-python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url>
-```
-
-Import instincts from local file paths or HTTP(S) URLs.
-
-## Usage
-
-```
-/instinct-import team-instincts.yaml
-/instinct-import https://github.com/org/repo/instincts.yaml
-/instinct-import team-instincts.yaml --dry-run
-/instinct-import team-instincts.yaml --scope global --force
-```
-
-## What to Do
-
-1. Fetch the instinct file (local path or URL)
-2. Parse and validate the format
-3. Check for duplicates with existing instincts
-4. Merge or add new instincts
-5. Save to inherited instincts directory:
-   - Project scope: `~/.claude/homunculus/projects/<project-id>/instincts/inherited/`
-   - Global scope: `~/.claude/homunculus/instincts/inherited/`
-
-## Import Process
-
-```
- Importing instincts from: team-instincts.yaml
-================================================
-
-Found 12 instincts to import.
-
-Analyzing conflicts...
-
-## New Instincts (8)
-These will be added:
-  ✓ use-zod-validation (confidence: 0.7)
-  ✓ prefer-named-exports (confidence: 0.65)
-  ✓ test-async-functions (confidence: 0.8)
-  ...
-
-## Duplicate Instincts (3)
-Already have similar instincts:
-  WARNING: prefer-functional-style
-     Local: 0.8 confidence, 12 observations
-     Import: 0.7 confidence
-     → Keep local (higher confidence)
-
-  WARNING: test-first-workflow
-     Local: 0.75 confidence
-     Import: 0.9 confidence
-     → Update to import (higher confidence)
-
-Import 8 new, update 1?
-```
-
-## Merge Behavior
-
-When importing an instinct with an existing ID:
-- Higher-confidence import becomes an update candidate
-- Equal/lower-confidence import is skipped
-- User confirms unless `--force` is used
-
-## Source Tracking
-
-Imported instincts are marked with:
-```yaml
-source: inherited
-scope: project
-imported_from: "team-instincts.yaml"
-project_id: "a1b2c3d4e5f6"
-project_name: "my-project"
-```
-
-## Flags
-
-- `--dry-run`: Preview without importing
-- `--force`: Skip confirmation prompt
-- `--min-confidence <n>`: Only import instincts above threshold
-- `--scope <project|global>`: Select target scope (default: `project`)
-
-## Output
-
-After import:
-```
-PASS: Import complete!
-
-Added: 8 instincts
-Updated: 1 instinct
-Skipped: 3 instincts (equal/higher confidence already exists)
-
-New instincts saved to: ~/.claude/homunculus/instincts/inherited/
-
-Run /instinct-status to see all instincts.
-```
+---
+name: instinct-import
+description: Import instincts from file or URL into project/global scope
+command: true
+---
+
+# Instinct Import Command
+
+## Implementation
+
+Run the instinct CLI using the plugin root path:
+
+```bash
+python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" import <file-or-url> [--dry-run] [--force] [--min-confidence 0.7] [--scope project|global]
+```
+
+Or if `CLAUDE_PLUGIN_ROOT` is not set (manual installation):
+
+```bash
+python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url>
+```
+
+Import instincts from local file paths or HTTP(S) URLs.
+
+## Usage
+
+```
+/instinct-import team-instincts.yaml
+/instinct-import https://github.com/org/repo/instincts.yaml
+/instinct-import team-instincts.yaml --dry-run
+/instinct-import team-instincts.yaml --scope global --force
+```
+
+## What to Do
+
+1. Fetch the instinct file (local path or URL)
+2. Parse and validate the format
+3. Check for duplicates with existing instincts
+4. Merge or add new instincts
+5. Save to inherited instincts directory:
+   - Project scope: `~/.claude/homunculus/projects/<project-id>/instincts/inherited/`
+   - Global scope: `~/.claude/homunculus/instincts/inherited/`
+
+## Import Process
+
+```
+ Importing instincts from: team-instincts.yaml
+================================================
+
+Found 12 instincts to import.
+
+Analyzing conflicts...
+
+## New Instincts (8)
+These will be added:
+  ✓ use-zod-validation (confidence: 0.7)
+  ✓ prefer-named-exports (confidence: 0.65)
+  ✓ test-async-functions (confidence: 0.8)
+  ...
+
+## Duplicate Instincts (3)
+Already have similar instincts:
+  WARNING: prefer-functional-style
+     Local: 0.8 confidence, 12 observations
+     Import: 0.7 confidence
+     → Keep local (higher confidence)
+
+  WARNING: test-first-workflow
+     Local: 0.75 confidence
+     Import: 0.9 confidence
+     → Update to import (higher confidence)
+
+Import 8 new, update 1?
+```
+
+## Merge Behavior
+
+When importing an instinct with an existing ID:
+- Higher-confidence import becomes an update candidate
+- Equal/lower-confidence import is skipped
+- User confirms unless `--force` is used
+
+## Source Tracking
+
+Imported instincts are marked with:
+```yaml
+source: inherited
+scope: project
+imported_from: "team-instincts.yaml"
+project_id: "a1b2c3d4e5f6"
+project_name: "my-project"
+```
+
+## Flags
+
+- `--dry-run`: Preview without importing
+- `--force`: Skip confirmation prompt
+- `--min-confidence <n>`: Only import instincts above threshold
+- `--scope <project|global>`: Select target scope (default: `project`)
+
+## Output
+
+After import:
+```
+PASS: Import complete!
+
+Added: 8 instincts
+Updated: 1 instinct
+Skipped: 3 instincts (equal/higher confidence already exists)
+
+New instincts saved to: ~/.claude/homunculus/instincts/inherited/
+
+Run /instinct-status to see all instincts.
+```