specrails-core 3.3.0 → 3.4.0

package/commands/setup.md

@@ -52,11 +52,11 @@ Read the following files to understand the current installation state:
    ```
    Template files are named with `sr-` prefix (e.g., `sr-architect.md`, `sr-developer.md`).
 
-5. List all template files in `$SPECRAILS_DIR/setup-templates/commands/sr/` — these are the NEW command templates from the update:
+5. List all template files in `$SPECRAILS_DIR/setup-templates/commands/specrails/` — these are the NEW command templates from the update:
    ```bash
-   ls $SPECRAILS_DIR/setup-templates/commands/sr/
+   ls $SPECRAILS_DIR/setup-templates/commands/specrails/
    ```
-   Command template files include `implement.md`, `batch-implement.md`, `health-check.md`, `compat-check.md`, `refactor-recommender.md`, `why.md`, `product-backlog.md`, `update-product-driven-backlog.md`.
+   Command template files include `implement.md`, `batch-implement.md`, `compat-check.md`, `refactor-recommender.md`, `why.md`, `product-backlog.md`, `update-product-driven-backlog.md`.
    If this directory does not exist, skip command template checking for this update.
 
 6. Read `$SPECRAILS_DIR/backlog-config.json` if it exists — contains stored provider configuration needed for command placeholder substitution.
@@ -94,16 +94,16 @@ Build three lists for agents:
 2. **New agents**: template file exists in `.claude/setup-templates/agents/` but the agent name is NOT in the manifest → mark for evaluation
 3. **Unchanged agents**: agent name exists in manifest AND checksum matches → skip
 
-**Command templates:** If `.claude/setup-templates/commands/sr/` exists, for each command template file, find its entry in the manifest's `artifacts` map (keyed as `templates/commands/sr/<name>.md`). Compute the SHA-256 checksum of the corresponding file in `.claude/setup-templates/commands/sr/`:
+**Command templates:** If `.claude/setup-templates/commands/specrails/` exists, for each command template file, find its entry in the manifest's `artifacts` map (keyed as `templates/commands/specrails/<name>.md`). Compute the SHA-256 checksum of the corresponding file in `.claude/setup-templates/commands/specrails/`:
 
 ```bash
-sha256sum .claude/setup-templates/commands/sr/<name>.md
+sha256sum .claude/setup-templates/commands/specrails/<name>.md
 ```
 
 Build three lists for commands:
 
 1. **Changed commands**: command name exists in manifest AND the current template checksum differs from the manifest checksum → mark for update
-2. **New commands**: template file exists in `.claude/setup-templates/commands/sr/` but the command name is NOT in the manifest → mark for evaluation
+2. **New commands**: template file exists in `.claude/setup-templates/commands/specrails/` but the command name is NOT in the manifest → mark for evaluation
 3. **Unchanged commands**: command name exists in manifest AND checksum matches → skip
 
 Display the combined analysis to the user:
@@ -130,7 +130,6 @@ Display the combined analysis to the user:
 - refactor-recommender.md
 
 ### Commands — Unchanged (keeping current)
-- health-check.md
 - compat-check.md
 - why.md
 ```
@@ -177,7 +176,7 @@ grep -r '{{[A-Z_]*}}' .codex/agents/sr-*.toml 2>/dev/null || echo "OK: no broken
 For each command in the "changed commands" list from Phase U3:
 
 1. Read the NEW template:
-   - If `cli_provider == "claude"`: from `$SPECRAILS_DIR/setup-templates/commands/sr/<name>.md`
+   - If `cli_provider == "claude"`: from `$SPECRAILS_DIR/setup-templates/commands/specrails/<name>.md`
    - If `cli_provider == "codex"`: from `$SPECRAILS_DIR/setup-templates/skills/sr-<name>/SKILL.md`
 2. Read stored backlog configuration from `$SPECRAILS_DIR/backlog-config.json` (if it exists) to resolve provider-specific placeholders:
    - `BACKLOG_PROVIDER` → `provider` field (`github`, `jira`, or `none`)
@@ -195,16 +194,16 @@ For each command in the "changed commands" list from Phase U3:
    - `{{BACKLOG_PREFLIGHT}}` → provider-specific preflight check from backlog config
    - Any other `{{PLACEHOLDER}}` values → use Phase U2 analysis data
 4. Write the updated file:
-   - If `cli_provider == "claude"`: to `.claude/commands/sr/<name>.md`
+   - If `cli_provider == "claude"`: to `.claude/commands/specrails/<name>.md`
    - If `cli_provider == "codex"`: to `.agents/skills/sr-<name>/SKILL.md`
 5. Show:
-   - If `cli_provider == "claude"`: `✓ Updated /sr:<name>`
+   - If `cli_provider == "claude"`: `✓ Updated /specrails:<name>`
    - If `cli_provider == "codex"`: `✓ Updated $sr-<name>`
 
 After updating all changed commands/skills, verify no unresolved placeholders remain:
 ```bash
 # If cli_provider == "claude":
-grep -l '{{[A-Z_]*}}' .claude/commands/sr/*.md 2>/dev/null || echo "OK: no broken placeholders"
+grep -l '{{[A-Z_]*}}' .claude/commands/specrails/*.md 2>/dev/null || echo "OK: no broken placeholders"
 # If cli_provider == "codex":
 grep -rl '{{[A-Z_]*}}' .agents/skills/sr-*/SKILL.md 2>/dev/null || echo "OK: no broken placeholders"
 ```
@@ -231,17 +230,17 @@ For each agent in the "new" list:
 For each command in the "new commands" list from Phase U3:
 
 1. Read the template:
-   - If `cli_provider == "claude"`: from `$SPECRAILS_DIR/setup-templates/commands/sr/<name>.md`
+   - If `cli_provider == "claude"`: from `$SPECRAILS_DIR/setup-templates/commands/specrails/<name>.md`
    - If `cli_provider == "codex"`: from `$SPECRAILS_DIR/setup-templates/skills/sr-<name>/SKILL.md`
 2. Prompt the user:
-   - If `cli_provider == "claude"`: `"New command available: /sr:<name> — [one-line description]. Install it? [Y/n]"`
+   - If `cli_provider == "claude"`: `"New command available: /specrails:<name> — [one-line description]. Install it? [Y/n]"`
    - If `cli_provider == "codex"`: `"New skill available: $sr-<name> — [one-line description]. Install it? [Y/n]"`
 3. If the user accepts (or presses Enter):
    - Apply placeholder substitution using the same rules as Phase U4b (backlog config + codebase analysis)
-   - If `cli_provider == "claude"`: write to `.claude/commands/sr/<name>.md` — show `✓ Added /sr:<name>`
+   - If `cli_provider == "claude"`: write to `.claude/commands/specrails/<name>.md` — show `✓ Added /specrails:<name>`
    - If `cli_provider == "codex"`: write to `.agents/skills/sr-<name>/SKILL.md` — show `✓ Added $sr-<name>`
 4. If the user declines:
-   - If `cli_provider == "claude"`: show `→ Skipped /sr:<name>`
+   - If `cli_provider == "claude"`: show `→ Skipped /specrails:<name>`
    - If `cli_provider == "codex"`: show `→ Skipped $sr-<name>`
 
 ### Phase U6: Update Workflow Commands
@@ -249,12 +248,12 @@ For each command in the "new commands" list from Phase U3:
 If any new agents were added in Phase U5:
 
 1. Read the implement command/skill:
-   - If `cli_provider == "claude"`: `.claude/commands/sr/implement.md`
+   - If `cli_provider == "claude"`: `.claude/commands/specrails/implement.md`
    - If `cli_provider == "codex"`: `.agents/skills/sr-implement/SKILL.md`
 2. Check if the file references agent names in its orchestration steps (look for `sr-architect`, `sr-developer`, `sr-reviewer` etc.)
 3. If newly added agents belong in the implementation pipeline (i.e., they are layer-specific developers such as `sr-frontend-developer` or `sr-backend-developer`), add them to the appropriate step in the implement command — specifically where parallel developer agents are launched
 4. Write the updated file if any changes were made:
-   - If `cli_provider == "claude"`: `.claude/commands/sr/implement.md`
+   - If `cli_provider == "claude"`: `.claude/commands/specrails/implement.md`
    - If `cli_provider == "codex"`: `.agents/skills/sr-implement/SKILL.md`
 5. Show which commands were updated, or "No command updates needed" if nothing changed
 
@@ -302,7 +301,7 @@ All agents and commands are now up to date.
 Update `.specrails-manifest.json` to reflect the new checksums for all regenerated/updated and added agents and commands:
 - For each regenerated agent: update its checksum entry to the new template's checksum (keyed as `templates/agents/sr-<name>.md`)
 - For each added agent: add a new entry with its checksum
-- For each updated command: update its checksum entry to the new template's checksum (keyed as `templates/commands/sr/<name>.md`)
+- For each updated command: update its checksum entry to the new template's checksum (keyed as `templates/commands/specrails/<name>.md`)
 - For each added command: add a new entry with its checksum
 - Update the `version` field to the version read from `.specrails-version`
 
@@ -352,9 +351,9 @@ Store as `QS_IS_EXISTING_CODEBASE=true/false`.
 Before generating files, check if this is a re-run:
 
 1. Check if commands/skills already exist:
-   - If `cli_provider == "claude"`: check if `.claude/commands/sr/` directory exists with any `.md` files:
+   - If `cli_provider == "claude"`: check if `.claude/commands/specrails/` directory exists with any `.md` files:
      ```bash
-     ls .claude/commands/sr/*.md 2>/dev/null
+     ls .claude/commands/specrails/*.md 2>/dev/null
      ```
    - If `cli_provider == "codex"`: check if `.agents/skills/sr-*/SKILL.md` files exist:
      ```bash
@@ -365,13 +364,13 @@ Before generating files, check if this is a re-run:
 
 In re-run mode, QS3 executes in **gap-fill mode** for command/skill files:
 - For each command in the list, check if it already exists:
-  - If `cli_provider == "claude"`: at `.claude/commands/sr/<name>.md`
+  - If `cli_provider == "claude"`: at `.claude/commands/specrails/<name>.md`
   - If `cli_provider == "codex"`: at `.agents/skills/sr-<name>/SKILL.md`
 - If it exists: skip it and show:
-  - Claude: `✓ Already installed: /sr:<name>`
+  - Claude: `✓ Already installed: /specrails:<name>`
   - Codex: `✓ Already installed: $sr-<name>`
 - If it does NOT exist: install it and show:
-  - Claude: `✓ Added /sr:<name> (was missing)`
+  - Claude: `✓ Added /specrails:<name> (was missing)`
   - Codex: `✓ Added $sr-<name> (was missing)`
 - Do NOT prompt the user for confirmation on missing files — install them automatically
 
@@ -419,7 +418,6 @@ Core commands (always install if missing):
 - `implement.md`
 - `batch-implement.md`
 - `propose-spec.md`
-- `health-check.md`
 - `compat-check.md`
 - `why.md`
 - `product-backlog.md`
@@ -438,11 +436,11 @@ Core commands (always install if missing):
 
 **If `cli_provider == "claude"`:**
 
-If `QS_IS_RERUN=false` (fresh install): for each core command, read the template from `$SPECRAILS_DIR/setup-templates/commands/sr/<name>.md`, substitute the backlog placeholders with local values (using the same table as Phase 4.3 "Local Tickets"), stub all persona placeholders with `(Lite Mode — run /setup to configure personas)`, then write to `.claude/commands/sr/<name>.md`.
+If `QS_IS_RERUN=false` (fresh install): for each core command, read the template from `$SPECRAILS_DIR/setup-templates/commands/specrails/<name>.md`, substitute the backlog placeholders with local values (using the same table as Phase 4.3 "Local Tickets"), stub all persona placeholders with `(Lite Mode — run /setup to configure personas)`, then write to `.claude/commands/specrails/<name>.md`.
 
-If `QS_IS_RERUN=true` (gap-fill mode): for each command in the list above, check if `.claude/commands/sr/<name>.md` already exists:
-- If it exists: skip it — show `✓ Already installed: /sr:<name>`
-- If it does NOT exist: read template, substitute placeholders as above, write to `.claude/commands/sr/<name>.md` — show `✓ Added /sr:<name> (was missing)`
+If `QS_IS_RERUN=true` (gap-fill mode): for each command in the list above, check if `.claude/commands/specrails/<name>.md` already exists:
+- If it exists: skip it — show `✓ Already installed: /specrails:<name>`
+- If it does NOT exist: read template, substitute placeholders as above, write to `.claude/commands/specrails/<name>.md` — show `✓ Added /specrails:<name> (was missing)`
 
 **If `cli_provider == "codex"`:**
 
@@ -463,25 +461,25 @@ Remove `commands/setup.md` from `.claude/commands/` if it was copied there by th
 After generating all files, display the setup complete message.
 
 Then, based on `QS_IS_EXISTING_CODEBASE`:
-- **Existing codebase** (`true`): recommend `/sr:health-check`
-- **New project** (`false`): recommend `/sr:product-backlog`
+- **Existing codebase** (`true`): recommend `/specrails:refactor-recommender`
+- **New project** (`false`): recommend `/specrails:product-backlog`
 
 If `QS_IS_RERUN=false`, display:
 ```
 ✅ Setup complete.
 
 Try your first command:
-  > /sr:product-backlog
+  > /specrails:product-backlog
 ```
-(Replace `/sr:product-backlog` with `/sr:health-check` for existing codebases.)
+(Replace `/specrails:product-backlog` with `/specrails:refactor-recommender` for existing codebases.)
 
 If `QS_IS_RERUN=true`, display the gap-fill summary and stop:
 ```
 ✅ Re-run complete.
 
 Commands status:
-  ✓ Already installed: /sr:<name>
-  ✓ Added /sr:<name> (was missing)
+  ✓ Already installed: /specrails:<name>
+  ✓ Added /specrails:<name> (was missing)
   [... one line per command ...]
 
 All commands are up to date.
@@ -915,8 +913,8 @@ Store the full configuration in `.claude/backlog-config.json`:
 
 #### If None
 
-- Skip `/sr:product-backlog` and `/sr:update-product-driven-backlog` commands.
-- The `/sr:implement` command will still work with text descriptions.
+- Skip `/specrails:product-backlog` and `/specrails:update-product-driven-backlog` commands.
+- The `/specrails:implement` command will still work with text descriptions.
 
 ### 3.3 Git & shipping workflow
 
@@ -945,15 +943,14 @@ If automatic, also check if `gh` is authenticated (for PR creation). If not, war
 
 | Command | Purpose | Requires |
 |---------|---------|----------|
-| /sr:implement | Full pipeline: sr-architect → sr-developer → sr-reviewer → ship | sr-architect + sr-developer + sr-reviewer |
-| /sr:batch-implement | Orchestrate multiple features in dependency-aware waves | sr-architect + sr-developer + sr-reviewer |
-| /sr:propose-spec | Interactively propose and refine a feature spec, then create a GitHub issue | GitHub CLI |
-| /sr:product-backlog | View prioritized backlog with VPC scores | sr-product-analyst + Backlog provider |
-| /sr:update-product-driven-backlog | Generate new feature ideas via product discovery | sr-product-manager + Backlog provider |
-| /sr:health-check | Run tests, linting, coverage, complexity, and dependency audit | None |
-| /sr:compat-check | Snapshot API surface and detect breaking changes | None |
-| /sr:refactor-recommender | Scan for refactoring opportunities ranked by impact/effort | None |
-| /sr:why | Search past architectural decisions from agent memory | None |
+| /specrails:implement | Full pipeline: sr-architect → sr-developer → sr-reviewer → ship | sr-architect + sr-developer + sr-reviewer |
+| /specrails:batch-implement | Orchestrate multiple features in dependency-aware waves | sr-architect + sr-developer + sr-reviewer |
+| /specrails:propose-spec | Interactively propose and refine a feature spec, then create a GitHub issue | GitHub CLI |
+| /specrails:product-backlog | View prioritized backlog with VPC scores | sr-product-analyst + Backlog provider |
+| /specrails:update-product-driven-backlog | Generate new feature ideas via product discovery | sr-product-manager + Backlog provider |
+| /specrails:compat-check | Snapshot API surface and detect breaking changes | None |
+| /specrails:refactor-recommender | Scan for refactoring opportunities ranked by impact/effort | None |
+| /specrails:why | Search past architectural decisions from agent memory | None |
 
 [All] [Custom selection]
 ```
@@ -1081,23 +1078,21 @@ Write each persona to `$SPECRAILS_DIR/agents/personas/`:
 For each selected command, read the template and adapt.
 
 **If `cli_provider == "claude"` (default):**
-- `setup-templates/commands/sr/implement.md` → `.claude/commands/sr/implement.md`
-- `setup-templates/commands/sr/batch-implement.md` → `.claude/commands/sr/batch-implement.md`
-- `setup-templates/commands/sr/propose-spec.md` → `.claude/commands/sr/propose-spec.md`
-- `setup-templates/commands/sr/product-backlog.md` → `.claude/commands/sr/product-backlog.md` (if `BACKLOG_PROVIDER != none`)
-- `setup-templates/commands/sr/update-product-driven-backlog.md` → `.claude/commands/sr/update-product-driven-backlog.md` (if `BACKLOG_PROVIDER != none`)
-- `setup-templates/commands/sr/health-check.md` → `.claude/commands/sr/health-check.md`
-- `setup-templates/commands/sr/compat-check.md` → `.claude/commands/sr/compat-check.md`
-- `setup-templates/commands/sr/refactor-recommender.md` → `.claude/commands/sr/refactor-recommender.md`
-- `setup-templates/commands/sr/why.md` → `.claude/commands/sr/why.md`
+- `setup-templates/commands/specrails/implement.md` → `.claude/commands/specrails/implement.md`
+- `setup-templates/commands/specrails/batch-implement.md` → `.claude/commands/specrails/batch-implement.md`
+- `setup-templates/commands/specrails/propose-spec.md` → `.claude/commands/specrails/propose-spec.md`
+- `setup-templates/commands/specrails/product-backlog.md` → `.claude/commands/specrails/product-backlog.md` (if `BACKLOG_PROVIDER != none`)
+- `setup-templates/commands/specrails/update-product-driven-backlog.md` → `.claude/commands/specrails/update-product-driven-backlog.md` (if `BACKLOG_PROVIDER != none`)
+- `setup-templates/commands/specrails/compat-check.md` → `.claude/commands/specrails/compat-check.md`
+- `setup-templates/commands/specrails/refactor-recommender.md` → `.claude/commands/specrails/refactor-recommender.md`
+- `setup-templates/commands/specrails/why.md` → `.claude/commands/specrails/why.md`
 
 **If `cli_provider == "codex"`:**
 - `setup-templates/skills/sr-implement/SKILL.md` → `.agents/skills/sr-implement/SKILL.md`
 - `setup-templates/skills/sr-batch-implement/SKILL.md` → `.agents/skills/sr-batch-implement/SKILL.md`
-- `setup-templates/commands/sr/propose-spec.md` → `.agents/skills/sr-propose-spec/SKILL.md` (wrap with YAML frontmatter if no skill template exists)
-- `setup-templates/commands/sr/product-backlog.md` → `.agents/skills/sr-product-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
-- `setup-templates/commands/sr/update-product-driven-backlog.md` → `.agents/skills/sr-update-product-driven-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
-- `setup-templates/skills/sr-health-check/SKILL.md` → `.agents/skills/sr-health-check/SKILL.md`
+- `setup-templates/commands/specrails/propose-spec.md` → `.agents/skills/sr-propose-spec/SKILL.md` (wrap with YAML frontmatter if no skill template exists)
+- `setup-templates/commands/specrails/product-backlog.md` → `.agents/skills/sr-product-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
+- `setup-templates/commands/specrails/update-product-driven-backlog.md` → `.agents/skills/sr-update-product-driven-backlog/SKILL.md` (if `BACKLOG_PROVIDER != none`; wrap with frontmatter)
 - `setup-templates/skills/sr-compat-check/SKILL.md` → `.agents/skills/sr-compat-check/SKILL.md`
 - `setup-templates/skills/sr-refactor-recommender/SKILL.md` → `.agents/skills/sr-refactor-recommender/SKILL.md`
 - `setup-templates/skills/sr-why/SKILL.md` → `.agents/skills/sr-why/SKILL.md`
@@ -1115,7 +1110,7 @@ metadata:
 ---
 ```
 
-For both providers, create the output directory before writing (`mkdir -p` for `.claude/commands/sr/` or `.agents/skills/sr-<name>/`).
+For both providers, create the output directory before writing (`mkdir -p` for `.claude/commands/specrails/` or `.agents/skills/sr-<name>/`).
 
 Adapt:
 - CI commands to match detected stack
@@ -1320,7 +1315,7 @@ After cleanup, verify that only the intended files remain:
 # If cli_provider == "claude":
 ls .claude/agents/sr-*.md
 ls .claude/agents/personas/*.md
-ls .claude/commands/sr/*.md
+ls .claude/commands/specrails/*.md
 ls .claude/rules/*.md
 ls .claude/agent-memory/
 
@@ -1376,15 +1371,14 @@ Display the complete installation summary:
 [If cli_provider == "claude":]
 | Command | File |
 |---------|------|
-| /sr:implement | .claude/commands/sr/implement.md |
-| /sr:batch-implement | .claude/commands/sr/batch-implement.md |
-| /sr:propose-spec | .claude/commands/sr/propose-spec.md |
-| /sr:product-backlog | .claude/commands/sr/product-backlog.md |
-| /sr:update-product-driven-backlog | .claude/commands/sr/update-product-driven-backlog.md |
-| /sr:health-check | .claude/commands/sr/health-check.md |
-| /sr:compat-check | .claude/commands/sr/compat-check.md |
-| /sr:refactor-recommender | .claude/commands/sr/refactor-recommender.md |
-| /sr:why | .claude/commands/sr/why.md |
+| /specrails:implement | .claude/commands/specrails/implement.md |
+| /specrails:batch-implement | .claude/commands/specrails/batch-implement.md |
+| /specrails:propose-spec | .claude/commands/specrails/propose-spec.md |
+| /specrails:product-backlog | .claude/commands/specrails/product-backlog.md |
+| /specrails:update-product-driven-backlog | .claude/commands/specrails/update-product-driven-backlog.md |
+| /specrails:compat-check | .claude/commands/specrails/compat-check.md |
+| /specrails:refactor-recommender | .claude/commands/specrails/refactor-recommender.md |
+| /specrails:why | .claude/commands/specrails/why.md |
 [If cli_provider == "codex":]
 | Skill | File |
 |-------|------|
@@ -1393,7 +1387,6 @@ Display the complete installation summary:
 | $sr-propose-spec | .agents/skills/sr-propose-spec/SKILL.md |
 | $sr-product-backlog | .agents/skills/sr-product-backlog/SKILL.md |
 | $sr-update-product-driven-backlog | .agents/skills/sr-update-product-driven-backlog/SKILL.md |
-| $sr-health-check | .agents/skills/sr-health-check/SKILL.md |
 | $sr-compat-check | .agents/skills/sr-compat-check/SKILL.md |
 | $sr-refactor-recommender | .agents/skills/sr-refactor-recommender/SKILL.md |
 | $sr-why | .agents/skills/sr-why/SKILL.md |
@@ -1417,9 +1410,9 @@ Note: Only commands/skills selected during setup are shown. Backlog commands are
 ### Next Steps
 [If cli_provider == "claude":]
 1. Review the generated files in .claude/
-2. Run `/sr:product-backlog` to see your backlog (if GitHub Issues exist)
-3. Run `/sr:update-product-driven-backlog` to generate feature ideas
-4. Run `/sr:implement #issue-number` to implement a feature
+2. Run `/specrails:product-backlog` to see your backlog (if GitHub Issues exist)
+3. Run `/specrails:update-product-driven-backlog` to generate feature ideas
+4. Run `/specrails:implement #issue-number` to implement a feature
 5. Commit the .claude/ directory to version control
 [If cli_provider == "codex":]
 1. Review the generated files in .codex/ and .agents/skills/
@@ -1430,9 +1423,9 @@ Note: Only commands/skills selected during setup are shown. Backlog commands are
 
 ### Quick Start
 [If cli_provider == "claude":]
-- `/sr:implement "describe a feature"` — implement something right now
-- `/sr:product-backlog` — see prioritized feature ideas
-- `/sr:update-product-driven-backlog` — discover new features using VPC
+- `/specrails:implement "describe a feature"` — implement something right now
+- `/specrails:product-backlog` — see prioritized feature ideas
+- `/specrails:update-product-driven-backlog` — discover new features using VPC
 [If cli_provider == "codex":]
 - `$sr-implement "describe a feature"` — implement something right now
 - `$sr-product-backlog` — see prioritized feature ideas
@@ -1449,7 +1442,7 @@ After displaying the setup complete summary above, detect the project type and o
 
 Try your first spec:
 [If cli_provider == "claude":]
-  > /sr:product-backlog
+  > /specrails:product-backlog
 [If cli_provider == "codex":]
   > $sr-product-backlog
 ```
@@ -1460,9 +1453,9 @@ Try your first spec:
 
 Try your first spec:
 [If cli_provider == "claude":]
-  > /sr:health-check
+  > /specrails:refactor-recommender
 [If cli_provider == "codex":]
-  > $sr-health-check
+  > $sr-refactor-recommender
 ```
 
 Then stop.

package/docs/README.md

@@ -13,9 +13,10 @@ Welcome to the SpecRails docs. This guide will take you from zero to a fully aut
 
 | Guide | What it covers |
 |-------|----------------|
-| [Installation & Setup](installation.md) | Detailed setup, prerequisites, the `/setup` wizard |
+| [Installation & Setup](installation.md) | Detailed setup, prerequisites, the `/specrails:setup` wizard |
+| [Plugin Architecture](plugin-architecture.md) | Plugin vs scaffold, what lives where, how updates work |
 | [Agents](agents.md) | Every agent explained — role, when it runs, why it exists |
-| [Workflows & Commands](workflows.md) | How to use `/sr:implement`, `/sr:product-backlog`, and more |
+| [Workflows & Commands](workflows.md) | How to use `/specrails:implement`, `/specrails:product-backlog`, and more |
 | [Customization](customization.md) | Adapt agents, rules, personas, and conventions to your project |
 | [Updating](updating.md) | Keep SpecRails up to date without losing your customizations |
 

package/docs/agents.md

@@ -21,7 +21,7 @@ The result: better quality at every stage, with clear accountability.
 |-|-|
 | **Color** | Blue |
 | **Model** | Opus (creative reasoning) |
-| **Trigger** | `/opsx:explore`, `/sr:update-product-driven-backlog` |
+| **Trigger** | `/opsx:explore`, `/specrails:update-product-driven-backlog` |
 | **Role** | Feature ideation and product strategy |
 
 The Product Manager is the **starting point** of the pipeline. It researches your competitive landscape (via web search), evaluates ideas against your user personas using the VPC framework, and produces prioritized feature recommendations.
@@ -42,7 +42,7 @@ The Product Manager is the **starting point** of the pipeline. It researches you
 |-|-|
 | **Color** | Cyan |
 | **Model** | Haiku (fast, read-only) |
-| **Trigger** | `/sr:product-backlog` |
+| **Trigger** | `/specrails:product-backlog` |
 | **Role** | Backlog analysis and reporting |
 
 The Product Analyst is a **read-only** agent. It reads your backlog, specs, and archived changes to produce structured reports. It never writes code or makes decisions — it just gives you the data.
@@ -62,7 +62,7 @@ The Product Analyst is a **read-only** agent. It reads your backlog, specs, and
 |-|-|
 | **Color** | Green |
 | **Model** | Sonnet |
-| **Trigger** | `/opsx:ff`, `/opsx:continue`, `/sr:implement` (Phase 3a) |
+| **Trigger** | `/opsx:ff`, `/opsx:continue`, `/specrails:implement` (Phase 3a) |
 | **Role** | System design and task breakdown |
 
 The Architect translates **what to build** into **how to build it**. It reads the relevant specs, analyzes the codebase, and produces a detailed implementation design with ordered tasks.
@@ -76,7 +76,7 @@ The Architect translates **what to build** into **how to build it**. It reads th
 - Risks and considerations
 - Backwards compatibility impact report (Phase 6 auto-check against API surface)
 
-The Architect also records decision rationale in `.claude/agent-memory/explanations/` — queryable later with `/sr:why`.
+The Architect also records decision rationale in `.claude/agent-memory/explanations/` — queryable later with `/specrails:why`.
 
 ---
 
@@ -86,7 +86,7 @@ The Architect also records decision rationale in `.claude/agent-memory/explanati
 |-|-|
 | **Color** | Purple |
 | **Model** | Sonnet |
-| **Trigger** | `/opsx:apply`, `/sr:implement` (Phase 3b) |
+| **Trigger** | `/opsx:apply`, `/specrails:implement` (Phase 3b) |
 | **Role** | Full-stack implementation |
 
 The Developer is the **workhorse**. It reads the Architect's design, loads the relevant layer conventions, and writes production-quality code across all layers. It follows a strict process: understand, plan, implement, verify.
@@ -106,7 +106,7 @@ Before starting implementation, the Developer reads any **failure records** from
 |-|-|
 | **Colors** | Purple (backend), Blue (frontend) |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` with parallel pipeline |
+| **Trigger** | `/specrails:implement` with parallel pipeline |
 | **Role** | Layer-specific implementation |
 
 For large full-stack features, SpecRails can split work between **Backend Developer** and **Frontend Developer** running in **parallel git worktrees**. Each has a lighter prompt focused on their stack and runs only the relevant CI checks.
@@ -121,7 +121,7 @@ For large full-stack features, SpecRails can split work between **Backend Develo
 |-|-|
 | **Color** | Cyan |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 3c) |
+| **Trigger** | `/specrails:implement` (Phase 3c) |
 | **Role** | Automated test generation |
 
 After the Developer finishes, the Test Writer generates comprehensive tests for the new code. It auto-detects your test framework, reads 3 existing tests to learn your patterns, and targets >80% coverage of new code.
@@ -143,7 +143,7 @@ After the Developer finishes, the Test Writer generates comprehensive tests for
 |-|-|
 | **Color** | Yellow |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 3d) |
+| **Trigger** | `/specrails:implement` (Phase 3d) |
 | **Role** | Keep documentation in sync with code |
 
 Doc Sync detects and updates your project's documentation after implementation:
@@ -162,7 +162,7 @@ Doc Sync detects and updates your project's documentation after implementation:
 |-|-|
 | **Color** | Cyan |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 4b, parallel) |
+| **Trigger** | `/specrails:implement` (Phase 4b, parallel) |
 | **Role** | Frontend-specific quality audit |
 
 The Frontend Reviewer runs in parallel with the Backend Reviewer during Phase 4b, specializing in client-side concerns that a generalist reviewer might miss.
@@ -180,7 +180,7 @@ The Frontend Reviewer runs in parallel with the Backend Reviewer during Phase 4b
 |-|-|
 | **Color** | Cyan |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 4b, parallel) |
+| **Trigger** | `/specrails:implement` (Phase 4b, parallel) |
 | **Role** | Backend-specific quality audit |
 
 The Backend Reviewer runs in parallel with the Frontend Reviewer during Phase 4b, specializing in server-side concerns.
@@ -199,7 +199,7 @@ The Backend Reviewer runs in parallel with the Frontend Reviewer during Phase 4b
 |-|-|
 | **Color** | Orange |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 4) |
+| **Trigger** | `/specrails:implement` (Phase 4) |
 | **Role** | Security audit |
 
 The Security Reviewer scans new code for:
@@ -221,7 +221,7 @@ You can suppress known false positives via `.claude/security-exemptions.yaml`.
 |-|-|
 | **Color** | Red |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 4b), after all developers complete |
+| **Trigger** | `/specrails:implement` (Phase 4b), after all developers complete |
 | **Role** | Final quality gate |
 
 The Reviewer is the **last agent before ship**. It:
@@ -251,7 +251,7 @@ The Reviewer is the **last agent before ship**. It:
 |-|-|
 | **Color** | Yellow |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:merge-resolve`, `/sr:implement` (Phase 4a, after worktree merge) |
+| **Trigger** | `/specrails:merge-resolve`, `/specrails:implement` (Phase 4a, after worktree merge) |
 | **Role** | AI-powered merge conflict resolution |
 
 When a multi-feature pipeline merges worktrees and produces conflict markers, the Merge Resolver analyzes each conflict block using the OpenSpec context bundles from both features. It applies resolutions where confidence is high enough and leaves clean markers for the conflicts it cannot safely resolve.
@@ -273,7 +273,7 @@ When a multi-feature pipeline merges worktrees and produces conflict markers, th
 |-|-|
 | **Color** | Yellow |
 | **Model** | Sonnet |
-| **Trigger** | `/sr:implement` (Phase 4, after Security Reviewer) |
+| **Trigger** | `/specrails:implement` (Phase 4, after Security Reviewer) |
 | **Role** | Performance regression detection |
 
 The Performance Reviewer benchmarks modified code paths after implementation, compares metrics against configured thresholds, and outputs a structured report. It never fixes code — findings above the threshold trigger the Developer to address them before the pipeline continues.
@@ -301,7 +301,7 @@ Every agent stores observations in `.claude/agent-memory/<agent>/MEMORY.md`. Thi
 └── ...
 ```
 
-Memory is automatic — you don't need to manage it. Agents read relevant memories at the start of each task and write new observations as they work. Use `/sr:why` to search the explanations directory in plain language.
+Memory is automatic — you don't need to manage it. Agents read relevant memories at the start of each task and write new observations as they work. Use `/specrails:why` to search the explanations directory in plain language.
 
 ## What's next?
 

package/docs/changelog.md

@@ -8,8 +8,8 @@ All notable changes to SpecRails are listed here, newest first.
 
 ### New commands
 
-- **`/sr:merge-conflict`** — Smart merge conflict resolver. Analyzes conflict context, understands intent of both sides, and proposes the correct resolution with an explanation.
-- **`/sr:refactor-recommender` (enhanced)** — Now includes VPC context-aware scoring: debt items are ranked against persona Jobs/Pains/Gains for product-aligned prioritization.
+- **`/specrails:merge-conflict`** — Smart merge conflict resolver. Analyzes conflict context, understands intent of both sides, and proposes the correct resolution with an explanation.
+- **`/specrails:refactor-recommender` (enhanced)** — Now includes VPC context-aware scoring: debt items are ranked against persona Jobs/Pains/Gains for product-aligned prioritization.
 
 ### Agents
 
@@ -41,8 +41,8 @@ All notable changes to SpecRails are listed here, newest first.
 
 ### New commands
 
-- **`/sr:opsx-diff`** — Change diff visualizer. Shows a structured, human-readable diff of what changed between two points in time across agents, commands, and templates.
-- **`/sr:telemetry`** — Agent telemetry and cost tracking. Reports per-agent token usage, run counts, and cost estimates with trend analysis.
+- **`/specrails:opsx-diff`** — Change diff visualizer. Shows a structured, human-readable diff of what changed between two points in time across agents, commands, and templates.
+- **`/specrails:telemetry`** — Agent telemetry and cost tracking. Reports per-agent token usage, run counts, and cost estimates with trend analysis.
 
 ### Agents
 
@@ -54,8 +54,8 @@ All notable changes to SpecRails are listed here, newest first.
 
 ### New commands
 
-- **`/sr:vpc-drift`** — Detects when your VPC personas have drifted from what your product actually delivers. Compares persona Jobs/Pains/Gains against the backlog and agent memory; produces per-persona alignment scores and concrete update recommendations.
-- **`/sr:memory-inspect`** — Inspect and manage agent memory directories. Shows per-agent stats, recent entries, and stale file detection with optional pruning.
+- **`/specrails:vpc-drift`** — Detects when your VPC personas have drifted from what your product actually delivers. Compares persona Jobs/Pains/Gains against the backlog and agent memory; produces per-persona alignment scores and concrete update recommendations.
+- **`/specrails:memory-inspect`** — Inspect and manage agent memory directories. Shows per-agent stats, recent entries, and stale file detection with optional pruning.
 
 ---
 
@@ -63,7 +63,7 @@ All notable changes to SpecRails are listed here, newest first.
 
 ### New commands
 
-- **`/sr:retry`** — Smart failure recovery. Resumes a failed `/sr:implement` pipeline from the last successful phase without restarting from scratch. Reads saved pipeline state to identify what completed, then re-executes only the remaining phases.
+- **`/specrails:retry`** — Smart failure recovery. Resumes a failed `/specrails:implement` pipeline from the last successful phase without restarting from scratch. Reads saved pipeline state to identify what completed, then re-executes only the remaining phases.
 
 ### Agents
 
@@ -75,7 +75,7 @@ All notable changes to SpecRails are listed here, newest first.
 
 ### Improvements
 
-- **`/sr:health-check` extended with static code analysis** — Now includes complexity metrics, dead code detection, and architectural pattern analysis in addition to test coverage and dependency health.
+- **`/specrails:health-check` extended with static code analysis** — Now includes complexity metrics, dead code detection, and architectural pattern analysis in addition to test coverage and dependency health.
 
 ---
 
@@ -107,7 +107,7 @@ Initial stable release.
 
 ### ⚠ Breaking changes
 
-All commands renamed from `/<name>` to `/sr:<name>`. All agent files renamed from `<name>.md` to `sr-<name>.md`. Existing installations are auto-migrated by `update.sh`.
+All commands renamed from `/<name>` to `/specrails:<name>`. All agent files renamed from `<name>.md` to `sr-<name>.md`. Existing installations are auto-migrated by `update.sh`.
 
 ### What shipped in 1.0
 
@@ -117,17 +117,17 @@ All commands renamed from `/<name>` to `/sr:<name>`. All agent files renamed fro
 - Security Reviewer, Doc Sync, Product Analyst
 
 **11 commands**
-- `/sr:implement` — full 8-phase pipeline (architecture → code → tests → docs → review → PR)
-- `/sr:batch-implement` — parallel multi-feature orchestrator using git worktrees
-- `/sr:health-check` — codebase quality dashboard with regression detection
-- `/sr:compat-check` — backwards compatibility analyzer and migration guide generator
-- `/sr:product-backlog` — VPC-scored backlog view with safe implementation ordering
-- `/sr:update-product-driven-backlog` — AI-powered product discovery via personas
-- `/sr:refactor-recommender` — tech debt scanner ranked by impact/effort
-- `/sr:why` — semantic search over agent decision records
-- `/sr:retry` — smart failure recovery (added in 1.3)
-- `/sr:vpc-drift` — persona drift detection (added in 1.4)
-- `/sr:propose-spec` — structured feature proposal generator
+- `/specrails:implement` — full 8-phase pipeline (architecture → code → tests → docs → review → PR)
+- `/specrails:batch-implement` — parallel multi-feature orchestrator using git worktrees
+- `/specrails:health-check` — codebase quality dashboard with regression detection
+- `/specrails:compat-check` — backwards compatibility analyzer and migration guide generator
+- `/specrails:product-backlog` — VPC-scored backlog view with safe implementation ordering
+- `/specrails:update-product-driven-backlog` — AI-powered product discovery via personas
+- `/specrails:refactor-recommender` — tech debt scanner ranked by impact/effort
+- `/specrails:why` — semantic search over agent decision records
+- `/specrails:retry` — smart failure recovery (added in 1.3)
+- `/specrails:vpc-drift` — persona drift detection (added in 1.4)
+- `/specrails:propose-spec` — structured feature proposal generator
 
 **Pipeline Monitor (web-manager)**
 - Real-time job queue dashboard

package/docs/concepts.md

@@ -153,17 +153,17 @@ Before starting implementation, the Developer reads matching failure records as
 
 The Architect, Developer, and Reviewer record **decision rationale** in `.claude/agent-memory/explanations/` as they work. These records capture the "why" behind implementation choices — which library was chosen and why, which trade-off was accepted, which alternative was rejected.
 
-Use `/sr:why` to search this memory in plain language:
+Use `/specrails:why` to search this memory in plain language:
 
 ```
-/sr:why "why did we switch to event sourcing"
+/specrails:why "why did we switch to event sourcing"
 ```
 
 This gives you an audit trail from product decision to implementation choice, without digging through git history or asking the original author.
 
 ## Dependency-Aware Ordering
 
-When `/sr:product-backlog` is run, the Product Analyst parses `Prerequisites:` fields from GitHub Issue bodies and builds a **dependency DAG** (directed acyclic graph). It then:
+When `/specrails:product-backlog` is run, the Product Analyst parses `Prerequisites:` fields from GitHub Issue bodies and builds a **dependency DAG** (directed acyclic graph). It then:
 
 1. Detects cycles and reports them as errors (circular dependencies block ordering)
 2. Computes a safe implementation order via topological sort