create-claude-workspace 1.1.149 → 1.1.151

package/dist/scripts/lib/tui.mjs

@@ -175,8 +175,7 @@ export class TUI {
             line += ` | ${trunc(s.taskName, 20)}`;
         if (s.paused)
             line += ' | PAUSED';
-        if (s.inputBuf)
-            line += `  > ${s.inputBuf}`;
+        line += s.inputBuf ? `  › ${s.inputBuf}` : '  › type to send input';
         // Truncate to terminal width
         const cols = process.stdout.columns || 120;
         if (line.length > cols)
@@ -201,8 +200,12 @@ export class TUI {
             line += ` | ${ANSI_COLORS.cyan}${trunc(s.taskName, 20)}${RESET}\x1b[7m`;
         if (s.paused)
             line += ` | ${ANSI_COLORS.yellow}⏸ PAUSED${RESET}\x1b[7m`;
-        if (s.inputBuf)
-            line += `  › ${s.inputBuf}`;
+        if (s.inputBuf) {
+            line += `  ${RESET}${ANSI_COLORS.white}› ${s.inputBuf}${RESET}`;
+        }
+        else {
+            line += `  ${RESET}${ANSI_COLORS.gray}› type to send input${RESET}`;
+        }
         line += ` ${RESET}`;
         return line;
     }

package/dist/template/.claude/agents/orchestrator.md

@@ -369,6 +369,19 @@ If `PLAN.md` exists in the project root, check whether it changed since the last
 - After merge (STEP 10), EXIT. Do NOT update MEMORY.md after merge — it was already committed in STEP 9 and arrived on main via merge. Do NOT ask whether to continue, do NOT wait for confirmation, do NOT start another task. Do NOT create any commits after merge.
 - Track complexity in MEMORY.md `Complexity This Session` for informational purposes only (S=1, M=2, L=4).
 
+### 14. User input during autonomous operation
+The user can send messages mid-session via the interactive TUI. When you receive a user message during the workflow:
+
+- **Read and understand the request** — determine what the user wants.
+- **Task/feature request** ("add X", "build Y", "I want Z"): delegate to `technical-planner` to create properly structured tasks in TODO.md with correct phase, dependencies, complexity, and Type field. The planner decides priority placement — urgent requests go to the top of the current phase, normal requests go to the appropriate phase. Then **continue your current task** — do NOT drop what you're doing. The new task will be picked up in a future invocation.
+- **Change to current task** ("use X instead", "also add Y here", "don't forget Z"): incorporate the feedback into your current implementation. If you're past STEP 3 (IMPLEMENT), adjust the code. If you're in STEP 2 (PLAN), adjust the plan.
+- **Bug report / fix request** ("X is broken", "fix Y"): if it's related to the current task, fix it now. If it's a separate issue, create a hotfix task at the top of the current phase in TODO.md (mark as `Complexity: S`, `Type:` based on affected files).
+- **Stop / abort** ("stop", "cancel", "skip this"): mark the current task as `[~]` SKIPPED in TODO.md with reason "user request", clean up worktree, commit tracking on main, EXIT.
+- **Question / status** ("what are you doing?", "how far along?"): respond briefly with current step and task, then continue working.
+- **Reprioritization** ("do X first", "skip phase 2", "focus on Y"): update TODO.md accordingly (reorder, mark `[~]` SKIPPED with reason). If the current task should be dropped, treat as stop/abort above.
+
+**Do NOT pause or ask for confirmation** — process the input and continue. The user is monitoring asynchronously; they don't expect a back-and-forth conversation.
+
 ## Task Type Detection
 
 To determine if a task is frontend, backend, or fullstack, use this heuristic:

package/dist/template/.claude/agents/project-initializer.md

@@ -43,7 +43,7 @@ After the conversation, scan what already exists. Do NOT create or scaffold anyt
   - `react` or `next` → React
   - `vue` or `nuxt` → Vue
   - `svelte` or `@sveltejs/kit` → Svelte
-  - None of the above → no frontend / backend-only / TS library
+  - None of the above → no frontend detected yet (for new projects, the framework will be chosen in Step 4b)
   - Store the detected framework for Step 4 (profile selection)
 - List `apps/` and `libs/` structure if they exist
 - Check for existing plan/design/UX files (TODO.md, PLAN.md, PRODUCT.md, UX.md)
@@ -182,9 +182,13 @@ Create a **minimal** CLAUDE.md in the project root by filling what is KNOWN from
 - Keep: CLI-First Principle, Code Quality & Linting, and general coding conventions — these apply to all project types
 - The result should be a working CLAUDE.md that will be EXPANDED by architect agents as they make technical decisions
 
-**4b. Copy frontend profile:**
+**4b. Choose and copy frontend profile:**
 
-If a frontend framework was detected (or is expected for a new project):
+**For new projects with a UI (no framework detected yet):** Ask the user which frontend framework they prefer: Angular, React, Vue, or Svelte. If they have no preference, default to React. **NEVER use plain HTML/CSS/JS** — all frontend development requires one of the four supported frameworks (there are no agents or profiles for vanilla web development).
+
+**For existing projects:** Use the framework detected in Step 3.
+
+Once the framework is determined:
 1. Check `.claude/profiles/` for the matching profile file:
    - Angular → `.claude/profiles/angular.md`
    - React → `.claude/profiles/react.md`
@@ -193,7 +197,7 @@ If a frontend framework was detected (or is expected for a new project):
 2. Copy the profile to `.claude/profiles/frontend.md` in the project
 3. If the profile file doesn't exist in the kit (not yet created), warn: "No profile found for [framework]. The ui-engineer, test-engineer, and senior-code-reviewer agents will rely on their native knowledge of [framework]. Consider creating `.claude/profiles/frontend.md` with project-specific conventions."
 
-If no frontend framework is detected (backend-only / TS library), skip this step.
+If the project has no UI (backend-only / TS library), skip this step.
 
 ### Step 5: Product Planning — DELEGATE to `product-owner` agent
 

package/dist/template/.claude/agents/technical-planner.md

@@ -31,7 +31,7 @@ Read these files (all mandatory if they exist):
 ### 2. Determine Tech Stack (for new/empty projects)
 
 If the codebase has no `nx.json` or `package.json` (brand new project), YOU must decide the tech stack based on PRODUCT.md features:
-- **Does it need a UI?** → Choose frontend framework based on project needs. Check if `.claude/profiles/` has a matching profile. If the user mentioned a preference in the discovery conversation, use that.
+- **Does it need a UI?** → MUST choose one of the supported frontend frameworks: **Angular, React, Vue, or Svelte**. NEVER use plain HTML/CSS/JS — there is no agent or profile for vanilla web development. Check `.claude/profiles/` for available profiles. If the user mentioned a preference in the discovery conversation, use that. If no preference, default to React (widest ecosystem).
 - **Does it need a backend?** → Default: Hono on Cloudflare Workers (production) + Node.js (local dev). Backend code must be platform-agnostic — no Node-specific or CF-specific APIs in business/domain layers.
 - **Does it need a database?** → Default: D1 (Cloudflare production) + SQLite/better-sqlite3 (local dev). Both behind repository interfaces.
 - **Package manager** → Default to `npm` unless PRODUCT.md or user context suggests otherwise.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-claude-workspace",
-  "version": "1.1.149",
+  "version": "1.1.151",
   "author": "",
   "repository": {
     "type": "git",