mandrel 1.58.0 → 1.60.0

package/README.md

@@ -31,31 +31,36 @@ package-manager combinations.
 
 ## Quickstart
 
-The canonical cold-start path is one launcher command, then two slash
+The canonical cold-start path is one command, then two slash
 commands inside Claude Code:
 
 ```bash
-npx create-mandrel        # install mandrel → sync → bootstrap
+npx mandrel init        # install mandrel → sync → prompt → bootstrap
 ```
 
 ```text
 # then, inside Claude Code (commands load from .claude/commands/):
-/onboard            # guided first run: stack detect → docs → doctor → /epic-plan
-/epic-plan          # ideation -> PRD/Tech Spec -> Epic/Feature/Story hierarchy
+/onboard            # guided first run: stack detect → docs → doctor → /plan
+/plan          # ideation -> PRD/Tech Spec -> Epic with child Stories
 ```
 
-`create-mandrel` installs `mandrel`, materializes `./.agents/` via
-`mandrel sync`, and runs `node .agents/scripts/bootstrap.js` for you,
-forwarding any flags you pass. `/onboard` then walks you from a clean
-checkout to a planned Epic (stack detection, docs scaffolding, a
-`mandrel doctor` readiness gate, and a started `/epic-plan`). Once you have a
-planned Epic, deliver it with `/epic-deliver <id>` (wave loop → validation →
+`npx mandrel init` installs `mandrel` (when `./.agents/` is absent),
+materializes it via `mandrel sync`, then asks whether to **configure now**
+(option 1 → runs `node .agents/scripts/bootstrap.js`, forwarding any flags you
+pass) or stop at **just the files** (option 2 → re-run `mandrel init` any time
+to configure). Pass `--assume-yes` for a non-interactive run that proceeds
+straight to configure (and forwards the flag to bootstrap). When `./.agents/`
+is already present (you ran `npm install mandrel` first), `init` skips the
+install/sync and goes straight to the prompt. `/onboard` then walks you from a
+clean checkout to a planned Epic (stack detection, docs scaffolding, a
+`mandrel doctor` readiness gate, and a started `/plan`). Once you have a
+planned Epic, deliver it with `/deliver <id>` (wave loop → validation →
 review → retro → open PR).
 
 ### Manual equivalent
 
-If you prefer to drive the three steps `create-mandrel` wraps by hand, run
-them from your project root:
+If you prefer to drive the steps `mandrel init` wraps by hand, run them from
+your project root:
 
 ```bash
 npm install mandrel   # pin an exact, provenance-signed version
@@ -145,14 +150,6 @@ npx mandrel sync                        # re-materialize ./.agents/
 npx mandrel doctor                      # verify the install
 ```
 
-### Migrating from `@mandrelai/agents`
-
-The framework package was renamed from the scoped `@mandrelai/agents` to the
-unscoped `mandrel`. Already on the old name? `mandrel update` does **not**
-auto-migrate (it resolves the package by name), so make the one-time manual
-hop documented in
-[`docs/migrate-mandrelai-to-mandrel.md`](docs/migrate-mandrelai-to-mandrel.md).
-
 ## Contributors
 
 Only `.agents/` is distributed to consumers — it ships inside the