roadmapsmith 0.9.14 → 0.9.16
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.
- package/README.md +71 -16
- package/bin/cli.js +340 -93
- package/package.json +2 -2
- package/src/config.js +33 -2
- package/src/generator/index.js +31 -4
- package/src/host.js +982 -0
- package/src/index.js +3 -0
- package/src/slash.js +226 -0
- package/src/zero.js +129 -0
package/README.md
CHANGED
|
@@ -12,15 +12,24 @@ Production-grade roadmap generator and sync tool for agent-driven projects.
|
|
|
12
12
|
|
|
13
13
|
```bash
|
|
14
14
|
npm install -g roadmapsmith
|
|
15
|
+
roadmapsmith setup
|
|
16
|
+
roadmapsmith zero
|
|
17
|
+
roadmapsmith maintain
|
|
15
18
|
```
|
|
16
19
|
|
|
20
|
+
Slash entrypoints are also supported from the CLI and launcher, for example: `roadmapsmith /road`, `roadmapsmith /zero`, `roadmapsmith /maintain`, and `roadmapsmith /roadmap-sync maintain`.
|
|
21
|
+
The generated VS Code task layer now resolves Node automatically where possible; if it cannot, RoadmapSmith prints a readable runtime diagnostic instead of a dead task.
|
|
22
|
+
`RoadmapSmith: Status` now treats "ready" as runnable task UX, not merely generated files.
|
|
23
|
+
|
|
17
24
|
### Agent Skill
|
|
18
25
|
|
|
19
26
|
```bash
|
|
20
|
-
npx skills add PapiScholz/roadmapsmith --skill
|
|
27
|
+
npx skills add PapiScholz/roadmapsmith --skill '*' -a claude-code
|
|
21
28
|
```
|
|
22
29
|
|
|
23
|
-
This
|
|
30
|
+
This is the recommended Claude Code install path for native GUI slash commands such as `/road`, `/zero`, `/maintain`, `/status`, `/init`, `/generate`, `/validate`, `/sync`, `/audit`, `/setup`, and the legacy `/roadmap-sync`.
|
|
31
|
+
If you install only `--skill roadmap-sync`, Claude GUI will expose only `/roadmap-sync`.
|
|
32
|
+
The skill bundle does not install the CLI and it does not create visible VS Code actions by itself.
|
|
24
33
|
|
|
25
34
|
## Updating
|
|
26
35
|
|
|
@@ -37,12 +46,15 @@ npm install roadmapsmith@latest
|
|
|
37
46
|
npx roadmapsmith@latest validate --json
|
|
38
47
|
```
|
|
39
48
|
|
|
40
|
-
The
|
|
49
|
+
The Claude skill bundle is separate from the CLI. Re-running the skills install updates the Claude-facing instructions, but it does not update the `roadmapsmith` npm binary or the generated VS Code host files:
|
|
41
50
|
|
|
42
51
|
```bash
|
|
43
|
-
npx skills add PapiScholz/roadmapsmith --skill
|
|
52
|
+
npx skills add PapiScholz/roadmapsmith --skill '*' -a claude-code
|
|
44
53
|
```
|
|
45
54
|
|
|
55
|
+
After updating the Claude skill bundle, run `/reload-skills` and, if applicable, `/reload-plugins`.
|
|
56
|
+
After updating the CLI, rerun `roadmapsmith setup` in repositories where you want the latest VS Code tasks, task wrappers, launcher behavior, or Claude hook template.
|
|
57
|
+
|
|
46
58
|
Fixes are available through `@latest` only after a new npm package version has been published. Before publication, install from a local checkout or a packed tarball for testing.
|
|
47
59
|
|
|
48
60
|
## Operating Modes
|
|
@@ -51,11 +63,11 @@ Fixes are available through `@latest` only after a new npm package version has b
|
|
|
51
63
|
|
|
52
64
|
Agent-guided discovery for empty or low-context repositories. The developer has a product idea but no implementation files, no stack decision, and no ROADMAP.md yet.
|
|
53
65
|
|
|
54
|
-
|
|
66
|
+
Run `roadmapsmith setup` first if you want visible VS Code tasks. `roadmapsmith zero` is the one-command entrypoint: it runs the terminal interview, creates governance files when needed, and generates the first roadmap.
|
|
55
67
|
|
|
56
68
|
```bash
|
|
57
|
-
roadmapsmith
|
|
58
|
-
roadmapsmith
|
|
69
|
+
roadmapsmith setup
|
|
70
|
+
roadmapsmith zero
|
|
59
71
|
```
|
|
60
72
|
|
|
61
73
|
### Sync/Audit Mode
|
|
@@ -63,32 +75,68 @@ roadmapsmith generate --project-root .
|
|
|
63
75
|
Repository-backed roadmap generation, validation, and synchronization. Use when the repository already has code, tests, docs, TODOs, or an existing ROADMAP.md.
|
|
64
76
|
|
|
65
77
|
```bash
|
|
66
|
-
roadmapsmith
|
|
67
|
-
roadmapsmith
|
|
68
|
-
roadmapsmith sync
|
|
69
|
-
roadmapsmith sync --dry-run
|
|
78
|
+
roadmapsmith setup
|
|
79
|
+
roadmapsmith maintain
|
|
70
80
|
```
|
|
71
81
|
|
|
82
|
+
## Recommended Daily Flow
|
|
83
|
+
|
|
84
|
+
Use the public entrypoints first:
|
|
85
|
+
|
|
86
|
+
```bash
|
|
87
|
+
roadmapsmith setup
|
|
88
|
+
roadmapsmith zero # empty repo
|
|
89
|
+
roadmapsmith maintain # existing repo
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Use the lower-level commands only when you want manual control over generation, validation, or sync.
|
|
93
|
+
|
|
72
94
|
## Host Support Today
|
|
73
95
|
|
|
74
96
|
| Host | Current support |
|
|
75
97
|
|---|---|
|
|
76
|
-
| Claude Code |
|
|
77
|
-
| Codex / Codex CLI |
|
|
98
|
+
| Claude Code | Supported through the full RoadmapSmith skill bundle for native GUI slash commands, plus `roadmapsmith setup` for visible VS Code tasks and the optional repo-local Claude hook. |
|
|
99
|
+
| Codex / Codex CLI | Supported through a visible VS Code task workflow and slash-capable launcher UX after `roadmapsmith setup`. Codex chat itself remains unchanged unless the host exposes native slash registration. |
|
|
78
100
|
| CI | Use disposable checkouts if you run `sync --audit`, because it still mutates the roadmap today. |
|
|
79
101
|
| Other hosts | Use the skill plus manual CLI commands. |
|
|
80
102
|
|
|
103
|
+
If Node is installed outside PATH, set `ROADMAPSMITH_NODE` to a working `node` executable before using the generated VS Code tasks.
|
|
104
|
+
|
|
81
105
|
---
|
|
82
106
|
|
|
83
107
|
## Commands
|
|
84
108
|
|
|
85
109
|
```bash
|
|
110
|
+
roadmapsmith /road
|
|
111
|
+
roadmapsmith /zero
|
|
112
|
+
roadmapsmith /maintain
|
|
113
|
+
roadmapsmith /roadmap-sync maintain
|
|
114
|
+
roadmapsmith setup [--project-root <path>] [--config <path>] [--editor vscode] [--hosts <codex,claude>] [--dry-run]
|
|
115
|
+
roadmapsmith zero [--project-root <path>] [--config <path>]
|
|
116
|
+
roadmapsmith maintain [--project-root <path>] [--config <path>] [--roadmap-file <path>]
|
|
86
117
|
roadmapsmith init [--roadmap-file <path>] [--agents-file <path>] [--dry-run]
|
|
87
118
|
roadmapsmith generate [--project-root <path>] [--config <path>] [--roadmap-file <path>] [--dry-run] [--audit]
|
|
88
119
|
roadmapsmith sync [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--dry-run] [--audit]
|
|
89
120
|
roadmapsmith validate [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--task <id|text>] [--json]
|
|
121
|
+
roadmapsmith doctor [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--json]
|
|
90
122
|
```
|
|
91
123
|
|
|
124
|
+
## Claude Code native slash commands
|
|
125
|
+
|
|
126
|
+
Install the full skill bundle for Claude Code:
|
|
127
|
+
|
|
128
|
+
```bash
|
|
129
|
+
npx skills add PapiScholz/roadmapsmith --skill '*' -a claude-code
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
Then reload the session:
|
|
133
|
+
|
|
134
|
+
1. Run `/reload-skills`
|
|
135
|
+
2. If RoadmapSmith was installed through a Claude plugin, also run `/reload-plugins`
|
|
136
|
+
3. Confirm the slash menu shows `/road`, `/zero`, `/maintain`, `/status`, `/init`, `/generate`, `/validate`, `/sync`, `/audit`, `/setup`, and `/roadmap-sync`
|
|
137
|
+
|
|
138
|
+
Native Claude GUI slash commands come from the installed skill bundle. CLI slash routing such as `roadmapsmith /road` is a separate surface and does not populate the Claude GUI menu by itself.
|
|
139
|
+
|
|
92
140
|
## Behavior
|
|
93
141
|
|
|
94
142
|
- Generates deterministic `ROADMAP.md` with fixed section order.
|
|
@@ -241,10 +289,9 @@ module.exports = {
|
|
|
241
289
|
## Example Usage
|
|
242
290
|
|
|
243
291
|
```bash
|
|
244
|
-
roadmapsmith
|
|
245
|
-
roadmapsmith
|
|
292
|
+
roadmapsmith zero
|
|
293
|
+
roadmapsmith maintain
|
|
246
294
|
roadmapsmith validate --json
|
|
247
|
-
roadmapsmith sync
|
|
248
295
|
roadmapsmith sync --dry-run
|
|
249
296
|
```
|
|
250
297
|
|
|
@@ -261,6 +308,8 @@ roadmapsmith sync --dry-run
|
|
|
261
308
|
npm test
|
|
262
309
|
```
|
|
263
310
|
|
|
311
|
+
If `npm test` fails in your shell with "`node` is not recognized", treat that as a local PATH/runtime issue first and rerun the suite with an explicit Node executable.
|
|
312
|
+
|
|
264
313
|
## Publishing
|
|
265
314
|
|
|
266
315
|
```bash
|
|
@@ -270,6 +319,12 @@ npm publish --access public
|
|
|
270
319
|
git push origin main --follow-tags
|
|
271
320
|
```
|
|
272
321
|
|
|
322
|
+
Repository-specific release note:
|
|
323
|
+
|
|
324
|
+
- The canonical release automation lives in `.github/workflows/ci.yml`.
|
|
325
|
+
- This repository publishes from GitHub Actions on `main`; local `npm publish` is a maintainer workflow, not the default repo release path.
|
|
326
|
+
- Before publishing, verify the UX/release gate in `docs/release-ux-gate.md` and update `CHANGELOG.md` with the user-visible behavior changes.
|
|
327
|
+
|
|
273
328
|
## Versioning Strategy
|
|
274
329
|
|
|
275
330
|
- `patch`: bug fixes and non-breaking validation/generation improvements.
|