planrails 0.4.0 → 0.4.1
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/CHANGELOG.md +6 -0
- package/PLANNER.md +1 -1
- package/README.md +5 -4
- package/bin/planrails.mjs +1 -1
- package/package.json +1 -1
- package/tools/check-plans.mjs +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,11 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.4.1 — 2026-09-13
|
|
4
|
+
|
|
5
|
+
- The Claude Code skill is `/planrails`, not `/plan`, because Claude Code has a
|
|
6
|
+
`/plan` of its own. Install it at `~/.claude/skills/planrails/`; the README and
|
|
7
|
+
the sentence `init` prints say so. Nothing else changed.
|
|
8
|
+
|
|
3
9
|
## 0.4.0 — 2026-09-13
|
|
4
10
|
|
|
5
11
|
A review of 0.3.0 against a real multi-session plan, the Claude Code docs, and
|
package/PLANNER.md
CHANGED
package/README.md
CHANGED
|
@@ -92,11 +92,12 @@ The checker needs Node to run. If your project has no Node at all, skip it — t
|
|
|
92
92
|
plan still works, and your agent enforces the gate the way `PLANNER.md` says. The
|
|
93
93
|
planner method does not depend on any language.
|
|
94
94
|
|
|
95
|
-
### As a `/
|
|
95
|
+
### As a `/planrails` command in Claude Code
|
|
96
96
|
|
|
97
|
-
Copy [`skill/`](skill) to `~/.claude/skills/
|
|
98
|
-
flow in any project that has run `npx planrails init` — the skill reads
|
|
99
|
-
project's own copy of `PLANNER.md`, so every project follows the version it
|
|
97
|
+
Copy [`skill/`](skill) to `~/.claude/skills/planrails/`. Then `/planrails` starts
|
|
98
|
+
the same flow in any project that has run `npx planrails init` — the skill reads
|
|
99
|
+
the project's own copy of `PLANNER.md`, so every project follows the version it
|
|
100
|
+
has. (It is not called `/plan`, because Claude Code has a `/plan` of its own.)
|
|
100
101
|
|
|
101
102
|
## How a plan works
|
|
102
103
|
|
package/bin/planrails.mjs
CHANGED
|
@@ -83,7 +83,7 @@ function init(args) {
|
|
|
83
83
|
console.log(`
|
|
84
84
|
Next:
|
|
85
85
|
1. Tell your agent: Follow .project-management/planrails/PLANNER.md and tell me when you are ready to plan <the feature> with me.
|
|
86
|
-
(Or, in Claude Code, use /
|
|
86
|
+
(Or, in Claude Code, use /planrails if you installed the skill.)
|
|
87
87
|
2. Add to the command you run before every commit:
|
|
88
88
|
node .project-management/planrails/check-plans.mjs
|
|
89
89
|
3. When the agent writes a plan, it adds one line to your CLAUDE.md so the plan
|
package/package.json
CHANGED
package/tools/check-plans.mjs
CHANGED