roadmapsmith 0.9.32 → 0.9.33

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "roadmapsmith",
-  "version": "0.9.32",
+  "version": "0.9.33",
   "description": "Evidence-backed ROADMAP.md workflows for AI coding agents, with canonical RoadmapSmith status and maintain surfaces plus advanced sync/generate tools and legacy compatibility aliases.",
   "author": {
     "name": "PapiScholz"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "roadmapsmith",
-  "version": "0.9.32",
+  "version": "0.9.33",
   "description": "Evidence-backed ROADMAP.md workflows for AI coding agents, with canonical RoadmapSmith status and maintain surfaces plus advanced sync/generate tools and legacy compatibility aliases.",
   "author": {
     "name": "PapiScholz"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "roadmapsmith",
-  "version": "0.9.32",
+  "version": "0.9.33",
   "description": "Evidence-backed ROADMAP.md workflows for AI coding agents, with canonical RoadmapSmith status and maintain surfaces plus advanced sync/generate tools and legacy compatibility aliases.",
   "main": "src/index.js",
   "bin": {

package/skills/roadmap/SKILL.md

@@ -10,21 +10,14 @@ Use this command as the native discovery entrypoint for the shared RoadmapSmith
 ## Required behavior
 
 1. Treat `/roadmap` as a no-side-effects palette. Do not run mutating commands from this skill.
-2. When working inside the RoadmapSmith repository itself and `roadmap-skill/bin/cli.js` exists, prefer the local engine:
-   - `node roadmap-skill/bin/cli.js /roadmap`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js /roadmap` if `node` is not in PATH
-3. Otherwise, if the `roadmapsmith` CLI is available, you may run `roadmapsmith /roadmap` from the project root and use that output directly. If its global shim cannot resolve `node`, use `& "C:\Program Files\nodejs\node.exe" "$env:APPDATA\npm\node_modules\roadmapsmith\bin\cli.js" /roadmap`.
-4. If the CLI is missing, provide the palette manually and explain the install path:
-   - `npm install -g roadmapsmith`
-   - `npx skills add PapiScholz/roadmapsmith --skill '*' -a claude-code`
-   - run `/reload-skills`
-   - if RoadmapSmith was installed as a Claude plugin, also run `/reload-plugins`
-5. Explain the preferred native host entrypoints:
+2. If the `roadmapsmith` CLI is available, run `roadmapsmith /roadmap` from the project root and use that output directly.
+3. If the CLI is missing, direct the user to the official repository README for installation instructions.
+4. Explain the preferred native host entrypoints:
    - `/roadmap-zero`
    - `/roadmap-maintain`
    - `/roadmap-status`
    - `/roadmap-init`, `/roadmap-generate`, `/roadmap-validate`, `/roadmap-update`, `/roadmap-audit`, and `/roadmap-setup`
-6. Mention that `/roadmap-sync <action>` remains a deprecated legacy CLI compatibility root, and `/road` plus `/road <action>` remain deprecated CLI compatibility aliases.
+5. Mention that `/roadmap-sync <action>` remains a deprecated legacy CLI compatibility root, and `/road` plus `/road <action>` remain deprecated CLI compatibility aliases.
 
 ## Output contract
 

package/skills/roadmap-audit/SKILL.md

@@ -9,8 +9,5 @@ Use this command when the user wants the post-sync mismatch summary after applyi
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js sync --audit --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js sync --audit --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith sync --audit --project-root .`.
-3. Explain that this is the current sync-plus-audit flow, not a standalone read-only audit engine.
+1. Run `roadmapsmith sync --audit --project-root .`.
+2. Explain that this is the current sync-plus-audit flow, not a standalone read-only audit engine.

package/skills/roadmap-generate/SKILL.md

@@ -9,10 +9,7 @@ Use this command when the user wants the managed roadmap block updated from repo
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js generate --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js generate --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith generate --project-root .`.
-3. Explain that `generate` is preserve-first when a substantive managed block already exists.
-4. When the user explicitly wants the destructive path, use `roadmapsmith generate --project-root . --full-regen`.
-5. Summarize what stayed preserved, whether generation refused, and what new additions, if any, were inserted.
+1. Run `roadmapsmith generate --project-root .`.
+2. Explain that `generate` is preserve-first when a substantive managed block already exists.
+3. To allow full roadmap regeneration, add `--full-regen`: `roadmapsmith generate --project-root . --full-regen`.
+4. Summarize what stayed preserved, whether generation refused, and what new additions, if any, were inserted.

package/skills/roadmap-init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: roadmap-init
-description: Create ROADMAP.md and AGENTS.md through the RoadmapSmith CLI.
+description: Initialize project governance files through the RoadmapSmith CLI.
 ---
 
 # RoadmapSmith Init
@@ -9,8 +9,5 @@ Use this command when the governance files are missing and the user wants them c
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js init --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js init --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith init`.
-3. Treat this command as CLI-backed and summarize whether files were created or skipped.
+1. Run `roadmapsmith init`.
+2. Summarize whether files were created or skipped.

package/skills/roadmap-maintain/SKILL.md

@@ -9,12 +9,7 @@ Use this command when the repository already has code, tests, docs, or an existi
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js maintain --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js maintain --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith maintain --project-root .`. If that global shim fails because `node` is not in PATH, run `& "C:\Program Files\nodejs\node.exe" "$env:APPDATA\npm\node_modules\roadmapsmith\bin\cli.js" maintain --project-root .`.
-3. Treat this command as CLI-backed. Do not silently replace it with manual reasoning when the CLI is unavailable.
-4. Mention that maintain runs preserve-first generate, sync, and audit in one invocation.
-5. After a successful maintain cycle, do not propose generate, sync, or audit separately unless the user needs manual control or inspection.
-6. Mention that `roadmapsmith maintain --full-regen` or `roadmapsmith generate --full-regen` is the explicit destructive rebuild path when the user truly wants a full managed-block replacement.
-7. When the user wants stale or outdated warning annotations to be recomputed from scratch (including annotations that were written by a prior maintain run or an external agent), use `roadmapsmith maintain --refresh-annotations`. This forces all existing warning text to be replaced with the current deterministic result rather than preserved. It is distinct from `--full-regen` (which rebuilds the managed block structure) — `--refresh-annotations` only affects warning annotations on still-failing tasks.
+1. Run `roadmapsmith maintain --project-root .`.
+2. Treat this command as CLI-backed. Do not silently replace it with manual reasoning when the CLI is unavailable.
+3. Mention that maintain runs preserve-first generate, sync, and audit in one invocation.
+4. After a successful maintain cycle, do not propose generate, sync, or audit separately unless the user needs manual control or inspection.

package/skills/roadmap-setup/SKILL.md

@@ -9,9 +9,6 @@ Use this command when the user wants RoadmapSmith host integration files generat
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js setup --project-root . --hosts codex,claude`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js setup --project-root . --hosts codex,claude` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith setup --project-root . --hosts codex,claude`.
-3. Explain that setup affects the repository host layer: VS Code tasks, launcher/wrappers, and the optional repo-local Claude hook.
-4. Do not claim that setup alone creates native host slash commands; those come from the installed bundle/plugin.
+1. Run `roadmapsmith setup --project-root . --hosts codex,claude`.
+2. Explain that setup generates VS Code task definitions for the current repository.
+3. Do not claim that setup alone creates native host slash commands; those come from the installed bundle/plugin.

package/skills/roadmap-status/SKILL.md

@@ -9,10 +9,7 @@ Use this command to inspect whether the shared bundle, native host surfaces, CLI
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js status --json --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js status --json --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith status --json --project-root .`. If its global shim cannot resolve `node`, use `& "C:\Program Files\nodejs\node.exe" "$env:APPDATA\npm\node_modules\roadmapsmith\bin\cli.js" status --json --project-root .`.
-3. Treat `roadmapsmith doctor --json` as compatibility-only output for existing automation, not as the primary recommendation.
+1. Run `roadmapsmith status --json --project-root .`.
+2. Treat `roadmapsmith doctor --json` as compatibility-only output for existing automation, not as the primary recommendation.
 4. Parse and summarize the JSON output in plain language.
 5. Explicitly call out missing canonical commands, duplicate legacy `/roadmap-sync` registration, and any missing advanced VS Code labels as warnings rather than canonical-readiness failures.

package/skills/roadmap-sync/SKILL.md

@@ -16,5 +16,5 @@ Use this skill only when the host exposes or the user explicitly invokes `/roadm
    - `/roadmap-maintain`
    - `/roadmap-status`
    - `/roadmap-init`, `/roadmap-generate`, `/roadmap-validate`, `/roadmap-update`, `/roadmap-audit`, and `/roadmap-setup`
-3. When the user explicitly invokes `/roadmap-sync <action>`, route to the matching CLI-backed action without changing semantics and mention the migration path to `/roadmap <action>` or the direct `/roadmap-*` command.
-4. Preserve the operating rules for evidence-backed roadmap maintenance and checklist synchronization: heuristic file/token matches may diagnose candidates, but only explicit `Evidence:` or typed `Verify:` checks may complete an unchecked implementation task. Never claim a behavioral task is complete without fresh test evidence or human verification.
+3. When the user explicitly invokes `/roadmap-sync <action>`, route to the matching CLI-backed action without changing semantics and mention the migration path to the direct `/roadmap-*` command.
+4. When routing `/roadmap-sync validate`, the tool uses the same validation rules as `/roadmap-validate`. Implementation tasks require an explicit `Evidence:` line or a `Verify:` check to be marked complete.

package/skills/roadmap-update/SKILL.md

@@ -9,10 +9,7 @@ Use this command when the user wants the canonical public `update` surface witho
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js update --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js update --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith update --project-root .`. If its global shim fails because `node` is not in PATH, run `& "C:\Program Files\nodejs\node.exe" "$env:APPDATA\npm\node_modules\roadmapsmith\bin\cli.js" update --project-root .`.
-3. Explain that `/roadmap-update` is the visible namespaced command for the public `update` family, while `/roadmap-sync <action>` remains deprecated compatibility only.
-4. Keep the evidence-backed refresh semantics unchanged: no-argument `update` syncs the roadmap from repository evidence, and `sync` remains the advanced CLI alias for that same mutating refresh path. It is not a full regeneration path and not an independent audit engine.
-5. To complete one task, run `roadmapsmith update --task <stable-id> --evidence "<single-line evidence>"`. It writes only after the supplied evidence validates at high confidence; use `--dry-run` to preview it.
+1. Run `roadmapsmith update --project-root .`.
+2. Explain that `/roadmap-update` is the visible namespaced command for the public `update` family, while `/roadmap-sync <action>` remains deprecated compatibility only.
+3. The no-argument `update` syncs the roadmap from repository evidence. The `sync` alias covers the same refresh path. It is not a full regeneration path and not an independent audit engine.
+4. To mark a specific task complete, run `roadmapsmith update --task TASK-ID --evidence "description"`. The CLI validates before writing; use `--dry-run` to preview.

package/skills/roadmap-validate/SKILL.md

@@ -9,8 +9,5 @@ Use this command when the user wants per-task evidence status without mutating t
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js validate --json --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js validate --json --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith validate --json --project-root .`.
-3. Treat this command as CLI-backed and non-mutating.
+1. Run `roadmapsmith validate --json --project-root .`.
+2. This command is non-mutating.

package/skills/roadmap-zero/SKILL.md

@@ -9,9 +9,5 @@ Use this command when the repository is empty or low-context and the user needs
 
 ## Required behavior
 
-1. Prefer the local engine inside this repository:
-   - `node roadmap-skill/bin/cli.js zero --project-root .`
-   - on this Windows machine, prefer `C:\Program Files\nodejs\node.exe roadmap-skill/bin/cli.js zero --project-root .` if `node` is not in PATH
-2. Otherwise prefer `roadmapsmith zero --project-root .`.
-3. Treat this command as CLI-backed and interactive.
-4. If the CLI is missing, explain the install path instead of improvising the workflow manually.
+1. Run `roadmapsmith zero --project-root .`.
+2. If the CLI is missing, explain the install path instead of improvising the workflow manually.

package/skills.json

@@ -28,67 +28,67 @@
       "name": "roadmap",
       "path": "skills/roadmap",
       "description": "Native slash palette for RoadmapSmith commands and recommended entrypoints across supported hosts.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-zero",
       "path": "skills/roadmap-zero",
       "description": "Native slash entrypoint for the one-command Zero Mode CLI workflow.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-maintain",
       "path": "skills/roadmap-maintain",
       "description": "Native slash entrypoint for the preserve-first generate + sync + audit flow.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-status",
       "path": "skills/roadmap-status",
       "description": "Native slash readiness check grounded in roadmapsmith status JSON.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-init",
       "path": "skills/roadmap-init",
       "description": "Native slash entrypoint for creating ROADMAP.md and AGENTS.md.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-generate",
       "path": "skills/roadmap-generate",
       "description": "Native slash entrypoint for managed roadmap updates that require --full-regen before destructive replacement.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-validate",
       "path": "skills/roadmap-validate",
       "description": "Native slash entrypoint for evidence-backed roadmap validation.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-update",
       "path": "skills/roadmap-update",
       "description": "Native slash entrypoint for evidence-backed sync and verified single-task completion.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-sync",
       "path": "skills/roadmap-sync",
       "description": "DEPRECATED legacy compatibility root; use roadmap-maintain or roadmap-update.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-audit",
       "path": "skills/roadmap-audit",
       "description": "Native slash entrypoint for the advanced sync-plus-audit mutating summary workflow.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     },
     {
       "name": "roadmap-setup",
       "path": "skills/roadmap-setup",
       "description": "Native slash entrypoint for generating RoadmapSmith host integration files.",
-      "version": "0.9.32"
+      "version": "0.9.33"
     }
   ]
 }