@haus-tech/haus-workflow 2.0.0 → 3.0.0

package/library/catalog/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "6.0.0",
+  "version": "6.0.1",
   "manifestFormat": 2,
   "globalPlugins": [
     {
@@ -1270,8 +1270,8 @@
       "path": "configs/eslint/eslint.config.mjs",
       "title": "Haus ESLint config",
       "purpose": "ESLint 9.x flat config for Haus Tech TypeScript/React projects.",
-      "whenToUse": "Recommended when `eslint` is missing from the repo. Run `haus scaffold haus.eslint-config` to copy the config into the project root.",
-      "whenNotToUse": "Do not scaffold if the project already has a custom ESLint config that extends beyond the Haus baseline.",
+      "whenToUse": "Recommended when `eslint` is missing from the repo. Run `haus configs haus.eslint-config` to copy the config into the project root.",
+      "whenNotToUse": "Skip it if the project already has a custom ESLint config that extends beyond the Haus baseline.",
       "tags": ["eslint", "tooling", "quality"],
       "repoRoles": [],
       "requiresAny": [
@@ -1582,8 +1582,8 @@
       "path": "configs/prettier",
       "title": "Haus Prettier config",
       "purpose": "Prettier config and .prettierignore for Haus Tech projects.",
-      "whenToUse": "Recommended when `prettier` is missing from the repo. Run `haus scaffold haus.prettier-config` to copy the config into the project root.",
-      "whenNotToUse": "Do not scaffold if the project already has a custom Prettier config.",
+      "whenToUse": "Recommended when `prettier` is missing from the repo. Run `haus configs haus.prettier-config` to copy the config into the project root.",
+      "whenNotToUse": "Skip it if the project already has a custom Prettier config.",
       "tags": ["prettier", "tooling", "quality"],
       "repoRoles": [],
       "requiresAny": [

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

@@ -29,6 +29,7 @@ repo's files. The short legacy aliases still work but the names below are canoni
 | `project:reinit` (`reinit`, `re-init`)                            | _Reinit procedure below_        | project | **Full re-setup.** Removes all haus-managed project files (backed up first, user content preserved), then re-runs `project:init` from scratch                                                                                                                                             |
 | `project:clone [name]` (`clone`)                                  | _Clone procedure below_         | project | With a `name`: find & clone one repo by name from GitHub. No name: asks single-repo-vs-workspace first, then either mode — workspace mode clones from `repos.manifest.json`                                                                                                               |
 | `project:cloneandsetup [name]` (`cloneandsetup`)                  | _Clone & setup procedure below_ | project | Run `project:clone`, then set up each repo for local dev — deps, databases, cross-repo links, and env — via each repo's `.haus-workflow/localdev.yml` (+ the workspace's order/links/env)                                                                                                 |
+| `project:new [stack] [name]` (`new`, `create`)                    | _New-project procedure below_   | project | Create a **brand-new** project from an allowed stack (Next.js, Vite+React, NestJS, Expo): scaffold, haus configs, git + GitHub repo, then full init                                                                                                                                       |
 | `project:add-skills` (`add-skills`, `opt-in`)                     | _Add-skills procedure below_    | project | Add optional skills, agents, or config (ESLint/Prettier) to an already-set-up project without re-running full setup                                                                                                                                                                       |
 | `project:refresh` (`apply`, `refresh`, `claude-md`, `regenerate`) | _Refresh procedure below_       | project | **Full non-destructive sync.** Updates the haus package + catalog first, then re-runs `project:init`'s pipeline in place — nothing is removed up front; new catalog items get added, changed ones updated, and anything removed upstream gets pruned by `apply`'s existing orphan-pruning |
 | `project:doctor` (`doctor`, `check`)                              | `haus doctor`                   | project | Check for install drift                                                                                                                                                                                                                                                                   |
@@ -43,7 +44,7 @@ repo's files. The short legacy aliases still work but the names below are canoni
 **If a task argument was passed:** look it up in the alias table above. If no match, tell the user and list valid options. If matched, skip to Step 2.
 
 **If no task was passed:** the menu has more options than one `AskUserQuestion` question can
-hold (max 4 options per question). Page through all 12 tasks in batches: each page shows the
+hold (max 4 options per question). Page through all 13 tasks in batches: each page shows the
 next 3 tasks plus a 4th "More options" choice, except the last page, which shows whatever
 tasks remain (≤4) with no continuation choice — nothing is dropped, and this pattern
 generalizes automatically if a task is ever added to or removed from the alias table above
@@ -56,39 +57,41 @@ Question 1: "What would you like to do?"
 Options:
   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 — full non-destructive sync with the latest haus
+  2. [project] project:new [stack] [name] — create a brand-new project from an allowed stack
+     (Next.js, Vite+React, NestJS, Expo — scaffold, haus configs, git + GitHub repo, then full init)
+  3. [project] project:refresh — full non-destructive sync with the latest haus
      (updates the haus package + catalog, then re-runs setup in place — nothing removed first)
-  3. [project] project:clone [name] — clone repos
-     (picked from here with no name yet — clone.md will ask whether it's a single repo or a whole workspace next)
-  4. [—] More options — see: project:cloneandsetup, project:add-skills, project:reinit, and 6 more
+  4. [—] More options — see: project:clone, project:cloneandsetup, project:add-skills, and 7 more
 
 Question 2: "What would you like to do?" (only shown if "More options" was picked)
 Options:
-  1. [project] project:cloneandsetup [name] — clone repos, then set them up for local dev
+  1. [project] project:clone [name] — clone repos
+     (picked from here with no name yet — clone.md will ask whether it's a single repo or a whole workspace next)
+  2. [project] project:cloneandsetup [name] — clone repos, then set them up for local dev
      (project:clone — asking single-repo-vs-workspace since no name is known yet — then per-repo deps + databases + cross-repo links + env from localdev.yml)
-  2. [project] project:add-skills — add optional skills, agents, or config to this project
+  3. [project] project:add-skills — add optional skills, agents, or config to this project
      (offers opt-in helpers matching your stack that aren't installed yet — no full re-setup)
-  3. [project] project:reinit — full re-setup from scratch
-     (removes all haus-managed project files, backed up first, then re-runs project:init)
-  4. [—] More options — see: update, project:doctor, project:fix, and 3 more
+  4. [—] More options — see: project:reinit, update, project:doctor, and 4 more
 
 Question 3: "What would you like to do?" (only shown if "More options" was picked again)
 Options:
-  1. [global] update — update haus package + catalog + global files
+  1. [project] project:reinit — full re-setup from scratch
+     (removes all haus-managed project files, backed up first, then re-runs project:init)
+  2. [global] update — update haus package + catalog + global files
      (haus update — checks npm for new version, fetches catalog, refreshes ~/.claude/)
-  2. [project] project:doctor — check for install drift
+  3. [project] project:doctor — check for install drift
      (haus doctor — a one-line plain-language verdict, healthy or a list of what needs attention)
-  3. [project] project:fix — diagnose and fix install drift
-     (runs doctor, applies the suggested fixes, confirms green)
-  4. [—] More options — see: install, uninstall, help
+  4. [—] More options — see: project:fix, install, uninstall, help
 
 Question 4: "What would you like to do?" (only shown if "More options" was picked a third time — last page, no further continuation)
 Options:
-  1. [global] install — seed ~/.claude/ with haus-owned files
+  1. [project] project:fix — diagnose and fix install drift
+     (runs doctor, applies the suggested fixes, confirms green)
+  2. [global] install — seed ~/.claude/ with haus-owned files
      (haus install)
-  2. [global] uninstall — remove all haus global files from ~/.claude/
+  3. [global] uninstall — remove all haus global files from ~/.claude/
      (haus uninstall)
-  3. [—] help — explain what haus-workflow is and list all available tasks
+  4. [—] help — explain what haus-workflow is and list all available tasks
      (touches no files — points to docs/cli.md and docs/runbook.md for depth)
 ```
 
@@ -98,7 +101,7 @@ 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.
+**Exception — `project:init` (`setup` / `init`):** this maps to a multi-step procedure that drives `haus init --json --dry-run` plus follow-up commands, not a single command. Skip to **Setup (`project:init`)** under Step 3 and follow it.
 
 **Exception — `project:reinit` (`reinit` / `re-init`):** removes files before re-running setup. Skip to **Reinit (`project:reinit`)** under Step 3 and follow it.
 
@@ -106,6 +109,8 @@ Run the mapped command via Bash. Quote the exact command you are running before
 
 **Exception — `project:cloneandsetup` (`cloneandsetup`):** clone followed by a per-repo setup pass, with confirmations. Skip to **Clone & setup (`project:cloneandsetup`)** under Step 3 and follow it.
 
+**Exception — `project:new` (`new` / `create`):** collects the stack/name/org/visibility via `AskUserQuestion` and drives `haus new` non-interactively — not a single command. Skip to **New project (`project:new`)** under Step 3 and follow it.
+
 **Exception — `project:add-skills` (`add-skills` / `opt-in`):** a short scan → recommend → choose → apply procedure. Skip to **Add optional skills (`project:add-skills`)** under Step 3 and follow it.
 
 **Exception — `project:refresh` (`apply` / `refresh` / `claude-md` / `regenerate`):** updates the haus package first, then re-runs the setup pipeline — not a single command. Skip to **Refresh (`project:refresh`)** under Step 3 and follow it.
@@ -164,6 +169,10 @@ upstream gets pruned automatically by `apply`'s existing orphan-pruning.
 
 1. Open and follow `references/cloneandsetup.md` in this skill's directory — it runs the full `project:clone` flow (including clone.md's Step 0 when no name is already known), then sets up each cloned repo locally: selects the node version (`nvm install` from `.nvmrc`), enables corepack, installs JS/PHP dependencies, and seeds `.env`, confirming before each phase. It does not start servers.
 
+### New project (`project:new`)
+
+1. Open and follow `references/new.md` in this skill's directory. It lists allowed stacks via `haus new --list --json`, collects the stack/name/org/visibility with `AskUserQuestion`, previews with `--dry-run`, confirms, then runs `haus new <stack> <name> --json --yes [flags]` for real and narrates the JSON result — including relaying any failure `detail` (resume commands) verbatim and surfacing `installHint`. Never run bare interactive `haus new`.
+
 ### Add optional skills (`project:add-skills`)
 
 For a project that's already set up but where the user wants more helpers later —
@@ -184,8 +193,8 @@ choices.
    with one option per group / config item. Then:
    - Skills/agents → `haus recommend --include <id> <id> …`, then
      `haus apply --write`.
-   - Config → `haus scaffold <id>` (add `--force` only if the user chose to
-     replace an existing file; scaffold preserves files by default).
+   - Config → `haus configs <id>` (add `--force` only if the user chose to
+     replace an existing file; configs preserves files by default).
 5. Confirm with the names added and their combined token estimate, e.g.
    "Added 2 optional helpers: Code review workflow, TDD workflow (~3k tokens)."
 

package/library/global/skills/haus-workflow/references/init.md

@@ -6,7 +6,7 @@ commands; they read plain language and approve.
 
 Do this in order:
 
-1. **Detect.** Run `haus setup-project --json`. Read the JSON yourself —
+1. **Detect.** Run `haus init --json --dry-run`. 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
@@ -47,9 +47,9 @@ Do this in order:
      `recommendation.json`, so repeated calls would drop the earlier includes.
    - **Project config** (entries in `recommended[]` with `install: false`, e.g.
      Haus ESLint / Prettier baselines): offer each as a plain choice ("Add the
-     Haus ESLint baseline"). On confirm, run `haus scaffold <id>`. `haus scaffold`
+     Haus ESLint baseline"). On confirm, run `haus configs <id>`. `haus configs`
      **preserves existing config files by default** and tells you when a file
-     already exists — only re-run with `haus scaffold <id> --force` if the user
+     already exists — only re-run with `haus configs <id> --force` if the user
      explicitly chooses to **replace** their current config.
 
    If neither list has anything, skip this step silently — don't ask an empty

package/library/global/skills/haus-workflow/references/new.md

@@ -0,0 +1,24 @@
+# project:new — create a new project from an allowed stack
+
+Drives `haus new` non-interactively. NEVER run bare `haus new` without flags —
+its interactive prompts don't work through the agent; collect answers with
+AskUserQuestion and pass everything as flags.
+
+1. **List stacks.** Run `haus new --list --json`. Present the stacks via
+   AskUserQuestion (one option per stack, id + title).
+2. **Collect inputs.** Ask for: project name (free text; lowercase letters, digits,
+   `. _ -`), GitHub org (default: WeAreHausTech; "personal" = omit --org),
+   visibility (private default / public), and whether to create the GitHub
+   repo at all (default yes; no → add `--no-github`).
+3. **Preview.** Run
+   `haus new <stack> <name> --json --yes --dry-run [--org <org>] [--public] [--no-github]`
+   and show the user the planned steps in plain language. Confirm before executing.
+4. **Execute.** Re-run the same command without `--dry-run`. Parse the JSON:
+   - `ok: true` → summarize: project path, repo URL, init result, and the
+     `installHint` (dependencies are NOT installed automatically).
+   - `ok: false` → report the failed step's `detail` verbatim — it contains the
+     exact resume commands (e.g. `gh repo create … && git push -u origin main`).
+     Do NOT retry destructively; the project directory is never auto-deleted.
+5. **Hand off.** Tell the user to `cd <name>` and run the install command from
+   `installHint` — the project is fully initialized (no separate `project:init`
+   needed).

package/package.json

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