roadmapsmith 0.9.13 → 0.9.15

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 CHANGED
@@ -12,15 +12,22 @@ 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
27
  npx skills add PapiScholz/roadmapsmith --skill roadmap-sync
21
28
  ```
22
29
 
23
- This adds the `roadmap-sync` agent skill. It does not install the CLI package.
30
+ This adds the `roadmap-sync` agent skill only. It does not install the CLI and it does not create visible VS Code actions by itself.
24
31
 
25
32
  ## Updating
26
33
 
@@ -34,15 +41,17 @@ npm install -g roadmapsmith@latest
34
41
  npm install roadmapsmith@latest
35
42
 
36
43
  # One-off execution without installing
37
- npx roadmapsmith@latest sync --audit
44
+ npx roadmapsmith@latest validate --json
38
45
  ```
39
46
 
40
- The `roadmap-sync` agent skill is separate from the CLI. Re-running the skills install updates the agent instructions, but it does not update the `roadmapsmith` npm binary:
47
+ The `roadmap-sync` agent skill is separate from the CLI. Re-running the skills install updates the agent instructions, but it does not update the `roadmapsmith` npm binary or the generated VS Code host files:
41
48
 
42
49
  ```bash
43
50
  npx skills add PapiScholz/roadmapsmith --skill roadmap-sync
44
51
  ```
45
52
 
53
+ 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.
54
+
46
55
  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
56
 
48
57
  ## Operating Modes
@@ -51,11 +60,11 @@ Fixes are available through `@latest` only after a new npm package version has b
51
60
 
52
61
  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
62
 
54
- The CLI creates governance files. The AI agent (using the `roadmap-sync` skill) performs the discovery interview before generating the roadmap.
63
+ 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
64
 
56
65
  ```bash
57
- roadmapsmith init
58
- roadmapsmith generate --project-root .
66
+ roadmapsmith setup
67
+ roadmapsmith zero
59
68
  ```
60
69
 
61
70
  ### Sync/Audit Mode
@@ -63,20 +72,50 @@ roadmapsmith generate --project-root .
63
72
  Repository-backed roadmap generation, validation, and synchronization. Use when the repository already has code, tests, docs, TODOs, or an existing ROADMAP.md.
64
73
 
65
74
  ```bash
66
- roadmapsmith generate --project-root .
67
- roadmapsmith validate --json
68
- roadmapsmith sync --audit
75
+ roadmapsmith setup
76
+ roadmapsmith maintain
77
+ ```
78
+
79
+ ## Recommended Daily Flow
80
+
81
+ Use the public entrypoints first:
82
+
83
+ ```bash
84
+ roadmapsmith setup
85
+ roadmapsmith zero # empty repo
86
+ roadmapsmith maintain # existing repo
69
87
  ```
70
88
 
89
+ Use the lower-level commands only when you want manual control over generation, validation, or sync.
90
+
91
+ ## Host Support Today
92
+
93
+ | Host | Current support |
94
+ |---|---|
95
+ | Claude Code | Supported through `roadmapsmith setup`: visible VS Code tasks, slash-capable launcher UX, and optional repo-local Claude hook wiring. |
96
+ | 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. |
97
+ | CI | Use disposable checkouts if you run `sync --audit`, because it still mutates the roadmap today. |
98
+ | Other hosts | Use the skill plus manual CLI commands. |
99
+
100
+ If Node is installed outside PATH, set `ROADMAPSMITH_NODE` to a working `node` executable before using the generated VS Code tasks.
101
+
71
102
  ---
72
103
 
73
104
  ## Commands
74
105
 
75
106
  ```bash
107
+ roadmapsmith /road
108
+ roadmapsmith /zero
109
+ roadmapsmith /maintain
110
+ roadmapsmith /roadmap-sync maintain
111
+ roadmapsmith setup [--project-root <path>] [--config <path>] [--editor vscode] [--hosts <codex,claude>] [--dry-run]
112
+ roadmapsmith zero [--project-root <path>] [--config <path>]
113
+ roadmapsmith maintain [--project-root <path>] [--config <path>] [--roadmap-file <path>]
76
114
  roadmapsmith init [--roadmap-file <path>] [--agents-file <path>] [--dry-run]
77
115
  roadmapsmith generate [--project-root <path>] [--config <path>] [--roadmap-file <path>] [--dry-run] [--audit]
78
116
  roadmapsmith sync [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--dry-run] [--audit]
79
117
  roadmapsmith validate [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--task <id|text>] [--json]
118
+ roadmapsmith doctor [--roadmap-file <path>] [--project-root <path>] [--config <path>] [--json]
80
119
  ```
81
120
 
82
121
  ## Behavior
@@ -84,6 +123,7 @@ roadmapsmith validate [--roadmap-file <path>] [--project-root <path>] [--config
84
123
  - Generates deterministic `ROADMAP.md` with fixed section order.
85
124
  - Uses stable task IDs: `<!-- rs:task=<slug> -->`.
86
125
  - Sync marks `[x]` only when validation passes.
126
+ - `sync --audit` currently runs sync and then prints a mismatch summary; it is not yet a dedicated read-only audit mode.
87
127
  - Validation evidence gate:
88
128
  - code OR test OR artifact evidence required.
89
129
  - test evidence required for code tasks when test frameworks are detected.
@@ -113,26 +153,27 @@ Create `roadmap-skill.config.json`:
113
153
  {
114
154
  "roadmapFile": "./ROADMAP.md",
115
155
  "agentsFile": "./AGENTS.md",
116
-
117
- // Forward-compatible fields — recognized by the skill/agent for Zero Mode discovery context,
118
- // but not yet read by the generator or validator. Safe to add now; they will be wired in a future release.
119
- "northStar": "Ship a self-hosted CLI tool for website capture and AI-readable design analysis.",
120
- "targetUser": "Frontend developers, full-stack developers, and AI coding agents.",
121
- "problemStatement": "Developers lack a unified tool to capture screenshots, crawl pages, extract assets, and export structured context.",
122
- "v1Outcome": "A stable CLI that captures full-page screenshots, crawls internal links, exports metadata, and produces an AI-readable report.",
123
- "antiGoals": [
124
- "Do not bypass authentication",
125
- "Do not target private systems without authorization"
126
- ],
127
- "risks": [
128
- "Browser automation instability",
129
- "Scope creep into generic scraping"
130
- ],
131
- "exitCriteria": [
132
- "CLI works against a public test site",
133
- "Screenshots and metadata are exported deterministically",
134
- "README documents safe and authorized usage"
135
- ],
156
+ "roadmapProfile": "professional",
157
+ "product": {
158
+ "name": "My Project",
159
+ "northStar": "Ship a self-hosted CLI tool for website capture and AI-readable design analysis.",
160
+ "positioning": "What makes this different from alternatives.",
161
+ "primaryUser": "Frontend developers, full-stack developers, and AI coding agents.",
162
+ "targetOutcome": "A stable CLI that captures full-page screenshots, crawls internal links, exports metadata, and produces an AI-readable report.",
163
+ "antiGoals": [
164
+ "Do not bypass authentication",
165
+ "Do not target private systems without authorization"
166
+ ],
167
+ "risks": [
168
+ "Browser automation instability",
169
+ "Scope creep into generic scraping"
170
+ ],
171
+ "successCriteria": [
172
+ "CLI works against a public test site",
173
+ "Screenshots and metadata are exported deterministically",
174
+ "README documents safe and authorized usage"
175
+ ]
176
+ },
136
177
 
137
178
  "taskMatchers": [
138
179
  {
@@ -229,17 +270,16 @@ module.exports = {
229
270
  ## Example Usage
230
271
 
231
272
  ```bash
232
- roadmapsmith init
233
- roadmapsmith generate --project-root .
273
+ roadmapsmith zero
274
+ roadmapsmith maintain
234
275
  roadmapsmith validate --json
235
- roadmapsmith sync --audit
236
276
  roadmapsmith sync --dry-run
237
277
  ```
238
278
 
239
279
  ## Dry Run and Audit
240
280
 
241
281
  - `--dry-run`: shows file diff preview without writing.
242
- - `--audit`: reports roadmap/code mismatches:
282
+ - `--audit`: currently runs sync and then reports roadmap/code mismatches:
243
283
  - checked without evidence
244
284
  - ready but unchecked
245
285
 
@@ -249,6 +289,8 @@ roadmapsmith sync --dry-run
249
289
  npm test
250
290
  ```
251
291
 
292
+ 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.
293
+
252
294
  ## Publishing
253
295
 
254
296
  ```bash
@@ -258,6 +300,12 @@ npm publish --access public
258
300
  git push origin main --follow-tags
259
301
  ```
260
302
 
303
+ Repository-specific release note:
304
+
305
+ - The canonical release automation lives in `.github/workflows/ci.yml`.
306
+ - This repository publishes from GitHub Actions on `main`; local `npm publish` is a maintainer workflow, not the default repo release path.
307
+ - Before publishing, verify the UX/release gate in `docs/release-ux-gate.md` and update `CHANGELOG.md` with the user-visible behavior changes.
308
+
261
309
  ## Versioning Strategy
262
310
 
263
311
  - `patch`: bug fixes and non-breaking validation/generation improvements.