skillwiki 0.2.1-beta.2 → 0.2.1-beta.3

package/package.json

@@ -1,7 +1,6 @@
 {
   "name": "skillwiki",
-  "version": "0.2.1-beta.2",
-  "version": "0.2.1-beta.2",
+  "version": "0.2.1-beta.3",
   "type": "module",
   "bin": {
     "skillwiki": "dist/cli.js"

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

@@ -1,9 +1,8 @@
 {
   "name": "skillwiki",
-  "version": "0.2.1-beta.2",
-  "version": "0.2.1-beta.2",
+  "version": "0.2.1-beta.3",
   "skills": "./",
-  "description": "Project-aware Karpathy-style knowledge base for Claude Code: 11 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI (8 subcommands, JSON-by-default).",
+  "description": "Project-aware Karpathy-style knowledge base for Claude Code: 15 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI.",
   "author": {
     "name": "karlorz",
     "url": "https://github.com/karlorz"

package/skills/package.json

@@ -1,7 +1,6 @@
 {
   "name": "@skillwiki/skills",
-  "version": "0.2.1-beta.2",
-  "version": "0.2.1-beta.2",
+  "version": "0.2.1-beta.3",
   "private": true,
   "files": [
     "wiki-*",

package/skills/using-skillwiki/SKILL.md

@@ -20,6 +20,7 @@ Invoke a skillwiki skill when the user:
 - Wants a health check or lint on their vault
 - Mentions crystallizing a session into a note
 - Talks about project workspaces, ADRs, or distillation
+- Wants to quickly capture an idea, bug, task, or note without interrupting their workflow
 - Wants to archive or clean up old vault pages
 - Needs to detect source drift or re-ingest updated content
 - Has a spec/plan in a non-skillwiki format (CodeStable, RFC, AIDE)
@@ -27,15 +28,15 @@ Invoke a skillwiki skill when the user:
 
 ## Vault Structure
 
-A skillwiki vault has two layers:
+A skillwiki vault has three layers. The canonical architecture lives in `SCHEMA.md` at the vault root — read it before creating any new directories.
 
-**Layer 1 — Raw (`raw/`):** Immutable source material. Never modify after ingest.
+**Layer 1 — Raw (`raw/`):** Immutable source material. Never modify after ingest. `raw/transcripts/` doubles as the ad-hoc capture point for meeting notes and unprocessed ideas.
 
 ```
 raw/
 ├── articles/    # Web articles, clippings
 ├── papers/      # PDFs, arxiv papers
-├── transcripts/ # Meeting notes, interviews
+├── transcripts/ # Meeting notes, interviews, ad-hoc captures
 └── assets/      # Images, diagrams referenced by sources
 ```
 
@@ -48,7 +49,11 @@ sha256:          # computed by skillwiki hash over body bytes after closing ---
 ---
 ```
 
-**Layer 2 — Agent-owned pages:** `entities/`, `concepts/`, `comparisons/`, `queries/`, `meta/`, `projects/`. Citations use `^[raw/articles/source-file.md]` markers at paragraph-end.
+**Layer 2 — Typed Knowledge:** `entities/`, `concepts/`, `comparisons/`, `queries/`, `meta/`. Agent-owned pages with `^[raw/...]` citation markers at paragraph-end. Global scope — project association via `provenance_projects:` frontmatter, not directory nesting.
+
+**Layer 3 — Project Workspaces (`projects/{slug}/`):** Per-project lifecycle directories with `work/` (spec + plan + retro), `compound/` (distilled lessons/patterns), `architecture/` (ADRs), and `history/` (archived specs/plans).
+
+**No `inbox/` directory.** Ad-hoc captures go to `raw/transcripts/` or directly into a project work item via `proj-work`. Do not invent new top-level directories — extend Layer 2 via SCHEMA.md tag taxonomy if needed.
 
 ## Skill Map
 
@@ -62,6 +67,7 @@ sha256:          # computed by skillwiki hash over body bytes after closing ---
 | `wiki-audit` | Verify raw provenance references and source frontmatter integrity |
 | `wiki-archive` | Archive a typed-knowledge page — move to `_archive/`, remove from index |
 | `wiki-reingest` | Detect drift in raw sources (sha256 comparison) and re-ingest updated content |
+| `wiki-add-task` | Quick-capture ideas, bugs, tasks, notes into `raw/transcripts/` without leaving the current workflow |
 | `wiki-adapter-prd` | Map foreign PRD formats (CodeStable, RFC, AIDE, Hermes) into vault pages |
 | `proj-init` | Bootstrap a project workspace (README, requirements, architecture) |
 | `proj-work` | Open or run a work item under a project's work/ directory |

package/skills/wiki-add-task/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: wiki-add-task
+description: Capture ad-hoc ideas, bugs, tasks, or notes into the vault without leaving the current workflow.
+---
+
+# wiki-add-task
+
+Quick-capture skill for ad-hoc ideas, bugs, tasks, and notes. Writes directly to `raw/transcripts/` — the vault's designated ad-hoc capture point (Layer 1). No new directories or inbox folders needed.
+
+## When This Skill Activates
+
+- User wants to quickly jot down an idea, bug, task, or note without interrupting their current workflow.
+- User says "add task", "capture this", "note this", "remember this", "log this idea", or similar.
+- User provides a short text description and optionally a type tag.
+
+## Output language
+
+Run `skillwiki lang` at the start. Entry prose and `--human` summaries use the resolved language. Frontmatter keys, file names, and structural markers stay English.
+
+## Steps
+
+0. **Resolve vault and language.** Run `skillwiki path` (fail if NO_VAULT_CONFIGURED) and `skillwiki lang`.
+1. **Parse arguments.** Extract from the user's message:
+   - `text` — the idea/bug/task/note content (required)
+   - `type` — one of: `idea`, `bug`, `task`, `note` (default: `idea`)
+   - `project` — optional project slug to cross-reference (e.g., `llm-wiki`)
+2. **Determine target file.** The capture file is `raw/transcripts/YYYY-MM-DD-ad-hoc-captures.md` where YYYY-MM-DD is today's date. If the file exists, append; otherwise create it with standard raw frontmatter.
+3. **Write the entry.** Append to the capture file:
+   ```markdown
+   ### HH:MM — [type]
+
+   [text]
+
+   <!---meta: {"captured_at": "YYYY-MM-DDTHH:MM:SS", "type": "[type]"}--->
+   ```
+   - Use 24-hour time for HH:MM.
+   - Do not overwrite or modify existing entries.
+4. **Cross-reference (optional).** If a `project` slug was provided:
+   - Check that `projects/{slug}/` exists in the vault.
+   - Append a one-line reference to the project's work log or compound notes:
+     `- [YYYY-MM-DD] capture: [text] → raw/transcripts/YYYY-MM-DD-ad-hoc-captures.md`
+   - Do NOT create a full work item (that's `proj-work`'s job).
+5. **Update log.md.** Append: `## [YYYY-MM-DD] capture | [type]: [text (first 60 chars)]`
+6. **Confirm to user.** Report what was captured and where. Suggest next steps:
+   - If `type: idea` → "Consider ingesting related sources to develop this idea."
+   - If `type: bug` → "Use proj-work to create a bug-fix work item."
+   - If `type: task` → "Use proj-work to track this task through the dev loop."
+   - If `type: note` → "Will be available for future wiki-query searches."
+
+## Ad-hoc captures file format
+
+The file `raw/transcripts/YYYY-MM-DD-ad-hoc-captures.md` is a standard raw source with frontmatter:
+
+```yaml
+---
+source_url:
+ingested: YYYY-MM-DD
+sha256:
+---
+```
+
+The `sha256` is computed over the body after the closing `---`. On each append, recompute and update `sha256`. This keeps source-drift detection functional even though the file grows throughout the day.
+
+## Stop conditions
+
+- `skillwiki path` returns NO_VAULT_CONFIGURED.
+- No `text` provided (prompt user once, then stop).
+
+## Forbidden
+
+- Creating an `inbox/` directory. All captures go to `raw/transcripts/`.
+- Modifying existing entries in the captures file — only append.
+- Creating a work item — this is capture-only. Use `proj-work` for full work items.
+- Writing to any Layer 2 or Layer 3 location. Captures are Layer 1 (raw).