@meyverick/agentic 5.0.2

package/skills/openspec-report/evals/benchmark.json

@@ -0,0 +1,44 @@
+{
+  "skill": "opsx-report",
+  "generated": {
+    "by": "process:compute-benchmark/1.0",
+    "at": "2026-08-23T12:42:46Z"
+  },
+  "stage": "behavioral",
+  "structural": {
+    "validate_structure": {
+      "pass": true,
+      "warnings": [
+        "Missing scripts/ directory",
+        "Missing references/ directory"
+      ]
+    },
+    "validate_routing": {
+      "checks_total": 6,
+      "positive_triggers": 3,
+      "anti_triggers": 2,
+      "description_body_alignment": "9/10 description keywords found in body (90% alignment)",
+      "single_responsibility": true
+    },
+    "evals": {
+      "count": 3,
+      "assertions": 7,
+      "anti_trigger_coverage": true
+    }
+  },
+  "behavioral_dxm": "1×0.33",
+  "ship_gate": {
+    "criterion": "d = +1 and m >= 0.2",
+    "applies_to": "behavioral stage"
+  },
+  "behavioral": {
+    "at": "2026-09-12T09:38:54.074Z",
+    "evals": 4,
+    "assertions": 9,
+    "baseline": 0.5556,
+    "with_skill": 0.8889,
+    "d": 1,
+    "m": 0.3333,
+    "ship": "pass"
+  }
+}

package/skills/openspec-report/evals/evals.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "opsx-report",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Generate a report from the archived change fix-auth-gate.",
+      "expected_output": "Agent loads the opsx-report skill, locates the archived change under openspec/changes/archive/, and generates report.md following the report.md.template section structure (What Happened, What I Learned, What I'd Do Differently, Key Decisions, Trade-offs Made, Follow-ups, Archive Reference).",
+      "files": [],
+      "assertions": [
+        "Skill activates on report-generation request",
+        "Generated report follows template section structure",
+        "Report references the archive path of the named change"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Analyze the reports in ./openspec/reports/ and improve our skills based on them.",
+      "expected_output": "Agent does NOT activate opsx-report. This is an analysis/improvement request handled by the opsx-learn skill; opsx-report only generates self-reflection reports from archived changes.",
+      "files": [],
+      "assertions": [
+        "Anti-trigger fires: request must route to opsx-learn, not opsx-report",
+        "No report generation attempted"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Create a report for the simplify-main-overlay change.",
+      "expected_output": "Generated report is a self-reflection (meditation) referencing openspec/changes/archive/<date>-simplify-main-overlay/ — it summarizes and links to archive artifacts rather than copying their content wholesale.",
+      "files": [],
+      "assertions": [
+        "Report contains an Archive Reference section with location",
+        "Report content is reflection (lessons, decisions, trade-offs), not artifact duplication"
+      ]
+    },
+    {
+      "id": 4,
+      "prompt": "I want to explore whether we should use Redis or Postgres for session storage.",
+      "expected_output": "Agent does NOT activate openspec-report. This is an open-ended exploration request handled by openspec-explore; openspec-report only reflects on completed/archived changes.",
+      "files": [],
+      "assertions": [
+        "Anti-trigger fires: request routes to openspec-explore, not openspec-report",
+        "No report generation attempted"
+      ]
+    }
+  ]
+}

package/skills/qmd-research/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: qmd-research
+description: >
+  Research project knowledge, specifications, and architecture using the
+  project-local QMD index and maintain index collections. Use when searching
+  project markdown, researching specifications or past reports, or managing
+  local QMD index collections and embeddings. Do NOT use when looking up exact
+  file paths, symbols, or code lines (use grep or Read), or creating a new change.
+allowed-tools: Bash(qmd:*)
+license: MIT
+compatibility: Requires qmd CLI and local .qmd index.
+metadata:
+  author: agentic
+  version: "1.0.0"
+positive_triggers:
+  - "research project specifications and architecture with qmd"
+  - "search project documentation and past reports conceptually"
+  - "manage and update local qmd collections and embeddings"
+anti_triggers:
+  - "look up exact file path or code symbol"
+  - "grep exact string in source code"
+---
+
+# QMD Research
+
+Research project knowledge bases and manage project-local QMD index collections.
+
+## Activation Boundary
+
+- **Use when:** Searching project documentation, researching specifications, exploring past change reports, or managing the project-local index and embeddings.
+- **Do NOT use when:** Locating exact file paths, line numbers, headings, or code symbols (use `grep` and `Read` instead); or executing code implementations.
+
+## Project-Local Index Law
+
+- **Strict Project Locality:** All index operations bind strictly to the project repository root (`<repo>/.qmd/index.sqlite`, gitignored).
+- **No Global Indexing:** NEVER create, populate, query, or fall back to a global or shared index (such as `~/.qmd`).
+- **Initialization:** When `.qmd/` is missing during a task, run `qmd init` at the repository root before querying.
+
+## Read Path
+
+### Mode Selection
+
+- **Exact Terms & Symbols:** Keyword search via BM25 (no LLM latency):
+  ```bash
+  qmd search '"<exact phrase>"' --json -n 10 -c <collection>
+  ```
+- **Conceptual & Paraphrased Recall:** Multi-line query document authored by the agent:
+  ```bash
+  qmd query $'intent: <goal and concepts to avoid>\nlex: <lexical anchors>\nvec: <semantic paraphrase>' --json -n 10 -c <collection>
+  ```
+  Author the query fields deliberately from task context; never pass raw user text to bare `qmd query`.
+
+### Retrieval Discipline
+
+- **Retrieve Before Claiming:** Always fetch full document contents using `qmd get` or `qmd multi-get` before asserting facts:
+  ```bash
+  qmd get "#<docid>"
+  qmd multi-get "<docid1>,<docid2>" --json
+  ```
+- **Evidence Citation:** Cite the `#docid` or document path together with exact line numbers for any claim.
+- **Document Slicing:** Slice ranges using `qmd get "<path:from:count>"` or `-l <count>`, never by piping through `head`, `tail`, or `sed`.
+- **Collection Scoping:** Restrict queries to relevant collections using `-c <collection>` (e.g., `-c openspec`, `-c references`).
+
+## Mutation Path (Gated)
+
+Index mutations modify files and vector state. They are strictly gated:
+- **Available Mutations:** `qmd init`, `qmd collection add/remove/rename`, `qmd context add/rm`, `qmd embed`, `qmd update`, `qmd cleanup`.
+- **Explicit Gate:** Mutations SHALL run ONLY when the user explicitly requests index setup, collection updates, embedding refresh, or repairs.
+- **Never on Search:** Read-only searches MUST NOT invoke `collection`, `embed`, `update`, or `cleanup` as a side effect.
+- **Embedding Command:**
+  ```bash
+  qmd update && qmd embed --chunk-strategy auto
+  ```
+- **Health Inspection:**
+  ```bash
+  qmd status
+  ```
+
+## Gotchas and Anti-Examples
+
+- **Anti-Example (Bare Expand):** Do NOT run `qmd query "how does auth work"`. This delegates query expansion to the model. Instead author `intent:`, `lex:`, and `vec:` lines explicitly.
+- **Anti-Example (Output Piping):** Do NOT pipe `qmd get` into `grep`, `sed`, or `awk`. Use QMD's native `path:from:count` range slicing.
+- **Anti-Example (External Paths):** Do NOT add home-directory collections (`qmd collection add ~/docs`). All collection paths must reside inside the project tree.
+- **Loud Degradation:** If `qmd status` fails or daemon is absent, report that QMD is unavailable and note any `grep` fallback explicitly with retrieved evidence.
+
+## References
+
+- [references/query-craft.md](references/query-craft.md) — Query grammar, multi-line fusion, metadata AST filters, and worked examples.
+- [references/index-management.md](references/index-management.md) — Project-local initialization, collection management, context attachment, and maintenance.

package/skills/qmd-research/evals/benchmark.json

@@ -0,0 +1,40 @@
+{
+  "skill": "qmd-research",
+  "generated": {
+    "by": "process:structural-stage/1.0",
+    "at": "2026-09-12T11:38:00Z"
+  },
+  "stage": "behavioral",
+  "structural": {
+    "validate_structure": {
+      "pass": true,
+      "note": "recorded at apply gate (task 7.2)"
+    },
+    "validate_routing": {
+      "checks_total": 6,
+      "positive_triggers": 3,
+      "anti_triggers": 2,
+      "single_responsibility": true
+    },
+    "evals": {
+      "count": 3,
+      "assertions": 9,
+      "anti_trigger_coverage": true
+    }
+  },
+  "behavioral_dxm": "1×0.33",
+  "ship_gate": {
+    "criterion": "d = +1 and m >= 0.2",
+    "applies_to": "behavioral stage"
+  },
+  "behavioral": {
+    "at": "2026-09-12T09:39:58.960Z",
+    "evals": 3,
+    "assertions": 9,
+    "baseline": 0.5556,
+    "with_skill": 0.8889,
+    "d": 1,
+    "m": 0.3333,
+    "ship": "pass"
+  }
+}

package/skills/qmd-research/evals/evals.json

@@ -0,0 +1,38 @@
+{
+  "skill_name": "qmd-research",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Research the specifications and architecture regarding how submodule pointer sync is enforced.",
+      "expected_output": "Agent activates qmd-research, selects hybrid query mode with authored intent/lex/vec lines, retrieves relevant documents with qmd get, and cites docid and line numbers.",
+      "files": [],
+      "assertions": [
+        "Skill activates on conceptual research request",
+        "Mode selection authors intent and lexical/semantic lines",
+        "Claims cite retrieved docids with line numbers",
+        "No index mutation commands run"
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Find the exact definition of the function `writeProvenanceManifest` in `project/install.ts`.",
+      "expected_output": "Agent does NOT activate qmd-research. Exact symbol and file lookups are handled via grep or Read; qmd-research is for conceptual research and collection management.",
+      "files": [],
+      "assertions": [
+        "Anti-trigger fires: request routes to grep/Read, not qmd-research",
+        "No QMD queries executed for exact symbol lookup"
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "Search the archive reports for lessons learned about database migrations.",
+      "expected_output": "Agent runs read path using qmd query scoped to openspec collection, fetches document slices, and reports findings without executing index mutations.",
+      "files": [],
+      "assertions": [
+        "Search scoped with -c openspec",
+        "Document fetched before claiming",
+        "Mutation path remains gated (no embed, cleanup, or update executed)"
+      ]
+    }
+  ]
+}

package/skills/qmd-research/references/index-management.md

@@ -0,0 +1,69 @@
+# QMD Index Management & Maintenance Reference
+
+This reference documents project-local index initialization, collection configuration, context attachment, embedding updates, and troubleshooting.
+
+---
+
+## 1. Project-Local Index Lifecycle
+
+All index operations MUST remain strictly local to the repository root.
+
+```bash
+# Initialize project-local index (creates .qmd/index.sqlite, gitignored)
+qmd init
+
+# View health, document counts, and active collections
+qmd status
+```
+
+NEVER create or point to a global index under `~/.qmd`.
+
+---
+
+## 2. Managing Collections
+
+Collections group markdown files for scoped retrieval. All paths must be relative to the repository.
+
+```bash
+# Add a collection
+qmd collection add ./openspec/ --name openspec
+
+# Add context describing collection purpose
+qmd context add qmd://openspec/ "Active specifications, proposals, and change archives"
+
+# List collections and indexed files
+qmd collection list
+qmd ls openspec
+```
+
+---
+
+## 3. Maintenance & Embeddings
+
+When files change or after adding new documents, update the index:
+
+```bash
+# Re-index all collections
+qmd update
+
+# Generate or refresh vector embeddings with AST chunking
+qmd embed --chunk-strategy auto
+
+# Clean up orphaned chunks and vacuum SQLite database
+qmd cleanup
+```
+
+---
+
+## 4. Troubleshooting & Health
+
+### Missing or Stale Index
+If `qmd status` returns an error or reports stale documents:
+1. Verify `.qmd/index.sqlite` exists: `ls -la .qmd/`.
+2. Run `qmd init` if absent.
+3. Re-index and embed: `qmd update && qmd embed --chunk-strategy auto`.
+
+### Missing Daemon or QMD Binary
+If `qmd` is not in `$PATH` or fails to run:
+- Fall back loudly to `grep` for exact keyword searches.
+- State `qmd unavailable, grep fallback` in the proposal or summary.

package/skills/qmd-research/references/query-craft.md

@@ -0,0 +1,82 @@
+# QMD Query Craft & Syntax Reference
+
+This reference covers the structured query grammar, search mode selection, filtering AST, and practical examples across project corpora.
+
+---
+
+## 1. Query Grammar (`SYNTAX.md`)
+
+A QMD query is either a single expand query or a multi-line query document.
+
+```text
+query          = expand_query | query_document ;
+expand_query   = text | explicit_expand ;
+explicit_expand= "expand:" text ;
+query_document = [ intent_line ] { typed_line } ;
+intent_line    = "intent:" text newline ;
+typed_line     = type ":" text newline ;
+type           = "lex" | "vec" | "hyde" ;
+text           = quoted_phrase | plain_text ;
+```
+
+### Typed Lines Explained
+
+- **`intent:`**: High-level task definition. Explains what the agent is looking for and what nearby-but-wrong concepts to avoid. (Used by rerankers and candidate filtering).
+- **`lex:`**: Lexical / BM25 search. Supports exact quoted phrases (`"exact phrase"`), term negation (`-unwanted`), and keyword combinations.
+- **`vec:`**: Dense vector embedding search. Translates conceptual paraphrase into semantic embedding space.
+- **`hyde:`**: Hypothetical Document Embedding. A simulated passage answering the query to bridge vocabulary mismatch.
+
+---
+
+## 2. Mode Selection & Scoping
+
+| Goal | Mode | CLI Pattern | Latency |
+|---|---|---|---|
+| Exact symbol, path, title, heading | `qmd search` | `qmd search '"<term>"' -c <collection>` | Fast (~3ms) |
+| Conceptual / Paraphrased topic | `qmd query` (structured) | `qmd query $'intent: ...\nlex: ...\nvec: ...'` | Medium (~50-100ms) |
+| Multi-document evidence gathering | `qmd multi-get` | `qmd multi-get "<docid1>,<docid2>" --json` | Fast (<10ms) |
+
+### Scoping with `-c`
+
+Always constrain search to target collections:
+- `-c openspec`: Search specifications, active changes, and archived changes.
+- `-c references`: Search external documentation, framework guides, and specifications.
+- `-c pi-memory`: Search persistent session memory and daily developer notes.
+
+---
+
+## 3. Worked Examples on Project Corpora
+
+### Example 1: Finding an Architectural Specification
+
+Goal: Locate which capability specification governs submodule pointer sync.
+
+```bash
+qmd query $'intent: find the spec governing submodule pointer freshness and CI gates\nlex: "Submodule Pointer Sync" gitlink\nvec: committing updated submodule pointer in orchestrator' --json -n 5 -c openspec
+```
+
+### Example 2: Clustering Gotchas Across Archived Reports
+
+Goal: Find past reports encountering borrow-checker or lifetime fights.
+
+```bash
+qmd query $'intent: cluster recurring knowledge gaps across reports\nlex: "lifetime" "borrow" "clippy"\nvec: difficulties with rust borrow checker and reference lifetimes' --json -n 10 -c openspec
+```
+
+### Example 3: Searching Shipped Skill Patterns
+
+Goal: Inspect how validation loops are designed in existing skills.
+
+```bash
+qmd search '"validate-routing"' --json -n 5 -c references
+```
+
+---
+
+## 4. Retrieval Verification (`qmd bench`)
+
+Pin search quality benchmarks against a JSON fixture file:
+```bash
+qmd bench project/skills/openspec-learn/evals/retrieval-bench.json
+```
+Measures Precision@k, Recall@1/3/5, MRR, and latency across BM25, vector, hybrid, and full reranked backends.