@houseofwolvesllc/claude-scrum-skill 1.8.0 → 1.8.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/README.md +6 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -66,12 +66,16 @@ PRD (optional) --> /project-orchestrate
|
|
|
66
66
|
# Global install — available in all projects
|
|
67
67
|
npm install -g @houseofwolvesllc/claude-scrum-skill
|
|
68
68
|
|
|
69
|
-
# Local install — this project only
|
|
70
|
-
npm install @houseofwolvesllc/claude-scrum-skill
|
|
69
|
+
# Local install — this project only (developer tooling → devDependencies)
|
|
70
|
+
npm install --save-dev @houseofwolvesllc/claude-scrum-skill
|
|
71
|
+
# or the shorthand:
|
|
72
|
+
npm install -D @houseofwolvesllc/claude-scrum-skill
|
|
71
73
|
```
|
|
72
74
|
|
|
73
75
|
Global install copies skills to `~/.claude/skills/`. Local install copies them to `<project>/.claude/skills/` and adds `.claude-scrum-skill` to your `.gitignore`.
|
|
74
76
|
|
|
77
|
+
> **Why `--save-dev`?** This package is developer tooling — the skills are consumed by Claude Code at planning/build/iteration time, never by your application's runtime. Saving to `devDependencies` (instead of `dependencies`) keeps it out of production installs (`npm ci --production`, `NODE_ENV=production`, Docker production layers), avoids running the postinstall script in environments where `~/.claude/skills/` doesn't exist, and accurately reflects that the package isn't a runtime requirement. Same category as `eslint`, `prettier`, `vitest`, etc.
|
|
78
|
+
|
|
75
79
|
Skills surface in Claude Code with their plain names: `/project-scaffold`, `/project-orchestrate`, `/sprint-plan`, etc.
|
|
76
80
|
|
|
77
81
|
> **Heads-up on re-installs:** the postinstall script overwrites every file under `<install-dir>/skills/` with the package's shipped version. If you've customized `<install-dir>/skills/shared/config.json` (e.g., changed `paths.specs` or `paths.adr`), back it up before re-running `npm install` and restore your values afterward. Skill files outside the shipped set are left alone — only files that exist in the package are overwritten.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@houseofwolvesllc/claude-scrum-skill",
|
|
3
|
-
"version": "1.8.
|
|
3
|
+
"version": "1.8.1",
|
|
4
4
|
"description": "Claude Code skills for scrum project management — PRD to production release pipeline with project scaffolding, sprint planning, status tracking, sprint releases, full-project emulation testing, autonomous orchestration, and project cleanup.",
|
|
5
5
|
"bin": {},
|
|
6
6
|
"publishConfig": {
|