skillwiki 0.10.47 → 0.10.49

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (17) hide show
  1. package/dist/{chunk-5JYOYMST.js → chunk-F7LXKP4T.js} +78 -1
  2. package/dist/{chunk-4SINVFR3.js → chunk-FXASPB3C.js} +84 -15
  3. package/dist/cli.js +283 -127
  4. package/dist/{managed-write-preflight-DWK3PJCO.js → managed-write-preflight-H7KVK2KI.js} +1 -1
  5. package/dist/skillwiki-mcp.js +2 -2
  6. package/package.json +1 -1
  7. package/skills/.claude-plugin/plugin.json +1 -1
  8. package/skills/.codex-plugin/plugin.json +1 -1
  9. package/skills/package.json +1 -1
  10. package/skills/proj-work/SKILL.md +8 -8
  11. package/skills/skills/proj-work/SKILL.md +8 -8
  12. package/skills/skills/using-skillwiki/SKILL.md +30 -20
  13. package/skills/skills/using-skillwiki/activation.md +2 -2
  14. package/skills/skills/wiki-gate-plan-mode/SKILL.md +8 -8
  15. package/skills/using-skillwiki/SKILL.md +30 -20
  16. package/skills/using-skillwiki/activation.md +2 -2
  17. package/skills/wiki-gate-plan-mode/SKILL.md +8 -8
package/dist/{managed-write-preflight-DWK3PJCO.js → managed-write-preflight-H7KVK2KI.js} RENAMED
@@ -2,7 +2,7 @@
2
2
  import {
3
3
  runManagedWritePreflight,
4
4
  runManagedWriteTransaction
5
- } from "./chunk-4SINVFR3.js";
5
+ } from "./chunk-FXASPB3C.js";
6
6
  import "./chunk-UHZBOOMK.js";
7
7
  import "./chunk-PLUHIOCQ.js";
8
8
  import "./chunk-EVQASYII.js";
package/dist/skillwiki-mcp.js CHANGED
@@ -1,10 +1,10 @@
1
1
  #!/usr/bin/env node
2
2
  import {
3
3
  runSkillwikiMcpStdio
4
- } from "./chunk-5JYOYMST.js";
4
+ } from "./chunk-F7LXKP4T.js";
5
5
  import "./chunk-7I2TPIV5.js";
6
6
  import "./chunk-GAU4D25O.js";
7
- import "./chunk-4SINVFR3.js";
7
+ import "./chunk-FXASPB3C.js";
8
8
  import "./chunk-UHZBOOMK.js";
9
9
  import "./chunk-PLUHIOCQ.js";
10
10
  import "./chunk-EVQASYII.js";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "skillwiki",
3
- "version": "0.10.47",
3
+ "version": "0.10.49",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "skillwiki": "dist/cli.js",
package/skills/.claude-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "skillwiki",
3
- "version": "0.10.47",
3
+ "version": "0.10.49",
4
4
  "skills": "./",
5
5
  "description": "Project-aware Karpathy-style knowledge base for Claude Code: 19 prompt-only skills (wiki-*, proj-*, using-skillwiki) backed by the deterministic `skillwiki` CLI.",
6
6
  "author": {
package/skills/.codex-plugin/plugin.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "skillwiki",
3
- "version": "0.10.47",
3
+ "version": "0.10.49",
4
4
  "description": "Project-aware Karpathy-style knowledge base for Codex with 19 prompt-only skills backed by the deterministic skillwiki CLI.",
5
5
  "author": {
6
6
  "name": "karlorz",
package/skills/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skillwiki/skills",
3
- "version": "0.10.47",
3
+ "version": "0.10.49",
4
4
  "private": true,
5
5
  "files": [
6
6
  "wiki-*",
package/skills/proj-work/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: proj-work
3
- description: Open or run a work item under projects/{slug}/work/YYYY-MM-DD-{slug}/. Redirects brainstorming/writing-plans output paths.
3
+ description: Open or run a work item under projects/{slug}/work/YYYY-MM-DD-{slug}/. Redirects brainstorming spec/plan output paths.
4
4
  ---
5
5
 
6
6
  # proj-work
@@ -22,7 +22,7 @@ install with `grok plugin update skillwiki`, not `skillwiki install`.
22
22
  ## When to invoke
23
23
  - User starts a feature, issue, refactor, or decision inside an existing project.
24
24
  - User asks to "get work of X" or "run work item Y" to review/execute an existing item.
25
- - Brainstorming or writing-plans skills would otherwise default-write outside the project tree.
25
+ - Brainstorming would otherwise default-write outside the project tree.
26
26
  - If no project context can be determined, default to the `playground` slug so redirect paths always emit and the PRD bridge chain works.
27
27
 
28
28
  ## Pre-orientation reads
@@ -59,14 +59,14 @@ After step 3 (output path override), emit redirect paths for the active PRD skil
59
59
  > spec -> <vault-root>/projects/{slug}/work/YYYY-MM-DD-{work-slug}/spec.md
60
60
  > plan -> <vault-root>/projects/{slug}/work/YYYY-MM-DD-{work-slug}/plan.md
61
61
  >
62
- > Pass these paths to your PRD skill (superpowers:brainstorming, superpowers:writing-plans,
63
- > CodeStable, or any other). Files land in the vault natively — no separate ingest needed.
64
-
65
62
  Rules:
66
- - Emit redirect paths as the first output after folder creation, before any PRD skill runs.
63
+ - Emit redirect paths as the first output after folder creation, before any spec write.
64
+ - After the folder exists, brainstorming writes `spec.md` at the spec redirect.
65
+ - Do not invoke `writing-plans`. Do not git commit from brainstorming.
66
+ - `plan.md` is a later explicit `proj-work` step, not a Superpowers plan file.
67
67
  - Resolve `<vault-root>` via `skillwiki path` (never hardcode).
68
- - proj-work does NOT invoke any PRD skill — it provides paths only.
69
- - If the PRD skill cannot accept custom save paths, fall back to manual `wiki-ingest`.
68
+ - proj-work does NOT invoke brainstorming — it provides paths only.
69
+ - If a foreign PRD skill cannot accept custom save paths, fall back to manual `wiki-ingest`.
70
70
  - When `spec.md` or `plan.md` mentions repo files, follow `using-skillwiki` → Portable Source References.
71
71
 
72
72
  ## Pitfalls
package/skills/skills/proj-work/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: proj-work
3
- description: Open or run a work item under projects/{slug}/work/YYYY-MM-DD-{slug}/. Redirects brainstorming/writing-plans output paths.
3
+ description: Open or run a work item under projects/{slug}/work/YYYY-MM-DD-{slug}/. Redirects brainstorming spec/plan output paths.
4
4
  ---
5
5
 
6
6
  # proj-work
@@ -22,7 +22,7 @@ install with `grok plugin update skillwiki`, not `skillwiki install`.
22
22
  ## When to invoke
23
23
  - User starts a feature, issue, refactor, or decision inside an existing project.
24
24
  - User asks to "get work of X" or "run work item Y" to review/execute an existing item.
25
- - Brainstorming or writing-plans skills would otherwise default-write outside the project tree.
25
+ - Brainstorming would otherwise default-write outside the project tree.
26
26
  - If no project context can be determined, default to the `playground` slug so redirect paths always emit and the PRD bridge chain works.
27
27
 
28
28
  ## Pre-orientation reads
@@ -59,14 +59,14 @@ After step 3 (output path override), emit redirect paths for the active PRD skil
59
59
  > spec -> <vault-root>/projects/{slug}/work/YYYY-MM-DD-{work-slug}/spec.md
60
60
  > plan -> <vault-root>/projects/{slug}/work/YYYY-MM-DD-{work-slug}/plan.md
61
61
  >
62
- > Pass these paths to your PRD skill (superpowers:brainstorming, superpowers:writing-plans,
63
- > CodeStable, or any other). Files land in the vault natively — no separate ingest needed.
64
-
65
62
  Rules:
66
- - Emit redirect paths as the first output after folder creation, before any PRD skill runs.
63
+ - Emit redirect paths as the first output after folder creation, before any spec write.
64
+ - After the folder exists, brainstorming writes `spec.md` at the spec redirect.
65
+ - Do not invoke `writing-plans`. Do not git commit from brainstorming.
66
+ - `plan.md` is a later explicit `proj-work` step, not a Superpowers plan file.
67
67
  - Resolve `<vault-root>` via `skillwiki path` (never hardcode).
68
- - proj-work does NOT invoke any PRD skill — it provides paths only.
69
- - If the PRD skill cannot accept custom save paths, fall back to manual `wiki-ingest`.
68
+ - proj-work does NOT invoke brainstorming — it provides paths only.
69
+ - If a foreign PRD skill cannot accept custom save paths, fall back to manual `wiki-ingest`.
70
70
  - When `spec.md` or `plan.md` mentions repo files, follow `using-skillwiki` → Portable Source References.
71
71
 
72
72
  ## Pitfalls
package/skills/skills/using-skillwiki/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: using-skillwiki
3
- description: Invoke at session start or when knowledge-base tasks arise — maps skillwiki skills, dev-loop alignment, adaptive workflow profiles, and vault routing
3
+ description: Invoke when vault, wiki, knowledge-base, or SkillWiki setup work arises — maps skillwiki skills, dev-loop alignment, adaptive workflow profiles, and vault routing. Do not invoke for unrelated coding or creative tasks.
4
4
  ---
5
5
  *Note: If executing as a background subagent, skip this skill section.*
6
6
 
@@ -30,19 +30,21 @@ Use this section as procedural planning guidelines:
30
30
 
31
31
  **Claude Code** and **Codex** activate SkillWiki via the plugin SessionStart hook (`hooks/session-start` / `hooks/session-start-codex`). Do **not** install activation markers into `~/.claude/CLAUDE.md` or `~/.codex/AGENTS.md` when the plugin is present — that double-injects context and pollutes user-scope instruction files.
32
32
 
33
- On harnesses where SessionStart `additionalContext` does **not** fire (**Grok**), SkillWiki activation context is delivered via a compact file. Run `npm run install:activation` from the repo to install:
33
+ On harnesses where SessionStart `additionalContext` does **not** fire (**Grok**), SkillWiki activation context is delivered via a compact file. Run `npm run install:activation` from the llm-wiki repo to install:
34
34
 
35
35
  - `~/.grok/skillwiki.md` — compact derivative covering identity, CLI probe, skill map, PRD bridge, fail-closed boundary, and drift warning.
36
- - `~/.grok/AGENTS.md` — prepended with a marker-wrapped reference: `Read @skillwiki.md for SkillWiki activation context.`
36
+ - `~/.grok/AGENTS.md` — prepended with a marker-wrapped reference: `Read @~/.grok/skillwiki.md for SkillWiki activation context.`
37
37
 
38
38
  Default install is **Grok only**. Re-running `install:activation` also **removes** any prior Claude/Codex activation marker and matching `skillwiki.md` (cleanup for the earlier dual-target installer). Opt-in fallbacks only when the plugin SessionStart path is unavailable:
39
39
 
40
- - `npm run install:activation -- --with-claude` — `~/.claude/skillwiki.md` + `CLAUDE.md` marker
41
- - `npm run install:activation -- --with-codex` — `~/.codex/skillwiki.md` + `AGENTS.md` marker
40
+ - `npm run install:activation -- --with-claude` — `~/.claude/skillwiki.md` + `CLAUDE.md` marker `Read @~/.claude/skillwiki.md …`
41
+ - `npm run install:activation -- --with-codex` — `~/.codex/skillwiki.md` + `AGENTS.md` marker `Read @~/.codex/skillwiki.md …`
42
42
 
43
- The activation file is self-contained literal text (ADR-3). On harnesses with `@file` import support, the reference is inlined automatically. On Grok (no `@file` support), the agent reads the file manually when it sees the instructional reference.
43
+ The activation file is self-contained literal text (ADR-3). On harnesses with `@file` import support, `@~/.grok/skillwiki.md` (or the Claude/Codex home path) is inlined. On Grok (no `@file` support), `read_file` the exact path `~/.grok/skillwiki.md`. Never `~/skillwiki.md`. Never a cwd-relative `skillwiki.md`. If that file is missing, say activation is absent and suggest `npm run install:activation` from the llm-wiki repo; do not create a home-level `skillwiki.md`.
44
44
 
45
- The template lives at `packages/skills/using-skillwiki/activation.md`. Run `npm run install:activation:check` to verify the Grok install matches the template and that Claude/Codex are not still carrying the activation block.
45
+ The compact `~/.grok/skillwiki.md` is the session-start context. This full skill is for vault/wiki/setup work only — do not load it at the start of an unrelated session.
46
+
47
+ The template lives at `packages/skills/using-skillwiki/activation.md`. Run `npm run install:activation:check` to verify the Grok install matches the template and that Claude/Codex are not still carrying the activation block. `skillwiki doctor` reports a warn on a missing file, a stale `@skillwiki.md` marker, or compact-file drift.
46
48
 
47
49
  ## When to Use These Skills
48
50
  Invoke a skillwiki skill when the user:
@@ -181,7 +183,7 @@ The vault is shared across hosts, so host-local absolute paths are not durable s
181
183
  | `wiki-sync` | Safely sync vault git repository — push/pull with lint guards and conflict resolution |
182
184
  | `wiki-canvas` | Generate Obsidian Canvas visualization from vault graph data |
183
185
  | `proj-decide` | Write an Architectural Decision Record (ADR) |
184
- | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating — force superpowers planning instead of built-in plan mode |
186
+ | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating — force brainstorming then proj-work instead of built-in plan mode |
185
187
  | `dev-loop:research` | Research agent for dev-loop IDLE — scans repo + vault health, outputs prioritized work-item recommendations (formerly `/dev-loop-research`) |
186
188
 
187
189
  ## dev-loop Alignment
@@ -224,7 +226,9 @@ for code changes.
224
226
 
225
227
  ## CLI Backbone
226
228
  All skills are backed by the `skillwiki` CLI — a deterministic tool with no LLM calls. It handles path resolution, config management, validation, health reporting, and linting. Skills invoke it via Bash for the mechanical parts and use the active agent for the creative parts.
227
- Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `query`, `sources pending`, `sources disposition`, `sources dispose`, `archive`, `remove`, `drift`, `dedup`, `compound`, `tag-sync`, `tag reconcile`, `page publish`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
229
+ Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `query`, `sources pending`, `sources disposition`, `sources dispose`, `archive`, `remove`, `drift`, `dedup`, `compound`, `tag-sync`, `tag reconcile`, `page publish`, `sync status`, `seed`, `stale`, `claim`, `claims audit`, `observe`, `canvas generate`.
230
+ `skillwiki claim` binds a transcript to a work item only through an exact `raw/transcripts/...` path in `source:` / `sources:` / `closes:`. A `--project` that contradicts the capture's explicit project is rejected. `skillwiki stale --project` uses exact normalized slugs, not substring matching. `skillwiki claims audit` is the read-only integrity report for duplicate, malformed, dangling, cross-project, and unbacked claims; it never rewrites captures or work items.
231
+
228
232
  Run `skillwiki health <vault> --out /tmp/skillwiki-health.json --no-fail` for a bounded whole-system report that includes the nonblocking source-lifecycle backlog. Pending captures are informational and do not make health fail. Run `skillwiki lint <vault> --summary` for lint-only bucket counts with capped examples and details commands. Run `skillwiki doctor` to diagnose setup/runtime issues only. Run `skillwiki config list` to see current configuration.
229
233
 
230
234
  ## Runtime Host Context and Fleet Freshness
@@ -298,15 +302,21 @@ skillwiki supports named wiki profiles for working with multiple vaults. Set `WI
298
302
  **Project-local override:** Place a `./skillwiki/.env` in a project root to bind that project to a specific wiki. Skills will use it automatically when running from that directory.
299
303
 
300
304
  ## PRD Bridge — Redirect Spec/Plan Output to Vault
301
- When skillwiki is installed, **all spec and plan documents must land in the vault**, not in repo-local directories like `docs/superpowers/`. This applies to PRD and TDD workflows (superpowers, codestable, AIDE, Hermes, manual templates).
302
- **Rule:** Before a PRD skill writes a spec or plan file, redirect its save path:
303
- 1. Resolve the vault path: `skillwiki path`
304
- 2. If the cwd is inside a project (check for `projects/{slug}/` via `skillwiki path --init-time` or look for `./skillwiki/.env`), use that project's work directory
305
- 3. Create or locate the work item via `proj-work`, which emits redirect paths for `spec.md` and `plan.md`
306
- 4. Pass those vault paths to the PRD/TDD skill as its save location
307
- **Concrete overrides for superpowers:**
308
- - `superpowers:brainstorming` step 6: override `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` → vault work-item `spec.md` path from `proj-work`
309
- - `superpowers:writing-plans` header: override `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md` → vault work-item `plan.md` path from `proj-work`
310
- Both skills say "User preferences for spec location override this default" — the vault work-item path IS the override. Apply the same override pattern to any TDD-oriented planner that emits spec/plan artifacts.
311
- **If no project context exists** (standalone vault, not inside a project), default to the `playground` project slug. Invoke `proj-work` with `playground` as the slug so redirect paths are emitted normally and the PRD bridge chain works. The `playground` project is a pre-initialized catch-all workspace at `projects/playground/` for exploratory work, experiments, and unclassified features. Work items that mature can be moved to a real project later.
305
+ When skillwiki is installed, **all spec and plan documents must land in the vault**, not in repo-local directories like `docs/superpowers/`. This applies to brainstorming, grill-me, and any foreign PRD template (CodeStable, AIDE, Hermes).
306
+
307
+ **Architectural brainstorming** (after the human approves the design):
308
+ 1. Resolve the vault path: `skillwiki path`.
309
+ 2. Invoke `proj-work` so the work folder exists. If cwd is inside `projects/{slug}/` (or `./skillwiki/.env` binds a project), use that slug. Otherwise use `playground`.
310
+ 3. Write `spec.md` only at the emitted redirect path.
311
+ 4. Do not invoke `writing-plans`.
312
+ 5. Do not git commit from brainstorming.
313
+ 6. `plan.md` is a later `proj-work` / explicit user step, not a Superpowers plan file.
314
+
315
+ If the work is UI (layout, mockup, component look, page structure), offer brainstorming `visual-companion.md` at the first UI question as its own message. Offer the companion once. The human may decline. Non-UI work never offers it. Do not auto-open.
316
+
317
+ **Bounded implementation:** after a bounded design is approved, TDD applies when standalone `test-driven-development` is installed. Do not require the Superpowers plugin.
318
+
319
+ **Foreign PRD skills** that still default to `docs/superpowers/specs/` or `docs/superpowers/plans/` must use the `proj-work` redirect paths instead. The vault work-item path is the user preference those skills honor.
320
+
321
+ The `playground` project at `projects/playground/` is the catch-all workspace when no project context exists. Work items that mature can move to a real project later.
312
322
  **Never create `docs/superpowers/` in any repo.**
package/skills/skills/using-skillwiki/activation.md CHANGED
@@ -28,7 +28,7 @@ Invoke a SkillWiki skill when the user: wants vault/wiki/knowledge-base operatio
28
28
  | `wiki-adapter-prd` | Map foreign PRD formats (CodeStable, RFC, AIDE, Hermes) |
29
29
  | `wiki-sync` | Safely sync vault git repository |
30
30
  | `wiki-canvas` | Generate Obsidian Canvas visualization |
31
- | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating for superpowers planning |
31
+ | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating for brainstorming then proj-work |
32
32
  | `proj-init` | Bootstrap a project workspace |
33
33
  | `proj-work` | Open or run a work item |
34
34
  | `proj-distill` | Distill project compound entries into concept pages |
@@ -37,7 +37,7 @@ Invoke a SkillWiki skill when the user: wants vault/wiki/knowledge-base operatio
37
37
 
38
38
  ## PRD Bridge
39
39
 
40
- Route PRD/spec/plan work to `wiki-adapter-prd` and `proj-work`, not `docs/superpowers/`. Spec and plan outputs must land in vault work-item paths. Never create `docs/superpowers/` in any repo.
40
+ After architectural design approval, invoke `proj-work` then write `spec.md` in that work folder. Do not invoke `writing-plans`. Do not git commit from brainstorming. Bounded TDD uses standalone `test-driven-development` when installed. For UI work, offer brainstorming `visual-companion.md` once (optional). Never create `docs/superpowers/` in any repo.
41
41
 
42
42
  ## Workflow Profiles
43
43
 
package/skills/skills/wiki-gate-plan-mode/SKILL.md CHANGED
@@ -1,18 +1,18 @@
1
1
  ---
2
2
  name: wiki-gate-plan-mode
3
- description: Toggle EnterPlanMode gating — force superpowers planning skills instead of built-in plan mode
3
+ description: Toggle EnterPlanMode gating — force brainstorming then SkillWiki proj-work instead of built-in plan mode
4
4
  ---
5
5
 
6
6
  # wiki-gate-plan-mode
7
7
 
8
8
  Gate the agent away from Claude Code's built-in `EnterPlanMode` tool, forcing
9
- all planning through `superpowers:brainstorming` → `superpowers:writing-plans`
10
- (or a configurable pipeline). Uses `permissions.deny` for two-layer enforcement:
11
- the tool is removed from the model's context before it ever sees it.
9
+ all planning through `brainstorming` → `proj-work` (SkillWiki PRD bridge).
10
+ Uses `permissions.deny` for two-layer enforcement: the tool is removed from
11
+ the model's context before it ever sees it.
12
12
 
13
13
  ## When This Skill Activates
14
14
 
15
- - User says "gate plan mode", "disable EnterPlanMode", "force superpowers planning"
15
+ - User says "gate plan mode", "disable EnterPlanMode", "force SkillWiki planning"
16
16
  - User asks to toggle, check, or configure plan-mode gating
17
17
  - User wants to enforce structured planning workflows in a project
18
18
 
@@ -40,7 +40,7 @@ None for the first run.
40
40
  - If `"EnterPlanMode"` is already in `permissions.deny`, report "already gated" and stop.
41
41
  - Otherwise, add `"EnterPlanMode"` to `permissions.deny[]`. Create the array if absent.
42
42
  - Write the updated JSON back, preserving formatting.
43
- - Report: "EnterPlanMode gated — agent will use superpowers planning skills."
43
+ - Report: "EnterPlanMode gated — agent will use brainstorming then proj-work."
44
44
 
45
45
  **`off`:**
46
46
  - If `"EnterPlanMode"` is not in `permissions.deny`, report "already ungated" and stop.
@@ -53,12 +53,12 @@ None for the first run.
53
53
  - Report whether EnterPlanMode is currently gated or ungated.
54
54
  - If gated, list which settings file contains the deny entry.
55
55
 
56
- 4. **Suggest CLAUDE.md directive (on action only).** After enabling gating, check whether the project's `CLAUDE.md` contains a planning directive (search for "EnterPlanMode" or "superpowers:brainstorming"). If not found, suggest adding:
56
+ 4. **Suggest CLAUDE.md directive (on action only).** After enabling gating, check whether the project's `CLAUDE.md` contains a planning directive (search for "EnterPlanMode", "brainstorming", or "proj-work"). If not found, suggest adding:
57
57
 
58
58
  ```
59
59
  ## Planning
60
60
 
61
- Use superpowers:brainstorming → superpowers:writing-plans for all planning. EnterPlanMode is disabled.
61
+ Use brainstorming → proj-work for all planning. Do not invoke writing-plans. EnterPlanMode is disabled.
62
62
  ```
63
63
 
64
64
  Do NOT edit CLAUDE.md automatically — only suggest.
package/skills/using-skillwiki/SKILL.md CHANGED
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: using-skillwiki
3
- description: Invoke at session start or when knowledge-base tasks arise — maps skillwiki skills, dev-loop alignment, adaptive workflow profiles, and vault routing
3
+ description: Invoke when vault, wiki, knowledge-base, or SkillWiki setup work arises — maps skillwiki skills, dev-loop alignment, adaptive workflow profiles, and vault routing. Do not invoke for unrelated coding or creative tasks.
4
4
  ---
5
5
  *Note: If executing as a background subagent, skip this skill section.*
6
6
 
@@ -30,19 +30,21 @@ Use this section as procedural planning guidelines:
30
30
 
31
31
  **Claude Code** and **Codex** activate SkillWiki via the plugin SessionStart hook (`hooks/session-start` / `hooks/session-start-codex`). Do **not** install activation markers into `~/.claude/CLAUDE.md` or `~/.codex/AGENTS.md` when the plugin is present — that double-injects context and pollutes user-scope instruction files.
32
32
 
33
- On harnesses where SessionStart `additionalContext` does **not** fire (**Grok**), SkillWiki activation context is delivered via a compact file. Run `npm run install:activation` from the repo to install:
33
+ On harnesses where SessionStart `additionalContext` does **not** fire (**Grok**), SkillWiki activation context is delivered via a compact file. Run `npm run install:activation` from the llm-wiki repo to install:
34
34
 
35
35
  - `~/.grok/skillwiki.md` — compact derivative covering identity, CLI probe, skill map, PRD bridge, fail-closed boundary, and drift warning.
36
- - `~/.grok/AGENTS.md` — prepended with a marker-wrapped reference: `Read @skillwiki.md for SkillWiki activation context.`
36
+ - `~/.grok/AGENTS.md` — prepended with a marker-wrapped reference: `Read @~/.grok/skillwiki.md for SkillWiki activation context.`
37
37
 
38
38
  Default install is **Grok only**. Re-running `install:activation` also **removes** any prior Claude/Codex activation marker and matching `skillwiki.md` (cleanup for the earlier dual-target installer). Opt-in fallbacks only when the plugin SessionStart path is unavailable:
39
39
 
40
- - `npm run install:activation -- --with-claude` — `~/.claude/skillwiki.md` + `CLAUDE.md` marker
41
- - `npm run install:activation -- --with-codex` — `~/.codex/skillwiki.md` + `AGENTS.md` marker
40
+ - `npm run install:activation -- --with-claude` — `~/.claude/skillwiki.md` + `CLAUDE.md` marker `Read @~/.claude/skillwiki.md …`
41
+ - `npm run install:activation -- --with-codex` — `~/.codex/skillwiki.md` + `AGENTS.md` marker `Read @~/.codex/skillwiki.md …`
42
42
 
43
- The activation file is self-contained literal text (ADR-3). On harnesses with `@file` import support, the reference is inlined automatically. On Grok (no `@file` support), the agent reads the file manually when it sees the instructional reference.
43
+ The activation file is self-contained literal text (ADR-3). On harnesses with `@file` import support, `@~/.grok/skillwiki.md` (or the Claude/Codex home path) is inlined. On Grok (no `@file` support), `read_file` the exact path `~/.grok/skillwiki.md`. Never `~/skillwiki.md`. Never a cwd-relative `skillwiki.md`. If that file is missing, say activation is absent and suggest `npm run install:activation` from the llm-wiki repo; do not create a home-level `skillwiki.md`.
44
44
 
45
- The template lives at `packages/skills/using-skillwiki/activation.md`. Run `npm run install:activation:check` to verify the Grok install matches the template and that Claude/Codex are not still carrying the activation block.
45
+ The compact `~/.grok/skillwiki.md` is the session-start context. This full skill is for vault/wiki/setup work only — do not load it at the start of an unrelated session.
46
+
47
+ The template lives at `packages/skills/using-skillwiki/activation.md`. Run `npm run install:activation:check` to verify the Grok install matches the template and that Claude/Codex are not still carrying the activation block. `skillwiki doctor` reports a warn on a missing file, a stale `@skillwiki.md` marker, or compact-file drift.
46
48
 
47
49
  ## When to Use These Skills
48
50
  Invoke a skillwiki skill when the user:
@@ -181,7 +183,7 @@ The vault is shared across hosts, so host-local absolute paths are not durable s
181
183
  | `wiki-sync` | Safely sync vault git repository — push/pull with lint guards and conflict resolution |
182
184
  | `wiki-canvas` | Generate Obsidian Canvas visualization from vault graph data |
183
185
  | `proj-decide` | Write an Architectural Decision Record (ADR) |
184
- | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating — force superpowers planning instead of built-in plan mode |
186
+ | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating — force brainstorming then proj-work instead of built-in plan mode |
185
187
  | `dev-loop:research` | Research agent for dev-loop IDLE — scans repo + vault health, outputs prioritized work-item recommendations (formerly `/dev-loop-research`) |
186
188
 
187
189
  ## dev-loop Alignment
@@ -224,7 +226,9 @@ for code changes.
224
226
 
225
227
  ## CLI Backbone
226
228
  All skills are backed by the `skillwiki` CLI — a deterministic tool with no LLM calls. It handles path resolution, config management, validation, health reporting, and linting. Skills invoke it via Bash for the mechanical parts and use the active agent for the creative parts.
227
- Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `query`, `sources pending`, `sources disposition`, `sources dispose`, `archive`, `remove`, `drift`, `dedup`, `compound`, `tag-sync`, `tag reconcile`, `page publish`, `sync status`, `seed`, `stale`, `observe`, `canvas generate`.
229
+ Key CLI subcommands: `init`, `health`, `lint`, `config`, `doctor`, `path`, `lang`, `install`, `fleet context`, `fleet validate`, `graph build`, `query`, `sources pending`, `sources disposition`, `sources dispose`, `archive`, `remove`, `drift`, `dedup`, `compound`, `tag-sync`, `tag reconcile`, `page publish`, `sync status`, `seed`, `stale`, `claim`, `claims audit`, `observe`, `canvas generate`.
230
+ `skillwiki claim` binds a transcript to a work item only through an exact `raw/transcripts/...` path in `source:` / `sources:` / `closes:`. A `--project` that contradicts the capture's explicit project is rejected. `skillwiki stale --project` uses exact normalized slugs, not substring matching. `skillwiki claims audit` is the read-only integrity report for duplicate, malformed, dangling, cross-project, and unbacked claims; it never rewrites captures or work items.
231
+
228
232
  Run `skillwiki health <vault> --out /tmp/skillwiki-health.json --no-fail` for a bounded whole-system report that includes the nonblocking source-lifecycle backlog. Pending captures are informational and do not make health fail. Run `skillwiki lint <vault> --summary` for lint-only bucket counts with capped examples and details commands. Run `skillwiki doctor` to diagnose setup/runtime issues only. Run `skillwiki config list` to see current configuration.
229
233
 
230
234
  ## Runtime Host Context and Fleet Freshness
@@ -298,15 +302,21 @@ skillwiki supports named wiki profiles for working with multiple vaults. Set `WI
298
302
  **Project-local override:** Place a `./skillwiki/.env` in a project root to bind that project to a specific wiki. Skills will use it automatically when running from that directory.
299
303
 
300
304
  ## PRD Bridge — Redirect Spec/Plan Output to Vault
301
- When skillwiki is installed, **all spec and plan documents must land in the vault**, not in repo-local directories like `docs/superpowers/`. This applies to PRD and TDD workflows (superpowers, codestable, AIDE, Hermes, manual templates).
302
- **Rule:** Before a PRD skill writes a spec or plan file, redirect its save path:
303
- 1. Resolve the vault path: `skillwiki path`
304
- 2. If the cwd is inside a project (check for `projects/{slug}/` via `skillwiki path --init-time` or look for `./skillwiki/.env`), use that project's work directory
305
- 3. Create or locate the work item via `proj-work`, which emits redirect paths for `spec.md` and `plan.md`
306
- 4. Pass those vault paths to the PRD/TDD skill as its save location
307
- **Concrete overrides for superpowers:**
308
- - `superpowers:brainstorming` step 6: override `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` → vault work-item `spec.md` path from `proj-work`
309
- - `superpowers:writing-plans` header: override `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md` → vault work-item `plan.md` path from `proj-work`
310
- Both skills say "User preferences for spec location override this default" — the vault work-item path IS the override. Apply the same override pattern to any TDD-oriented planner that emits spec/plan artifacts.
311
- **If no project context exists** (standalone vault, not inside a project), default to the `playground` project slug. Invoke `proj-work` with `playground` as the slug so redirect paths are emitted normally and the PRD bridge chain works. The `playground` project is a pre-initialized catch-all workspace at `projects/playground/` for exploratory work, experiments, and unclassified features. Work items that mature can be moved to a real project later.
305
+ When skillwiki is installed, **all spec and plan documents must land in the vault**, not in repo-local directories like `docs/superpowers/`. This applies to brainstorming, grill-me, and any foreign PRD template (CodeStable, AIDE, Hermes).
306
+
307
+ **Architectural brainstorming** (after the human approves the design):
308
+ 1. Resolve the vault path: `skillwiki path`.
309
+ 2. Invoke `proj-work` so the work folder exists. If cwd is inside `projects/{slug}/` (or `./skillwiki/.env` binds a project), use that slug. Otherwise use `playground`.
310
+ 3. Write `spec.md` only at the emitted redirect path.
311
+ 4. Do not invoke `writing-plans`.
312
+ 5. Do not git commit from brainstorming.
313
+ 6. `plan.md` is a later `proj-work` / explicit user step, not a Superpowers plan file.
314
+
315
+ If the work is UI (layout, mockup, component look, page structure), offer brainstorming `visual-companion.md` at the first UI question as its own message. Offer the companion once. The human may decline. Non-UI work never offers it. Do not auto-open.
316
+
317
+ **Bounded implementation:** after a bounded design is approved, TDD applies when standalone `test-driven-development` is installed. Do not require the Superpowers plugin.
318
+
319
+ **Foreign PRD skills** that still default to `docs/superpowers/specs/` or `docs/superpowers/plans/` must use the `proj-work` redirect paths instead. The vault work-item path is the user preference those skills honor.
320
+
321
+ The `playground` project at `projects/playground/` is the catch-all workspace when no project context exists. Work items that mature can move to a real project later.
312
322
  **Never create `docs/superpowers/` in any repo.**
package/skills/using-skillwiki/activation.md CHANGED
@@ -28,7 +28,7 @@ Invoke a SkillWiki skill when the user: wants vault/wiki/knowledge-base operatio
28
28
  | `wiki-adapter-prd` | Map foreign PRD formats (CodeStable, RFC, AIDE, Hermes) |
29
29
  | `wiki-sync` | Safely sync vault git repository |
30
30
  | `wiki-canvas` | Generate Obsidian Canvas visualization |
31
- | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating for superpowers planning |
31
+ | `wiki-gate-plan-mode` | Toggle EnterPlanMode gating for brainstorming then proj-work |
32
32
  | `proj-init` | Bootstrap a project workspace |
33
33
  | `proj-work` | Open or run a work item |
34
34
  | `proj-distill` | Distill project compound entries into concept pages |
@@ -37,7 +37,7 @@ Invoke a SkillWiki skill when the user: wants vault/wiki/knowledge-base operatio
37
37
 
38
38
  ## PRD Bridge
39
39
 
40
- Route PRD/spec/plan work to `wiki-adapter-prd` and `proj-work`, not `docs/superpowers/`. Spec and plan outputs must land in vault work-item paths. Never create `docs/superpowers/` in any repo.
40
+ After architectural design approval, invoke `proj-work` then write `spec.md` in that work folder. Do not invoke `writing-plans`. Do not git commit from brainstorming. Bounded TDD uses standalone `test-driven-development` when installed. For UI work, offer brainstorming `visual-companion.md` once (optional). Never create `docs/superpowers/` in any repo.
41
41
 
42
42
  ## Workflow Profiles
43
43
 
package/skills/wiki-gate-plan-mode/SKILL.md CHANGED
@@ -1,18 +1,18 @@
1
1
  ---
2
2
  name: wiki-gate-plan-mode
3
- description: Toggle EnterPlanMode gating — force superpowers planning skills instead of built-in plan mode
3
+ description: Toggle EnterPlanMode gating — force brainstorming then SkillWiki proj-work instead of built-in plan mode
4
4
  ---
5
5
 
6
6
  # wiki-gate-plan-mode
7
7
 
8
8
  Gate the agent away from Claude Code's built-in `EnterPlanMode` tool, forcing
9
- all planning through `superpowers:brainstorming` → `superpowers:writing-plans`
10
- (or a configurable pipeline). Uses `permissions.deny` for two-layer enforcement:
11
- the tool is removed from the model's context before it ever sees it.
9
+ all planning through `brainstorming` → `proj-work` (SkillWiki PRD bridge).
10
+ Uses `permissions.deny` for two-layer enforcement: the tool is removed from
11
+ the model's context before it ever sees it.
12
12
 
13
13
  ## When This Skill Activates
14
14
 
15
- - User says "gate plan mode", "disable EnterPlanMode", "force superpowers planning"
15
+ - User says "gate plan mode", "disable EnterPlanMode", "force SkillWiki planning"
16
16
  - User asks to toggle, check, or configure plan-mode gating
17
17
  - User wants to enforce structured planning workflows in a project
18
18
 
@@ -40,7 +40,7 @@ None for the first run.
40
40
  - If `"EnterPlanMode"` is already in `permissions.deny`, report "already gated" and stop.
41
41
  - Otherwise, add `"EnterPlanMode"` to `permissions.deny[]`. Create the array if absent.
42
42
  - Write the updated JSON back, preserving formatting.
43
- - Report: "EnterPlanMode gated — agent will use superpowers planning skills."
43
+ - Report: "EnterPlanMode gated — agent will use brainstorming then proj-work."
44
44
 
45
45
  **`off`:**
46
46
  - If `"EnterPlanMode"` is not in `permissions.deny`, report "already ungated" and stop.
@@ -53,12 +53,12 @@ None for the first run.
53
53
  - Report whether EnterPlanMode is currently gated or ungated.
54
54
  - If gated, list which settings file contains the deny entry.
55
55
 
56
- 4. **Suggest CLAUDE.md directive (on action only).** After enabling gating, check whether the project's `CLAUDE.md` contains a planning directive (search for "EnterPlanMode" or "superpowers:brainstorming"). If not found, suggest adding:
56
+ 4. **Suggest CLAUDE.md directive (on action only).** After enabling gating, check whether the project's `CLAUDE.md` contains a planning directive (search for "EnterPlanMode", "brainstorming", or "proj-work"). If not found, suggest adding:
57
57
 
58
58
  ```
59
59
  ## Planning
60
60
 
61
- Use superpowers:brainstorming → superpowers:writing-plans for all planning. EnterPlanMode is disabled.
61
+ Use brainstorming → proj-work for all planning. Do not invoke writing-plans. EnterPlanMode is disabled.
62
62
  ```
63
63
 
64
64
  Do NOT edit CLAUDE.md automatically — only suggest.