specrails-core 3.5.3 → 3.7.0

package/docs/README.md

@@ -13,7 +13,7 @@ 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 `/specrails:setup` wizard |
+| [Installation & Setup](installation.md) | Detailed setup, prerequisites, the `/specrails:enrich` wizard, TUI installer |
 | [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 `/specrails:implement`, `/specrails:get-backlog-specs`, and more |

package/docs/changelog.md

@@ -4,6 +4,23 @@ All notable changes to SpecRails are listed here, newest first.
 
 ---
 
+## [Unreleased]
+
+### Breaking changes
+
+- **`/specrails:setup` renamed to `/specrails:enrich`** — The setup wizard is now invoked as `/specrails:enrich`. The `--lite` flag is now `--quick` (both are accepted during the transition period). Update any scripts or documentation that reference `/specrails:setup`.
+
+### New features
+
+- **TUI installer** — `npx specrails-core@latest init` now launches an interactive terminal UI before copying files. Select which agents to install and choose a model preset (balanced/budget/max). Results are saved to `.specrails/install-config.yaml`.
+- **`/specrails:enrich --from-config`** — Non-interactive enrichment mode. Reads `.specrails/install-config.yaml` (written by the TUI installer) and runs the full AI analysis without prompts.
+- **`/specrails:enrich --quick`** — Quick setup mode: three questions, sensible defaults, done in under a minute.
+- **`npx specrails-core enrich`** — New CLI subcommand that runs `/specrails:enrich` via Claude CLI directly from the terminal.
+- **`install-config.yaml` schema** — Declarative configuration file for reproducible installations. Supports agent selection, model presets, and per-agent model overrides.
+- **`integration-contract.json`** — Hub integration contract describing provider commands, tier configurations, checkpoint names, and model presets for hub integrations.
+
+---
+
 ## [1.7.0](https://github.com/fjpulidop/specrails-core/compare/v1.6.1...v1.7.0) — 2026-03-20
 
 ### New commands

package/docs/customization.md

@@ -4,7 +4,7 @@ Everything SpecRails generates is editable markdown. Here's how to adapt it to y
 
 ## What gets generated
 
-After running `/specrails:setup`, your project data lives in `.specrails/` (plugin method) or `.claude/` (scaffold method):
+After running `/specrails:enrich`, your project data lives in `.specrails/` (plugin method) or `.claude/` (scaffold method):
 
 **Plugin method — `.specrails/`**
 
@@ -54,20 +54,50 @@ Example — adding a constraint to the developer:
 
 ### Agent model selection
 
-Each agent specifies its model in YAML frontmatter:
+Agent models are controlled by `.specrails/agents.yaml`, generated automatically when you first run `/specrails:enrich`. The model preset can also be set ahead of time in `.specrails/install-config.yaml` (written by the TUI installer).
 
 ```yaml
----
-model: sonnet
----
+# specrails agent configuration
+# Valid models: opus, sonnet, haiku
+
+defaults:
+  model: sonnet
+
+agents:
+  sr-architect:
+    model: sonnet
+  sr-product-manager:
+    model: opus
+  sr-product-analyst:
+    model: haiku
+  # ... all 14 agents listed
 ```
 
-Available models:
+**Valid models:**
 - `opus` — best for creative/strategic tasks (Product Manager)
 - `sonnet` — balanced for implementation tasks (most agents)
 - `haiku` — fast and cheap for analysis tasks (Product Analyst)
 
-Change the model by editing the frontmatter.
+**Precedence rules:**
+1. Per-agent entry in `agents:` section overrides everything
+2. `defaults.model` applies to any agent not explicitly listed
+3. Template hard-coded value is the fallback when no config exists
+
+**Applying config changes:** After editing `.specrails/agents.yaml`, run `/specrails:reconfig` to update the generated agent files without re-running the full setup wizard:
+
+```
+/specrails:reconfig
+```
+
+Output example:
+```
+Updated 1 agent(s):
+  sr-developer: sonnet → opus
+
+Unchanged (13): sr-architect, sr-reviewer, ...
+```
+
+**Important:** `/specrails:reconfig` wins over direct edits to `.claude/agents/sr-*.md`. If you edit an agent file directly, that change will be overwritten the next time you run reconfig or setup. For permanent per-agent overrides, edit `.specrails/agents.yaml` instead.
 
 ### Adding a new agent
 

package/docs/getting-started.md

@@ -37,15 +37,15 @@ npx specrails-core@latest init --root-dir <your-project>
 
 See [installation.md](installation.md) for full details on both methods and when to use each.
 
-## Run the Setup Wizard
+## Run the Enrich Wizard
 
 Open Claude Code in your project and run:
 
 ```
-/specrails:setup
+/specrails:enrich
 ```
 
-By default, `/specrails:setup` runs the **full 5-phase wizard** — deep stack analysis, researched user personas, and fully adapted agents.
+By default, `/specrails:enrich` runs the **full 5-phase wizard** — deep stack analysis, researched user personas, and fully adapted agents.
 
 | Phase | What happens |
 |-------|-------------|
@@ -55,7 +55,7 @@ By default, `/specrails:setup` runs the **full 5-phase wizard** — deep stack a
 | **4. Generate** | Generates your project data files (`.specrails/`) with project-specific context |
 | **5. Cleanup** | Removes the wizard scaffolding, leaving only your tailored workflow files |
 
-**In a hurry?** Run `/specrails:setup --lite` for the quick version: three questions, sensible defaults, done in under a minute.
+**In a hurry?** Run `/specrails:enrich --quick` for the quick version: three questions, sensible defaults, done in under a minute.
 
 | Question | What it configures |
 |----------|-------------------|
@@ -63,7 +63,7 @@ By default, `/specrails:setup` runs the **full 5-phase wizard** — deep stack a
 | Who are the target users? | Persona stubs for product discovery |
 | Git access — read-only or read-write? | Whether agents can commit |
 
-Lite mode installs the four core agents (architect, developer, reviewer, product manager), all workflow commands, and local ticket storage. You can run the full wizard later to deepen the configuration.
+Quick mode installs the four core agents (architect, developer, reviewer, product manager), all workflow commands, and local ticket storage. You can run the full wizard later to deepen the configuration.
 
 After either mode, your project data files are ready to use and your `/specrails:*` commands are live.
 

package/docs/installation.md

@@ -78,32 +78,39 @@ git clone https://github.com/fjpulidop/specrails-core.git
 
 ### What the scaffold installer does
 
-1. **Checks prerequisites** — validates Git, Claude Code; optionally installs npm and gh
-2. **Detects existing setup** — warns if SpecRails artifacts already exist
-3. **Installs artifacts:**
-   - `.claude/commands/specrails/setup.md` — the `/specrails:setup` wizard
-   - `.specrails/setup-templates/` — agent and command templates (temporary, removed after `/specrails:setup`)
+The `npx specrails-core@latest init` command now includes a **TUI installer** that runs before copying files:
+
+1. **TUI agent selection** — Interactive terminal UI lets you select which agents to install and choose a model preset (balanced/budget/max). Writes `.specrails/install-config.yaml`.
+2. **Checks prerequisites** — validates Git, Claude Code; optionally installs npm and gh
+3. **Detects existing setup** — warns if SpecRails artifacts already exist
+4. **Installs artifacts:**
+   - `.claude/commands/specrails/enrich.md` — the `/specrails:enrich` wizard
+   - `.specrails/setup-templates/` — agent and command templates (temporary, removed after `/specrails:enrich`)
    - `.claude/security-exemptions.yaml` — security scanner config
-4. **Tracks version** — writes `.specrails/specrails-version` and `.specrails/specrails-manifest.json`
+5. **Tracks version** — writes `.specrails/specrails-version` and `.specrails/specrails-manifest.json`
+
+To skip the TUI and use an existing config: `npx specrails-core@latest init --from-config`
+To skip the TUI and use all defaults: `npx specrails-core@latest init --yes`
 
 The scaffold installer only copies files. It does not modify your existing code, create commits, or push to any remote.
 
 ---
 
-## The Setup Wizard
+## The Enrich Wizard
 
 After either installation method, open Claude Code (or Codex) in your project and run:
 
 ```
-/specrails:setup
+/specrails:enrich
 ```
 
-There are two modes:
+There are three modes:
 
 | Mode | Command | When to use |
 |------|---------|-------------|
-| **Full wizard** (default) | `/specrails:setup` | Deep stack analysis, researched personas, fully adapted agents — takes 5–10 min |
-| **Lite** | `/specrails:setup --lite` | Fastest path — 3 questions, sensible defaults, done in under a minute |
+| **Full wizard** (default) | `/specrails:enrich` | Deep stack analysis, researched personas, fully adapted agents — takes 5–10 min |
+| **Quick** | `/specrails:enrich --quick` | Fastest path — 3 questions, sensible defaults, done in under a minute |
+| **From-config** | `/specrails:enrich --from-config` | Non-interactive — reads `.specrails/install-config.yaml` from TUI installer |
 
 ---
 
@@ -111,6 +118,8 @@ There are two modes:
 
 The full 5-phase wizard — takes 5–10 minutes and produces deeply adapted agents.
 
+> **Note:** If the TUI installer already captured agent and model preferences, use `/specrails:enrich --from-config` to apply them non-interactively.
+
 ### Phase 1: Codebase Analysis
 
 The wizard scans your project to detect:
@@ -209,15 +218,15 @@ The wizard fills all templates with your project-specific context:
 
 The wizard removes itself:
 
-- Deletes `.claude/commands/specrails/setup.md`
+- Deletes `.claude/commands/specrails/enrich.md`
 - Deletes `.specrails/setup-templates/`
 - Leaves only the final generated files
 
-After this phase, `/specrails:setup` is no longer available until re-run — your workflow is ready.
+After this phase, `/specrails:enrich` is no longer available until re-run — your workflow is ready.
 
 ---
 
-### Lite Mode (`/specrails:setup --lite`)
+### Quick Mode (`/specrails:enrich --quick`)
 
 The quick path — three questions, sensible defaults, done in under a minute.
 
@@ -238,6 +247,43 @@ You can run the full wizard later to deepen configuration: personas, stack analy
 
 ---
 
+### From-Config Mode (`/specrails:enrich --from-config`)
+
+Runs a fully automated installation using `.specrails/install-config.yaml`. No interactive prompts — all decisions come from the config file written by the TUI installer.
+
+**Config schema** (`.specrails/install-config.yaml`):
+
+```yaml
+version: 1
+provider: claude        # claude | codex | auto
+tier: full              # full | quick
+agents:
+  selected:             # list of agent names to install
+    - sr-architect
+    - sr-developer
+    - sr-reviewer
+    - sr-test-writer
+    - sr-product-manager
+  excluded: []          # agent names to skip
+models:
+  preset: balanced      # balanced | budget | max
+  overrides: {}         # per-agent overrides: { sr-architect: opus }
+quick_context:
+  product_description: ""   # product description seed
+  target_users: ""          # target users seed
+agent_teams: false      # install team-review/team-debug commands
+```
+
+**Model presets:**
+
+| Preset | Description |
+|--------|-------------|
+| `balanced` (default) | Opus for architect + PM, Sonnet for all others |
+| `budget` | Haiku for all agents |
+| `max` | Opus for all agents |
+
+---
+
 ## Verify installation
 
 After setup, verify everything is in place:
@@ -302,7 +348,7 @@ The installer warns if SpecRails artifacts already exist. You can:
 
 ### Placeholders not resolved
 
-If you see `{{PLACEHOLDER}}` in generated files (scaffold method), the `/specrails:setup` wizard didn't complete. Re-run `/specrails:setup` or manually fill the values.
+If you see `{{PLACEHOLDER}}` in generated files (scaffold method), the `/specrails:enrich` wizard didn't complete. Re-run `/specrails:enrich` or manually fill the values.
 
 ---
 

package/docs/migration-guide.md

@@ -118,11 +118,11 @@ The original JIRA key is preserved in `metadata.jira_key` so you can cross-refer
 
 ## Step 3: Regenerate commands (optional but recommended)
 
-Command templates are generated at `/specrails:setup` time with provider-specific instructions baked in. After switching providers, regenerate them so commands use the local file operations instead of GitHub/JIRA CLI calls:
+Command templates are generated at `/specrails:enrich` time with provider-specific instructions baked in. After switching providers, regenerate them so commands use the local file operations instead of GitHub/JIRA CLI calls:
 
 ```bash
 npx specrails-core@latest init --root-dir .
-> /specrails:setup --update
+> /specrails:enrich --update
 ```
 
 The `--update` flag regenerates only the backlog commands (`get-backlog-specs`, `auto-propose-backlog-specs`, `implement`) without re-running the full stack analysis.
@@ -134,7 +134,7 @@ The `--update` flag regenerates only the backlog commands (`get-backlog-specs`,
 To revert to GitHub Issues:
 
 1. Edit `.specrails/config.yaml` (or `.specrails/backlog-config.json` for scaffold installs) and set `provider: github`
-2. Re-run `/specrails:setup --update` to regenerate commands
+2. Re-run `/specrails:enrich --update` to regenerate commands
 3. Your `local-tickets.json` is preserved — switch back any time
 
 Local tickets and external provider data are independent. Switching providers does not delete tickets from either system.

package/docs/plugin-architecture.md

@@ -12,7 +12,7 @@ SpecRails separates **logic** (the plugin) from **project data** (your repo).
 │  agents · skills · hooks · refs     │
 │  updated via: claude plugin update  │
 └────────────────┬────────────────────┘
-                 │  /specrails:setup generates
+                 │  /specrails:enrich generates
                  ▼
 ┌─────────────────────────────────────┐
 │       .specrails/ (project data)    │
@@ -36,7 +36,7 @@ You never edit these directly. To update them, run `claude plugin update sr`.
 
 ### What lives in your project (`.specrails/`)
 
-`/specrails:setup` generates ~8–10 files adapted to your specific codebase:
+`/specrails:enrich` generates ~8–10 files adapted to your specific codebase:
 
 | File | Description |
 |------|-------------|
@@ -57,7 +57,7 @@ SpecRails supports three installation paths:
 
 ```bash
 claude plugin install sr   # install
-/specrails:setup                  # configure for your project
+/specrails:enrich                 # configure for your project
 claude plugin update sr    # update logic anytime
 ```
 
@@ -66,11 +66,11 @@ claude plugin update sr    # update logic anytime
 ### 2. Claude Code scaffold
 
 ```bash
-npx specrails-core@latest init --root-dir .   # copy templates
-/specrails:setup                                      # configure
+npx specrails-core@latest init --root-dir .   # TUI agent selection + copy templates
+/specrails:enrich --from-config               # AI analysis using your saved config
 ```
 
-The scaffold copies the full agent+command set into `.claude/` — you own and version those files. Updates require re-running `npx` and re-running `/specrails:setup`.
+The scaffold copies the full agent+command set into `.claude/` — you own and version those files. The `init` command now includes a TUI installer that lets you select agents and model preset. Updates require re-running `npx` and re-running `/specrails:enrich`.
 
 **Best for:** Teams that want to version the agent prompts themselves, or projects that need full offline control.
 
@@ -79,16 +79,16 @@ The scaffold copies the full agent+command set into `.claude/` — you own and v
 ```bash
 npx specrails-core@latest init --root-dir .   # same as scaffold
 codex                                          # open Codex
-/specrails:setup                                      # configure
+/specrails:enrich                             # configure
 ```
 
 Codex does not support the Claude Code plugin system. Use the scaffold method.
 
 **Best for:** OpenAI Codex CLI users.
 
-## The `/specrails:setup` wizard
+## The `/specrails:enrich` wizard
 
-`/specrails:setup` is a 5-phase setup wizard that generates your project data. It runs once (or re-runs to regenerate).
+`/specrails:enrich` is a 5-phase wizard that generates your project data. It runs once (or re-runs to regenerate).
 
 | Phase | Output |
 |-------|--------|
@@ -98,7 +98,9 @@ Codex does not support the Claude Code plugin system. Use the scaffold method.
 | **4. Generate** | Writes `.specrails/config.yaml`, personas, rules, CLAUDE.md |
 | **5. Cleanup** | Removes wizard scaffolding |
 
-Quick mode: `/specrails:setup --lite` — three questions, done in under a minute.
+Quick mode: `/specrails:enrich --quick` — three questions, done in under a minute.
+
+From-config mode: `/specrails:enrich --from-config` — reads `.specrails/install-config.yaml` (written by the TUI installer) and runs non-interactively.
 
 ## OpenSpec skills
 
@@ -127,7 +129,7 @@ Updates agents, skills, hooks, and references. Does not touch `.specrails/` proj
 ### Regenerate project data
 
 ```bash
-/specrails:setup
+/specrails:enrich
 ```
 
 Re-runs the wizard and regenerates `.specrails/`. Useful when your stack changes significantly or you want to refresh personas.

package/docs/user-docs/faq.md

@@ -8,7 +8,7 @@ Yes. SpecRails runs on top of Claude Code, which requires an Anthropic account.
 
 **What does the installer actually do to my project?**
 
-The plugin method (`claude plugin install sr`) installs logic into Claude Code's plugin system — nothing is added to your project until you run `/specrails:setup`. The scaffold method (`npx specrails-core@latest init`) copies templates into `.claude/`. Neither method modifies your source code, creates commits, or pushes anything.
+The plugin method (`claude plugin install sr`) installs logic into Claude Code's plugin system — nothing is added to your project until you run `/specrails:enrich`. The scaffold method (`npx specrails-core@latest init`) launches a TUI to select agents and model preset, writes `.specrails/install-config.yaml`, then copies templates into `.claude/`. Neither method modifies your source code, creates commits, or pushes anything.
 
 **Do I need Node.js if my project is not JavaScript?**
 
@@ -23,11 +23,11 @@ No. SpecRails ships with a built-in local ticket system — no GitHub account re
 /specrails:implement "add rate limiting to the API"
 ```
 
-You can switch to GitHub Issues or JIRA during `/specrails:setup` (Phase 3) if you prefer.
+You can switch to GitHub Issues or JIRA during `/specrails:enrich` (Phase 3) if you prefer.
 
-**How long does /specrails:setup take?**
+**How long does /specrails:enrich take?**
 
-The full wizard takes about 5 minutes — most of the time is Phase 2 (persona research via web search). For a faster start, use `/specrails:setup --lite`: three questions, under a minute, no web research.
+The full wizard takes about 5 minutes — most of the time is Phase 2 (persona research via web search). For a faster start, use `/specrails:enrich --quick`: three questions, under a minute, no web research.
 
 ---
 
@@ -35,7 +35,7 @@ The full wizard takes about 5 minutes — most of the time is Phase 2 (persona r
 
 **Can I run SpecRails on an existing project with existing code?**
 
-Yes, that's the intended use case. The `/specrails:setup` wizard analyzes your existing codebase — your tech stack, layers, CI commands, and conventions — and generates agents configured specifically for it.
+Yes, that's the intended use case. The `/specrails:enrich` wizard analyzes your existing codebase — your tech stack, layers, CI commands, and conventions — and generates agents configured specifically for it.
 
 **Does /specrails:implement always create a PR?**
 
@@ -77,7 +77,7 @@ For layer-specific coding conventions, edit `.specrails/rules/*.md` (plugin) or
 
 **What is a VPC persona?**
 
-VPC stands for Value Proposition Canvas. Personas are structured profiles of your target users with their Jobs (what they're trying to accomplish), Pains (what frustrates them), and Gains (what they want). The Product Manager and Architect use these to make better design decisions. They're generated during `/specrails:setup` and stored in `.specrails/personas/` (plugin) or `.claude/agents/personas/` (scaffold).
+VPC stands for Value Proposition Canvas. Personas are structured profiles of your target users with their Jobs (what they're trying to accomplish), Pains (what frustrates them), and Gains (what they want). The Product Manager and Architect use these to make better design decisions. They're generated during `/specrails:enrich` and stored in `.specrails/personas/` (plugin) or `.claude/agents/personas/` (scaffold).
 
 ---
 
@@ -85,11 +85,11 @@ VPC stands for Value Proposition Canvas. Personas are structured profiles of you
 
 **Does SpecRails work with monorepos?**
 
-Yes. During `/specrails:setup`, the architect detects your monorepo structure and generates separate layer configurations for each package or service.
+Yes. During `/specrails:enrich`, the architect detects your monorepo structure and generates separate layer configurations for each package or service.
 
 **Which languages and frameworks are supported?**
 
-SpecRails works with any stack. The agents are general-purpose and adapt based on what `/specrails:setup` detects in your codebase. It's been used with Node.js, Python, Go, Ruby, Rust, and mixed-stack projects.
+SpecRails works with any stack. The agents are general-purpose and adapt based on what `/specrails:enrich` detects in your codebase. It's been used with Node.js, Python, Go, Ruby, Rust, and mixed-stack projects.
 
 **Does it work with private repositories?**
 
@@ -113,7 +113,7 @@ Scaffold method:
 npx specrails-core@latest init --root-dir .
 ```
 
-Then re-run `/specrails:setup` to regenerate project data with any new templates. See the [updating guide](../updating.md) for details.
+Then re-run `/specrails:enrich` to regenerate project data with any new templates. See the [updating guide](../updating.md) for details.
 
 **How do I know which version is installed?**
 
@@ -125,13 +125,13 @@ cat .specrails/specrails-version
 
 ## Troubleshooting
 
-**The /specrails:setup command isn't available after installing.**
+**The /specrails:enrich command isn't available after installing.**
 
 For the plugin method: make sure the plugin is installed (`claude plugin list` should show `sr`). For the scaffold method: Claude Code loads commands from `.claude/commands/` — make sure you opened Claude Code from inside your project directory.
 
 **Generated files contain `{{PLACEHOLDER}}` text.**
 
-The `/specrails:setup` wizard did not complete all phases. Re-run `/specrails:setup` — it will pick up where it left off.
+The `/specrails:enrich` wizard did not complete all phases. Re-run `/specrails:enrich` — it will pick up where it left off.
 
 **The pipeline created a PR but the CI checks failed.**
 

package/docs/user-docs/getting-started-codex.md

@@ -73,24 +73,24 @@ your-project/
 
 ---
 
-## Configure with setup
+## Configure with enrich
 
-After installation, open Codex and run the setup skill:
+After installation, open Codex and run the enrich skill:
 
 ```bash
 codex
 ```
 
-Then invoke the setup skill:
+Then invoke the enrich skill:
 
 ```
-/specrails:setup
+/specrails:enrich
 ```
 
 Or run it non-interactively:
 
 ```bash
-codex exec "run /specrails:setup --yes"
+codex exec "run /specrails:enrich --yes"
 ```
 
 The wizard runs 5 phases:
@@ -186,7 +186,7 @@ The installer warns if SpecRails artifacts already exist. You can merge or abort
 
 ### Placeholders not resolved
 
-If you see `{{PLACEHOLDER}}` in generated files, `/specrails:setup` did not complete. Re-run `/specrails:setup` or fill the values manually.
+If you see `{{PLACEHOLDER}}` in generated files, `/specrails:enrich` did not complete. Re-run `/specrails:enrich` or fill the values manually.
 
 ---
 

package/docs/user-docs/installation.md

@@ -1,6 +1,6 @@
 # Installation
 
-Install SpecRails into any git repository in two steps: install, then run `/specrails:setup` inside your AI CLI.
+Install SpecRails into any git repository in two steps: install, then run `/specrails:enrich` inside your AI CLI.
 
 SpecRails supports both **Claude Code** and **OpenAI Codex**. The installer detects which CLI you have and configures accordingly. See [Codex vs Claude Code](codex-vs-claude-code.md) for a feature comparison.
 
@@ -69,7 +69,7 @@ The installer copies templates and commands into `.claude/` (Claude Code) or `.c
 ```
 your-project/
 └── .claude/
-    ├── commands/specrails/setup.md      # The /specrails:setup wizard
+    ├── commands/specrails/enrich.md     # The /specrails:enrich wizard
     ├── skills/                   # Workflow skills (/specrails:*, /opsx:*)
     ├── agents/                   # Agent definitions
     ├── rules/                    # Per-layer coding conventions
@@ -90,7 +90,7 @@ your-project/
 
 The installer also writes `.specrails/specrails-version` and `.specrails/specrails-manifest.json` to track the installed version.
 
-## Configure with /specrails:setup
+## Configure with /specrails:enrich
 
 After either installation method, open your AI CLI in your project and run:
 
@@ -101,10 +101,10 @@ codex     # Codex
 ```
 
 ```
-/specrails:setup
+/specrails:enrich
 ```
 
-By default, `/specrails:setup` runs the full 5-phase wizard:
+By default, `/specrails:enrich` runs the full 5-phase wizard:
 
 | Phase | What happens |
 |-------|-------------|
@@ -114,7 +114,9 @@ By default, `/specrails:setup` runs the full 5-phase wizard:
 | **4. Generate** | Generates project data files (`.specrails/` or `.claude/`) with your context |
 | **5. Cleanup** | Removes setup scaffolding, leaving only your tailored workflow |
 
-**In a hurry?** Run `/specrails:setup --lite` instead — three questions, sensible defaults, done in under a minute.
+**In a hurry?** Run `/specrails:enrich --quick` instead — three questions, sensible defaults, done in under a minute.
+
+**Already ran the TUI installer?** If you used `npx specrails-core@latest init` and completed the TUI agent selection, run `/specrails:enrich --from-config` to apply your saved configuration without re-answering the prompts.
 
 ## Verify
 
@@ -151,7 +153,7 @@ The installer warns if SpecRails artifacts already exist. You can merge (install
 
 ### Placeholders not resolved
 
-If you see `{{PLACEHOLDER}}` in generated files (scaffold method), the `/specrails:setup` wizard did not complete. Re-run `/specrails:setup` or fill the values manually.
+If you see `{{PLACEHOLDER}}` in generated files (scaffold method), the `/specrails:enrich` wizard did not complete. Re-run `/specrails:enrich` or fill the values manually.
 
 ### "No Claude API key configured"
 

package/docs/user-docs/quick-start.md

@@ -29,7 +29,7 @@ npx specrails-core@latest init --root-dir .
 
 Your existing code is not touched by either method.
 
-## Step 2: Run the setup wizard
+## Step 2: Run the enrich wizard
 
 Open Claude Code in your project:
 
@@ -40,7 +40,7 @@ claude
 Then run:
 
 ```
-/specrails:setup
+/specrails:enrich
 ```
 
 The wizard runs the full 5-phase setup (about 5 minutes). It analyzes your codebase and configures SpecRails for your specific project:
@@ -69,7 +69,9 @@ Phase 5/5  Cleanup complete.
 ✓ SpecRails is ready. Run /specrails:implement to start building.
 ```
 
-**In a hurry?** Use `/specrails:setup --lite` for a 3-question quick setup (under a minute). You can always run the full wizard later.
+**In a hurry?** Use `/specrails:enrich --quick` for a 3-question quick setup (under a minute). You can always run the full wizard later.
+
+**Used the TUI installer?** If the `npx specrails-core@latest init` TUI already collected your agent and model choices, run `/specrails:enrich --from-config` to apply them automatically.
 
 ## Step 3: Implement your first feature