@haus-tech/haus-workflow 0.16.0 → 0.16.2

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## [0.16.2](https://github.com/WeAreHausTech/haus-workflow/compare/v0.16.1...v0.16.2) (2026-06-09)
+
+## [0.16.1](https://github.com/WeAreHausTech/haus-workflow/compare/v0.16.0...v0.16.1) (2026-06-09)
+
 ## [0.16.0](https://github.com/WeAreHausTech/haus-workflow/compare/v0.15.0...v0.16.0) (2026-06-05)
 
 ### Features

package/README.md

@@ -29,13 +29,17 @@ and configures the repo for you.
 
 Once installed, Claude Code gains a `/haus-workflow` slash command.
 
+The `project:*` tasks act on the current repo. The unprefixed verbs (`update`,
+`catalog`, `install`, `uninstall`) manage the haus tool itself on your machine
+(`~/.claude` + npm), like `npm install -g`. The short legacy names still work.
+
 ```
-/haus-workflow          # interactive menu — pick setup, update, refresh, etc.
-/haus-workflow init     # first-time project setup
-/haus-workflow apply    # refresh .claude/ and regenerate CLAUDE.md imports
-/haus-workflow update   # update npm package + catalog + ~/.claude/
-/haus-workflow catalog  # fetch only latest catalog
-/haus-workflow doctor   # health check for drift
+/haus-workflow                 # interactive menu — pick a task
+/haus-workflow project:init    # [project] add haus to an EXISTING repo — AI skills, commands, workflow + docs
+/haus-workflow project:refresh # [project] refresh .claude/ and regenerate CLAUDE.md imports
+/haus-workflow project:doctor  # [project] health check for drift
+/haus-workflow update          # [global]  update npm package + catalog + ~/.claude/
+/haus-workflow catalog         # [global]  fetch only the latest catalog
 ```
 
 Without an argument, the skill presents a menu so you can pick the task. With an argument, it runs immediately.

package/dist/cli.js

@@ -3290,45 +3290,10 @@ async function runSetupCore(root, opts) {
 }
 
 // src/commands/setup-project.ts
-var GUIDED_QUESTIONS = [
-  "What is this project for?",
-  "Is it for a client, internal Haus work, or experimentation?",
-  "What should Claude help with most?",
-  "Is this project connected to other repositories?",
-  "Are there parts of the project Claude should avoid touching?",
-  "Are there client-specific rules or sensitive areas?",
-  "Do you want a minimal, standard, or strict setup?"
-];
 async function runSetupProject(options) {
   const root = process.cwd();
-  let mode = options.guided ? "guided" : "fast";
-  if (!options.guided && !options.fast && !options.json) {
-    log("How do you want to set this project up?");
-    log("1. Guided setup - I'll ask a few simple questions, then scan the project.");
-    log("2. Fast setup - I'll only scan the project and recommend defaults.");
-    const choice = await ask("Choose 1 or 2");
-    mode = choice === "1" ? "guided" : "fast";
-  }
-  if (mode === "guided") {
-    const existing = await readJson(hausPath(root, "setup-answers.json")) ?? {};
-    const merged = {};
-    for (const question of GUIDED_QUESTIONS) {
-      if (options.json) {
-        merged[question] = existing[question] ?? "pending-user-answer";
-        continue;
-      }
-      const prefilled = existing[question];
-      if (prefilled && prefilled !== "pending-user-answer" && prefilled !== "no-answer") {
-        merged[question] = prefilled;
-        continue;
-      }
-      const answer = await ask(question);
-      merged[question] = answer || prefilled || "no-answer";
-    }
-    await writeJson(hausPath(root, "setup-answers.json"), merged);
-  }
   await runSetupCore(root, {
-    mode,
+    mode: "fast",
     json: options.json,
     apply: !options.json,
     dryRun: false,
@@ -4963,7 +4928,7 @@ validateRuntimeNodeVersion();
 program.name("haus").description("Haus AI workflow CLI").version(cliVersion());
 program.command("scan").option("--json").action(runScan);
 program.command("recommend").option("--json").action(runRecommend);
-program.command("setup-project").option("--guided").option("--fast").option("--json").action(runSetupProject);
+program.command("setup-project").option("--json").action(runSetupProject);
 program.command("doctor").option("--hooks", "Verify .claude/settings.json matches the hook contract").action(runDoctor);
 program.command("apply").option("--dry-run").option("--write").option("--select", "Interactively select catalog items before applying").option(
   "--allow-empty-cache",
@@ -4975,7 +4940,7 @@ program.command("apply").option("--dry-run").option("--write").option("--select"
 program.command("undo").option("-y, --yes", "Skip confirmation").action(runUndo);
 program.command("explain-recommendation").option("--json").action(runExplainRecommendation);
 program.command("context").option("--task <task>").option("--from-hook").option("--json").option("--verbose").action(runContext);
-program.command("init").option("--fast").option("--json").action(runInit);
+program.command("init").option("--json").action(runInit);
 program.command("refresh").action(runRefresh);
 program.command("catalog-audit").action(runCatalogAudit);
 program.command("validate-catalog").argument("[manifest]").action(runValidateCatalog);

package/library/catalog/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.4.1",
+  "version": "2.4.2",
   "items": [
     {
       "id": "haus.nextjs-patterns",

package/library/global/commands/haus-setup.md

@@ -4,7 +4,7 @@ commands; they read plain language and approve.
 
 Do this in order:
 
-1. **Detect.** Run `haus setup-project --fast --json`. Read the JSON yourself —
+1. **Detect.** Run `haus setup-project --json`. Read the JSON yourself —
    do not show it. Translate what was detected into one or two plain sentences,
    e.g. "This looks like a Next.js website using Yarn. I found unit tests but no
    end-to-end tests." If the detection status is `unknown` or `partial`, say so

package/library/global/skills/haus-workflow/SKILL.md

@@ -17,16 +17,21 @@ All-in-one entry point for the Haus AI workflow.
 
 ## Task aliases → commands
 
-| Alias(es)                            | Command              | What it does                                   |
-| ------------------------------------ | -------------------- | ---------------------------------------------- |
-| `init`, `setup`                      | `haus init`          | First-time project setup                       |
-| `apply`, `refresh`, `update-project` | `haus apply --write` | Re-run setup / refresh `.claude/` context      |
-| `update`, `upgrade`                  | `haus update`        | Update npm package + catalog + `~/.claude/`    |
-| `catalog`                            | `haus update`        | Fetch latest catalog (same command as update)  |
-| `doctor`, `check`                    | `haus doctor`        | Check for install drift                        |
-| `install`, `global`                  | `haus install`       | Seed `~/.claude/` with haus-owned files        |
-| `uninstall`                          | `haus uninstall`     | Remove all haus global files from `~/.claude/` |
-| `claude-md`, `regenerate`            | `haus apply --write` | Regenerate root `CLAUDE.md` import block       |
+Task names use an asymmetric scope convention. The **project:** namespace marks tasks that
+act on **this repo** (`./.claude`, `./.haus-workflow`) — type `project:` to see them all.
+The unprefixed verbs (`update`, `catalog`, `install`, `uninstall`) act on **this machine's
+haus install** (`~/.claude`, npm) — they manage the haus tool itself, like `npm install -g`.
+The short legacy aliases still work but the names below are canonical.
+
+| Task name (legacy aliases)                                        | Command                 | Scope   | What it does                                                                                |
+| ----------------------------------------------------------------- | ----------------------- | ------- | ------------------------------------------------------------------------------------------- |
+| `project:init` (`setup`, `init`)                                  | _Setup procedure below_ | project | First-time setup of an **existing** repo: adds AI skills, commands, workflow + project docs |
+| `project:refresh` (`apply`, `refresh`, `claude-md`, `regenerate`) | `haus apply --write`    | project | Re-run setup / refresh `.claude/` context + regenerate root `CLAUDE.md` import block        |
+| `project:doctor` (`doctor`, `check`)                              | `haus doctor`           | project | Check for install drift                                                                     |
+| `update` (`upgrade`)                                              | `haus update`           | global  | Update npm package + catalog + `~/.claude/` (also refreshes this project)                   |
+| `catalog`                                                         | `haus update`           | global  | Fetch latest catalog (same command as update)                                               |
+| `install` (`global`)                                              | `haus install`          | global  | Seed `~/.claude/` with haus-owned files                                                     |
+| `uninstall`                                                       | `haus uninstall`        | global  | Remove all haus global files from `~/.claude/`                                              |
 
 ## Step 1 — Determine the task
 
@@ -37,16 +42,14 @@ All-in-one entry point for the Haus AI workflow.
 ```
 Question: "What would you like to do?"
 Options:
-  1. Set up this project for the first time
-     (haus init — scans repo, writes .haus-workflow/, updates CLAUDE.md)
-  2. Refresh project setup
+  1. [project] project:init — add haus to an existing project for the first time
+     (AI skills + commands + workflow into a repo you already have, then a deep read to write the CLAUDE.md docs body + docs/)
+  2. [project] project:refresh — refresh this project's setup
      (haus apply --write — re-runs setup, regenerates CLAUDE.md imports)
-  3. Update haus package + catalog + global files
+  3. [global] update — update haus package + catalog + global files
      (haus update — checks npm for new version, fetches catalog, refreshes ~/.claude/)
-  4. Fetch catalog updates only
+  4. [global] catalog — fetch catalog updates only
      (haus update — same command; pulls latest workflow templates and lockfile)
-  5. Regenerate CLAUDE.md import block
-     (haus apply --write — rewrites the @-import block at the root CLAUDE.md)
 ```
 
 Map the user's selection to the command from the alias table, then continue to Step 2.
@@ -55,21 +58,16 @@ Map the user's selection to the command from the alias table, then continue to S
 
 Run the mapped command via Bash. Quote the exact command you are running before executing it.
 
+**Exception — `project:init` (`setup` / `init`):** this maps to a multi-step procedure, not a single command. Do not run a bare `haus init`. Skip to **Setup (`project:init`)** under Step 3 and follow it.
+
 ## Step 3 — Post-run steps
 
 After the command completes, follow the relevant post-run steps below.
 
-### After `haus init`
-
-1. Open `.haus-workflow/workflow-config.md`.
-2. Check for unfilled placeholders (`TODO`, `n/a`, empty values) in:
-   - Test, lint, typecheck, build commands — confirm against `package.json` scripts.
-   - Docs paths — check whether `docs/SPEC.md`, `docs/DESIGN.md`, `docs/UX.md` exist.
-   - Validation library — check `package.json` dependencies for `zod`, `yup`, `joi`, `valibot`.
-   - Pre-commit tool — check for `.husky/`, `lefthook.yml`, `.pre-commit-config.yaml`.
-   - Highest-stakes logic — ask the user if unclear.
-3. Fill in every unfilled field. Do not leave placeholders.
-4. Confirm with the user that `workflow-config.md` is complete before proceeding.
+### Setup (`project:init`)
+
+1. Open and follow `~/.claude/commands/haus-setup.md` — the installed `haus-setup` command (in some projects also `.claude/commands/haus-setup.md`). Run every step in order. It detects the stack, asks the guided questions, runs `haus apply --write` (scaffolding, skills, commands, rules, docs skill), writes the **project docs** (`CLAUDE.md` body + `docs/`) and `.haus-workflow/deep-context.json`, runs `haus recommend`, applies the newly-matched helpers, and confirms.
+2. Then fill `.haus-workflow/workflow-config.md` — replace every placeholder (`TODO`, `n/a`, empty): test/lint/typecheck/build commands (check `package.json`), docs paths, validation library, pre-commit tool, highest-stakes logic (ask if unclear). Leave none.
 
 ### After `haus apply --write`
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haus-tech/haus-workflow",
-  "version": "0.16.0",
+  "version": "0.16.2",
   "description": "Haus AI workflow CLI for Claude Code.",
   "type": "module",
   "bin": {