skillwiki 0.9.0 → 0.9.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "type": "module",
   "bin": {
     "skillwiki": "dist/cli.js"

package/skills/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "skills": "./",
   "description": "Project-aware Karpathy-style knowledge base for Claude Code: 18 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI.",
   "author": {

package/skills/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Project-aware Karpathy-style knowledge base for Codex with 18 prompt-only skills backed by the deterministic skillwiki CLI.",
   "author": {
     "name": "karlorz",

package/skills/agents/wiki-adapter-prd.md

@@ -36,7 +36,7 @@ You are a PRD format adapter specializing in mapping foreign design document for
 | Requirements list | `concepts/` or `entities/` |
 | Architecture decisions | `concepts/` with `tags: [architecture]` |
 | Motivation / context | `entities/` |
-| Trade-offs / comparisons | `comparisons/` |
+| Trade-offs / comparisons | `comparisons/` with a `Decision Closeout` block |
 | Action items / next steps | Skip (project management, not knowledge) |
 
 **Execution Process:**
@@ -51,6 +51,15 @@ You are a PRD format adapter specializing in mapping foreign design document for
    - `## TL;DR` as first section
    - Preserve requirement IDs as tags or inline references
    - Convert internal links to `[[wikilinks]]` where pages exist
+   - For generated comparison or evaluation pages, end with:
+     ```markdown
+     ## Decision Closeout
+
+     Disposition: no-op | concept | ADR | work-item | evidence-needed
+     Reason: ...
+     Follow-up: ...
+     ```
+     Use exactly one disposition. Keep skipped action items out of typed knowledge unless the closeout disposition is `work-item`.
 7. **Validate.** `skillwiki validate <page>` for each page. If any non-zero, STOP.
 8. **Apply writes:** raw → pages → `index.md` → `log.md`.
 

package/skills/agents/wiki-crystallize.md

@@ -32,6 +32,15 @@ You are a knowledge crystallizer specializing in distilling raw session material
    - Citations using `^[raw/...]` markers for every factual claim
    - For pages tagged `architecture` or explaining workflows: a Mermaid diagram (`graph TB` or `sequenceDiagram`)
    - Tags must come from `{vault}/SCHEMA.md` taxonomy only. If no relevant tag exists, use `[dev-loop]`.
+   - For `comparison`, evaluation-style `query`, or research-summary pages, end with:
+     ```markdown
+     ## Decision Closeout
+
+     Disposition: no-op | concept | ADR | work-item | evidence-needed
+     Reason: ...
+     Follow-up: ...
+     ```
+     Use exactly one disposition. Keep this as a prompt/template convention, not validation or lint enforcement.
 6. **Validate.** Run `skillwiki validate <page>`. If non-zero, fix issues and re-validate. Do NOT proceed until validation passes.
 7. **Apply writes in order:** Page file → add entry to `{vault}/index.md` → append entry to `{vault}/log.md`.
 

package/skills/agents/wiki-ingest.md

@@ -34,6 +34,15 @@ You are a vault ingestion specialist converting source material (URLs, files, te
    - `^[raw/...]` citations for every factual claim
    - Mermaid diagram if tagged `architecture` or explaining workflows
    - `confidence: low` if only one source cited
+   - For generated `comparisons/` pages or evaluation-style `queries/` pages, end with:
+     ```markdown
+     ## Decision Closeout
+
+     Disposition: no-op | concept | ADR | work-item | evidence-needed
+     Reason: ...
+     Follow-up: ...
+     ```
+     Use exactly one disposition. This is a prompt convention, not a validator rule.
 6. **Validate.** For each page: `skillwiki validate <page>`. If any non-zero, fix issues and re-validate. Do NOT proceed until all pages pass.
 7. **Apply writes in order:** raw file(s) → page(s) → update `index.md` → append `log.md`.
 

package/skills/agents/wiki-query.md

@@ -34,7 +34,15 @@ You are a vault search and synthesis specialist using E2 4-signal ranking to fin
    - Type affinity: 1.0×
 6. **Read top candidates.** Read frontmatter + body of highest-scored pages.
 7. **Synthesize answer.** Compose with explicit citations to candidate pages using `^[page-path]` markers.
-8. **Optional file.** If the task asks to persist: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` → `log.md`.
+8. **Optional file.** If the task asks to persist: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` → `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
+   ```markdown
+   ## Decision Closeout
+
+   Disposition: no-op | concept | ADR | work-item | evidence-needed
+   Reason: ...
+   Follow-up: ...
+   ```
+   Use exactly one disposition. This is a prompt convention only; do not add CLI enforcement here.
 
 ### Verification Rule
 When a wiki page (especially a work item tasks.md) claims fixes were applied or features completed, **verify on disk before accepting**. Check file existence, grep config, inspect crontab. The filesystem is the source of truth — wiki pages can drift.

package/skills/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skillwiki/skills",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "private": true,
   "files": [
     "wiki-*",

package/skills/skills/wiki-adapter-prd/SKILL.md

@@ -48,7 +48,7 @@ Map source sections to typed-knowledge pages:
 | Requirements list | `concepts/` or `entities/` | Each major requirement becomes its own page or a section in a compound page |
 | Architecture decisions | `concepts/` | Map to concept pages with `tags: [architecture]` |
 | Motivation / context | `entities/` | Capture as entity pages describing the system or component |
-| Trade-offs / comparisons | `comparisons/` | Create comparison pages when the source weighs alternatives |
+| Trade-offs / comparisons | `comparisons/` | Create comparison pages when the source weighs alternatives; include a `Decision Closeout` block |
 | Action items / next steps | Skip | Not knowledge — track in project work items instead |
 
 ### Cross-reference handling
@@ -65,6 +65,15 @@ Map source sections to typed-knowledge pages:
 3. Write raw capture: frontmatter + full body → `raw/articles/<slug>.md`.
 4. Run `skillwiki hash <raw-file>`, embed sha256.
 5. Generate typed-knowledge pages following the mapping strategy.
+   For generated comparison or evaluation pages, end the body with:
+   ```markdown
+   ## Decision Closeout
+
+   Disposition: no-op | concept | ADR | work-item | evidence-needed
+   Reason: ...
+   Follow-up: ...
+   ```
+   Use exactly one disposition. Preserve action items as skipped project-management content unless the closeout explicitly says `work-item`.
 6. For each page: run `skillwiki validate <page>`. If any fails, STOP.
 7. Write pages, then update `index.md` and `log.md`.
 

package/skills/skills/wiki-crystallize/SKILL.md

@@ -17,6 +17,15 @@ Standard four reads. If cwd is inside `projects/{slug}/`, also read project READ
 3. Compose the page with citations pre-attached. Reuse existing `raw/` sources where possible. Every page MUST include:
 - `> **TL;DR:**` blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md `## TL;DR Convention`.
 - For pages tagged `architecture` or explaining workflows/systems: include a Mermaid diagram (`graph TB` or `sequenceDiagram`) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md `## Mermaid Diagrams`).
+For `comparison`, evaluation-style `query`, or research-summary pages, end the body with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. Keep this as a prompt/template convention; do not add validation or lint enforcement.
 4. `skillwiki validate <page>`. If non-zero, STOP.
 5. Apply writes: page → `index.md` → `log.md`.
 ## Stop conditions

package/skills/skills/wiki-ingest/SKILL.md

@@ -23,6 +23,15 @@ Run `skillwiki lang` at the start. Generate page-body prose, narrative sections,
 5. **Generate page(s).** Compose typed-knowledge page(s) with citations pre-attached (`^[raw/...]` markers). Every page MUST include:
 - `> **TL;DR:**` blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md `## TL;DR Convention`.
 - For pages tagged `architecture` or explaining workflows/systems: include a Mermaid diagram (`graph TB` or `sequenceDiagram`) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md `## Mermaid Diagrams`).
+For generated `comparisons/` pages or evaluation-style `queries/` pages, end the body with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. Keep this as a prompt convention, not a validator rule.
 6. **Validate.** For each generated page: run `skillwiki validate <page>`. If exit ≠ 0, STOP — do not write index/log.
 7. **Apply writes in order.** raw → page(s) → `index.md` → `log.md`.
 8. **Confidence flag.** If only one source is cited, set `confidence: low`.

package/skills/skills/wiki-query/SKILL.md

@@ -22,7 +22,15 @@ Standard four reads (SCHEMA, index, log, project context if applicable).
 - Type affinity: 1.0×
 5. **Read top candidates** in full (frontmatter + body).
 6. **Synthesize answer** with explicit citations to the candidate pages.
-7. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`.
+7. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. This is a prompt convention only; do not add CLI enforcement here.
 ## Stop conditions
 - Zero matching pages.
 - User declines to file.

package/skills/wiki-adapter-prd/SKILL.md

@@ -48,7 +48,7 @@ Map source sections to typed-knowledge pages:
 | Requirements list | `concepts/` or `entities/` | Each major requirement becomes its own page or a section in a compound page |
 | Architecture decisions | `concepts/` | Map to concept pages with `tags: [architecture]` |
 | Motivation / context | `entities/` | Capture as entity pages describing the system or component |
-| Trade-offs / comparisons | `comparisons/` | Create comparison pages when the source weighs alternatives |
+| Trade-offs / comparisons | `comparisons/` | Create comparison pages when the source weighs alternatives; include a `Decision Closeout` block |
 | Action items / next steps | Skip | Not knowledge — track in project work items instead |
 
 ### Cross-reference handling
@@ -65,6 +65,15 @@ Map source sections to typed-knowledge pages:
 3. Write raw capture: frontmatter + full body → `raw/articles/<slug>.md`.
 4. Run `skillwiki hash <raw-file>`, embed sha256.
 5. Generate typed-knowledge pages following the mapping strategy.
+   For generated comparison or evaluation pages, end the body with:
+   ```markdown
+   ## Decision Closeout
+
+   Disposition: no-op | concept | ADR | work-item | evidence-needed
+   Reason: ...
+   Follow-up: ...
+   ```
+   Use exactly one disposition. Preserve action items as skipped project-management content unless the closeout explicitly says `work-item`.
 6. For each page: run `skillwiki validate <page>`. If any fails, STOP.
 7. Write pages, then update `index.md` and `log.md`.
 

package/skills/wiki-crystallize/SKILL.md

@@ -17,6 +17,15 @@ Standard four reads. If cwd is inside `projects/{slug}/`, also read project READ
 3. Compose the page with citations pre-attached. Reuse existing `raw/` sources where possible. Every page MUST include:
 - `> **TL;DR:**` blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md `## TL;DR Convention`.
 - For pages tagged `architecture` or explaining workflows/systems: include a Mermaid diagram (`graph TB` or `sequenceDiagram`) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md `## Mermaid Diagrams`).
+For `comparison`, evaluation-style `query`, or research-summary pages, end the body with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. Keep this as a prompt/template convention; do not add validation or lint enforcement.
 4. `skillwiki validate <page>`. If non-zero, STOP.
 5. Apply writes: page → `index.md` → `log.md`.
 ## Stop conditions

package/skills/wiki-ingest/SKILL.md

@@ -23,6 +23,15 @@ Run `skillwiki lang` at the start. Generate page-body prose, narrative sections,
 5. **Generate page(s).** Compose typed-knowledge page(s) with citations pre-attached (`^[raw/...]` markers). Every page MUST include:
 - `> **TL;DR:**` blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md `## TL;DR Convention`.
 - For pages tagged `architecture` or explaining workflows/systems: include a Mermaid diagram (`graph TB` or `sequenceDiagram`) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md `## Mermaid Diagrams`).
+For generated `comparisons/` pages or evaluation-style `queries/` pages, end the body with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. Keep this as a prompt convention, not a validator rule.
 6. **Validate.** For each generated page: run `skillwiki validate <page>`. If exit ≠ 0, STOP — do not write index/log.
 7. **Apply writes in order.** raw → page(s) → `index.md` → `log.md`.
 8. **Confidence flag.** If only one source is cited, set `confidence: low`.

package/skills/wiki-query/SKILL.md

@@ -22,7 +22,15 @@ Standard four reads (SCHEMA, index, log, project context if applicable).
 - Type affinity: 1.0×
 5. **Read top candidates** in full (frontmatter + body).
 6. **Synthesize answer** with explicit citations to the candidate pages.
-7. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`.
+7. **Optional file.** If user accepts: write to `queries/<slug>.md` or `comparisons/<slug>.md` with full frontmatter, validate, then update `index.md` then `log.md`. If the filed page is a research/evaluation answer, recommendation, or comparison, end it with:
+```markdown
+## Decision Closeout
+
+Disposition: no-op | concept | ADR | work-item | evidence-needed
+Reason: ...
+Follow-up: ...
+```
+Use exactly one disposition. This is a prompt convention only; do not add CLI enforcement here.
 ## Stop conditions
 - Zero matching pages.
 - User declines to file.