bmad-method 6.10.1-next.47 → 6.10.1-next.49

package/README.md

@@ -1,8 +1,8 @@
 ![BMad Method](banner-bmad-method.png)
 
-**Turn an idea or change request into working software without giving up the thinking.**
+**Agile Ai Driven Development — turn an idea or change request into working software without giving up the thinking.**
 
-**Heard BMad means heavyweight process for every change? It doesn't.** Small changes go straight to build. Complex work gets the depth it needs.
+Ai Driven Development (AiDD) covers the whole effort, not only the code: what to build, how it holds together, and how it changes as you learn. BMad Method is the agile way to do it — decisions stay explicit, context carries forward, and the process sizes itself to the work. Small changes go straight to build. Complex work gets the depth it needs. The same method covers a weekend prototype and a system with years of history behind it.
 
 ![The BMad delivery loop: a vague notion starts at Clarify, a big clear idea at Plan, and a small change at Build and verify; Learn and adjust loops back to Plan](docs/images/bmad-delivery-loop.svg)
 
@@ -20,6 +20,8 @@ Open your project in your AI coding tool, invoke `bmad-build` with what you want
 
 **[Build your first project with BMad →](https://docs.bmad-method.org/tutorials/getting-started/)**
 
+**[Add BMad to an existing codebase →](https://docs.bmad-method.org/how-to/established-projects/)**
+
 BMad is free and open source, with no paywalled workflows or gated community. For prerelease builds, CI/CD, configuration overrides, and non-interactive setup, see the [installation guide](https://docs.bmad-method.org/how-to/install-bmad/).
 
 ## Why BMad?
@@ -27,6 +29,7 @@ BMad is free and open source, with no paywalled workflows or gated community. Fo
 Coding assistants are effective at implementation, but they often turn unstated assumptions into code. BMad keeps you in control while its agents and workflows make the important decisions explicit and preserve them as context for the work that follows.
 
 - **Right-sized process** — Go directly to implementation for clear changes or add deeper planning for larger initiatives.
+- **New or existing code** — Start from nothing, or establish verified context on a codebase you inherited and work from what is actually there.
 - **Durable context** — Carry product and technical decisions forward instead of re-explaining them in every chat.
 - **Specialized perspectives** — Bring in product, architecture, UX, development, and testing expertise when it helps.
 - **Guided collaboration** — Use structured workflows and multiple-agent discussions without handing over judgment.
@@ -40,11 +43,12 @@ Install the core method or add official modules for specialized work.
 
 | Module | Purpose |
 | --- | --- |
-| **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)** | Plan and deliver software with scale-adaptive workflows |
-| **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)** | Create custom BMad agents and workflows |
-| **[Test Architect (TEA)](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)** | Design risk-based test strategy and automation |
-| **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)** | Build games with Unity, Unreal, or Godot workflows |
-| **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Run innovation, brainstorming, and design-thinking workflows |
+| **[BMad Method](https://github.com/bmad-code-org/BMAD-METHOD)** | Plan and deliver software, from new prototypes to established codebases |
+| **[BMad Builder](https://github.com/bmad-code-org/bmad-builder)** | Skill, workflow, and agent builder |
+| **[BMad Creative Intelligence Suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Creative thinking partners for innovation, design thinking, and storytelling |
+| **[BMad Test Architect](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)** | Enterprise testing add-on for BMad Method |
+| **[BMad Loop](https://github.com/bmad-code-org/bmad-loop)** | Builds, verifies, and retros a whole epic unattended |
+| **[BMad Game Dev Studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)** | Ideate, design, and build games in any framework, including Unity, Unreal, Godot, and Phaser |
 
 ## Plan on the Web
 

package/README_CN.md

@@ -5,7 +5,7 @@
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen)](https://nodejs.org)
 [![Discord](https://img.shields.io/badge/Discord-Join%20Community-7289da?logo=discord&logoColor=white)](https://discord.gg/gk8jAdXWmj)
 
-**筑梦架构（Build More Architect Dreams）** —— 简称 “BMAD 方法”，面向 BMad 模块生态的 AI 驱动敏捷开发方法。它会随项目复杂度调整工作深度，从日常 bug 修复到企业级系统建设都能适配。
+**Agile Ai Driven Development（敏捷 AI 驱动开发）** —— Ai Driven Development（AiDD）关注的不只是代码，还包括做什么、如何组织，以及在认知变化时如何调整。BMad Method 是实践 AiDD 的敏捷方式：决策保持显式，上下文持续传递，流程随工作量自动调整。同一套方法既适用于周末原型，也适用于有多年历史的系统。
 
 **100% 免费且开源。** 没有付费墙，没有封闭内容，也没有封闭 Discord。我们希望每个人都能平等获得高质量的人机协作开发方法。
 
@@ -56,19 +56,21 @@ npx bmad-method install --directory /path/to/project --modules bmm --tools claud
 
 BMad 可通过官方模块扩展到不同专业场景。你可以在安装时选择，也可以后续随时补装。
 
-| 模块                                                                                                                | 用途                           |
-| ----------------------------------------------------------------------------------------------------------------- | ---------------------------- |
-| **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)**                                             | 核心框架，内含 34+ 工作流         |
-| **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)**                                           | 创建自定义 BMad 智能体与工作流     |
-| **[Test Architect (TEA)](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)**             | 基于风险的测试策略与自动化         |
-| **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                        | 游戏开发工作流（Unity/Unreal/Godot） |
-| **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | 创新、头脑风暴、设计思维           |
+| 模块                                                                                                             | 用途                                                                    |
+| ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
+| **[BMad Method](https://github.com/bmad-code-org/BMAD-METHOD)**                                                  | 规划并交付软件，覆盖全新原型到成熟代码库                                |
+| **[BMad Builder](https://github.com/bmad-code-org/bmad-builder)**                                                | 技能、工作流与智能体构建器                                              |
+| **[BMad Creative Intelligence Suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | 创意思考伙伴：创新、设计思维与叙事                                      |
+| **[BMad Test Architect](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)**             | 面向 BMad Method 的企业级测试扩展模块                                   |
+| **[BMad Loop](https://github.com/bmad-code-org/bmad-loop)**                                                      | 无人值守地构建、验证并复盘整个 Epic                                     |
+| **[BMad Game Dev Studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                         | 构思、设计并开发游戏，支持任意框架，包括 Unity、Unreal、Godot 与 Phaser |
 
 ## 文档
 
 [BMad 方法文档站点](https://docs.bmad-method.org/zh-cn/) — 教程、指南、概念和参考
 
 **快速链接：**
+
 - [入门教程](https://docs.bmad-method.org/zh-cn/tutorials/getting-started/)
 - [从旧版本升级](https://docs.bmad-method.org/zh-cn/how-to/upgrade-to-v6/)
 - [测试架构师文档（英文）](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/)

package/README_VN.md

@@ -9,7 +9,7 @@
 
 [English](README.md) | [简体中文](README_CN.md) | Tiếng Việt
 
-**Build More Architect Dreams** - một mô-đun khung phát triển hướng AI trong hệ sinh thái BMad, có khả năng thích ứng theo quy mô từ sửa lỗi nhỏ đến các hệ thống doanh nghiệp.
+**Agile Ai Driven Development (Phát triển hướng AI theo lối agile)** - Ai Driven Development (AiDD) bao trùm toàn bộ công việc chứ không chỉ phần mã: xây dựng cái gì, các phần gắn kết ra sao, và thay đổi thế nào khi bạn hiểu thêm. BMad Method là cách làm AiDD theo lối agile: quyết định luôn tường minh, ngữ cảnh được giữ lại xuyên suốt, và quy trình tự co giãn theo khối lượng công việc. Cùng một phương pháp dùng được cho nguyên mẫu cuối tuần lẫn hệ thống đã có nhiều năm lịch sử.
 
 **100% miễn phí và mã nguồn mở.** Không có tường phí. Không có nội dung bị khóa. Không có Discord giới hạn quyền truy cập. Chúng tôi tin vào việc trao quyền cho mọi người, không chỉ cho những ai có thể trả tiền để vào một cộng đồng hay khóa học khép kín.
 
@@ -60,19 +60,21 @@ npx bmad-method install --directory /path/to/project --modules bmm --tools claud
 
 BMad Method có thể được mở rộng bằng các mô-đun chính thức cho những miền chuyên biệt. Chúng có sẵn trong lúc cài đặt hoặc bất kỳ lúc nào sau đó.
 
-| Module                                                                                                            | Mục đích                                           |
-| ----------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
-| **[BMad Method (BMM)](https://github.com/bmad-code-org/BMAD-METHOD)**                                             | Khung lõi với hơn 34 quy trình                     |
-| **[BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)**                                           | Tạo agent và quy trình BMad tùy chỉnh             |
-| **[Test Architect (TEA)](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)**             | Chiến lược kiểm thử và tự động hóa dựa trên rủi ro |
-| **[Game Dev Studio (BMGD)](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                        | Quy trình phát triển game (Unity, Unreal, Godot)   |
-| **[Creative Intelligence Suite (CIS)](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Đổi mới, động não ý tưởng, tư duy thiết kế         |
+| Module                                                                                                           | Mục đích                                                                                        |
+| ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| **[BMad Method](https://github.com/bmad-code-org/BMAD-METHOD)**                                                  | Lập kế hoạch và bàn giao phần mềm, từ nguyên mẫu mới đến codebase lâu năm                       |
+| **[BMad Builder](https://github.com/bmad-code-org/bmad-builder)**                                                | Trình tạo skill, quy trình và agent                                                             |
+| **[BMad Creative Intelligence Suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite)** | Đối tác tư duy sáng tạo cho đổi mới, tư duy thiết kế và kể chuyện                               |
+| **[BMad Test Architect](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise)**             | Mô-đun kiểm thử doanh nghiệp bổ trợ cho BMad Method                                             |
+| **[BMad Loop](https://github.com/bmad-code-org/bmad-loop)**                                                      | Tự động xây dựng, kiểm chứng và tổng kết cả một Epic                                            |
+| **[BMad Game Dev Studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio)**                         | Lên ý tưởng, thiết kế và phát triển game trên mọi framework, gồm Unity, Unreal, Godot và Phaser |
 
 ## Tài liệu
 
 [Trang tài liệu BMad Method](https://docs.bmad-method.org/vi-vn/) - bài hướng dẫn, hướng dẫn tác vụ, giải thích khái niệm và tài liệu tham chiếu
 
 **Liên kết nhanh:**
+
 - [Hướng dẫn bắt đầu](https://docs.bmad-method.org/vi-vn/tutorials/getting-started/)
 - [Nâng cấp từ các phiên bản trước](https://docs.bmad-method.org/vi-vn/how-to/upgrade-to-v6/)
 - [Tài liệu Test Architect](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/)

package/bmad-modules.yaml

@@ -34,6 +34,39 @@
 # install to the new code and removes the stale `_bmad/<alias>/` directory.
 
 modules:
+  bmad-builder:
+    url: https://github.com/bmad-code-org/bmad-builder
+    module-definition: skills/module.yaml
+    code: bmb
+    name: "BMad Builder"
+    description: "Skill, workflow, and agent builder"
+    defaultSelected: false
+    type: bmad-org
+    npmPackage: bmad-builder
+    default_channel: stable
+
+  bmad-creative-intelligence-suite:
+    url: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite
+    module-definition: src/module.yaml
+    code: cis
+    name: "BMad Creative Intelligence Suite"
+    description: "Creative thinking partners"
+    defaultSelected: false
+    type: bmad-org
+    npmPackage: bmad-creative-intelligence-suite
+    default_channel: stable
+
+  bmad-method-test-architecture-enterprise:
+    url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise
+    module-definition: src/module.yaml
+    code: tea
+    name: "BMad Test Architect"
+    description: "Enterprise testing BMM add-on"
+    defaultSelected: false
+    type: bmad-org
+    npmPackage: bmad-method-test-architecture-enterprise
+    default_channel: stable
+
   bmad-loop:
     url: https://github.com/bmad-code-org/bmad-loop
     module-definition: src/bmad_loop/data/skills/bmad-loop-setup/assets/module.yaml
@@ -43,7 +76,7 @@ modules:
     # installs migrating forward instead of being orphaned.
     aliases: [bauto]
     name: "BMad Loop"
-    description: "Deterministic, Python-based unattended dev loop with adversarial review"
+    description: "Builds, verifies, and retros a whole epic unattended"
     defaultSelected: false
     type: bmad-org
     default_channel: stable
@@ -59,27 +92,18 @@ modules:
       It installs the bmad-loop orchestrator tool and wires up the per-project
       hooks and policy. The automation skills don't run until setup completes.
 
-  bmad-method-test-architecture-enterprise:
-    url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise
+  bmad-game-dev-studio:
+    url: https://github.com/bmad-code-org/bmad-module-game-dev-studio.git
     module-definition: src/module.yaml
-    code: tea
-    name: "BMad Test Architect"
-    description: "Quality strategy, test automation, and release gates for enterprise teams"
+    code: gds
+    name: "BMad Game Dev Studio"
+    description: "Ideate, design, and build games"
     defaultSelected: false
     type: bmad-org
-    npmPackage: bmad-method-test-architecture-enterprise
+    npmPackage: bmad-game-dev-studio
     default_channel: stable
 
-  bmad-builder:
-    url: https://github.com/bmad-code-org/bmad-builder
-    module-definition: skills/module.yaml
-    code: bmb
-    name: "BMad Builder"
-    description: "Build AI agents, workflows, and modules from a conversation"
-    defaultSelected: false
-    type: bmad-org
-    npmPackage: bmad-builder
-    default_channel: stable
+  # --- Deprecated: hidden from the picker unless already installed ---
 
   bmad-automator:
     url: https://github.com/bmad-code-org/bmad-automator
@@ -94,28 +118,6 @@ modules:
     deprecated: true
     deprecation-message: "BMad Automator has been deprecated and is replaced by BMad Loop (bmad-loop). Install BMad Loop instead."
 
-  bmad-creative-intelligence-suite:
-    url: https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite
-    module-definition: src/module.yaml
-    code: cis
-    name: "BMad Creative Intelligence Suite"
-    description: "Brainstorming, ideation, storytelling, design thinking, and problem-solving"
-    defaultSelected: false
-    type: bmad-org
-    npmPackage: bmad-creative-intelligence-suite
-    default_channel: stable
-
-  bmad-game-dev-studio:
-    url: https://github.com/bmad-code-org/bmad-module-game-dev-studio.git
-    module-definition: src/module.yaml
-    code: gds
-    name: "BMad Game Dev Studio"
-    description: "Game design and development for Unity, Unreal, Godot, and Phaser."
-    defaultSelected: false
-    type: bmad-org
-    npmPackage: bmad-game-dev-studio
-    default_channel: stable
-
   bmad-method-wds-expansion:
     url: https://github.com/bmad-code-org/bmad-method-wds-expansion
     module-definition: src/module.yaml
@@ -127,3 +129,5 @@ modules:
     type: bmad-org
     npmPackage: bmad-wds
     default_channel: stable
+    deprecated: true
+    deprecation-message: "Whiteport Design Studio is no longer receiving updates. Its capabilities are being folded into BMad Method (bmm) as enhanced UX features. Your existing install is kept as-is."

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.10.1-next.47",
+  "version": "6.10.1-next.49",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/bmm-skills/module.yaml

@@ -1,6 +1,6 @@
 code: bmm
 name: "BMad Method"
-description: "Full-lifecycle AI agile development: analysis, planning, architecture, implementation"
+description: "Agile Ai Driven Development"
 default_selected: true # This module will be selected by default for new installations
 
 # Variables from Core Config inserted:

package/src/bmm-skills/ship/bmad-build/review-prompts/verification-gap.md

@@ -54,6 +54,8 @@ Find and read the relevant test. Ask whether the Demonstration would make an ass
 
 A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
 
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
 Common patterns:
 
 - **Caller-path gap** — helper test covers the branch, but caller values skip it.
@@ -67,6 +69,8 @@ Common patterns:
 
 Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
 
+Explain why the test misses the bug using what the test sets up and checks.
+
 Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
 
 Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.

package/src/bmm-skills/ship/bmad-build-auto/review-prompts/verification-gap.md

@@ -54,6 +54,8 @@ Find and read the relevant test. Ask whether the Demonstration would make an ass
 
 A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
 
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
 Common patterns:
 
 - **Caller-path gap** — helper test covers the branch, but caller values skip it.
@@ -67,6 +69,8 @@ Common patterns:
 
 Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
 
+Explain why the test misses the bug using what the test sets up and checks.
+
 Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
 
 Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.

package/src/bmm-skills/ship/bmad-code-review/review-prompts/verification-gap.md

@@ -54,6 +54,8 @@ Find and read the relevant test. Ask whether the Demonstration would make an ass
 
 A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; source-text assertions that match a file's wording instead of running it; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
 
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
 Common patterns:
 
 - **Caller-path gap** — helper test covers the branch, but caller values skip it.
@@ -67,6 +69,8 @@ Common patterns:
 
 Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
 
+Explain why the test misses the bug using what the test sets up and checks.
+
 Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
 
 Report genuine problems you noticed while tracing verification, even if they are not verification gaps. Put them under `Other findings` in the output. This permits reporting what you already reached, not extra hunting.

package/src/core-skills/bmad-review/references/lens-verification-gap.md

@@ -56,6 +56,8 @@ Find and read the relevant test. Ask whether the Demonstration would make an ass
 
 A test counts only if it runs normally and an assertion observes the changed output, branch, or contract. These do not count: no execution; success/no-throw/snapshot-only checks; mock/log-call checks; human-only checks; tests that mock away the integration; e2e tests that pass through without checking the changed output; stale assertions or fixtures.
 
+For example, `expect(x ?? DEFAULT).toBe(DEFAULT)` passes when `x` is missing.
+
 Common patterns:
 
 - **Caller-path gap** — helper test covers the branch, but caller values skip it.
@@ -69,6 +71,8 @@ Common patterns:
 
 Before writing a finding, re-open the specific tests or search results the finding relies on. Verify the Demonstration would not make any test you checked fail, or that the absence claim is backed by the symbol/import-reference search. Do not claim more than you verified; drop any finding you cannot ground.
 
+Explain why the test misses the bug using what the test sets up and checks.
+
 Do not report: compiler/type-checker-enforced cases; behavior already verified by an integration, contract, or e2e test; implementation-detail or mock-only tests; low coverage or a missing test file by itself; legacy untested code the change did not affect.
 
 Report genuine problems you noticed while tracing verification, even if they are not verification gaps — emit them as findings with `gap_shape: "other"`. This permits reporting what you already reached, not extra hunting.

package/tools/installer/cli-utils.js

@@ -29,9 +29,13 @@ const CLIUtils = {
 
     const logoLines = termWidth >= 95 ? logoWide : logoNarrow;
     const logo = logoLines.map((line) => color.blue(line)).join('\n');
-    const tagline = color.white('    Build More, Architect Dreams\n    © BMad Code');
+    // The wordmark supplies "BMad Method", so the lines below read as its
+    // tagline, then its positioning, then the company credit.
+    const tagline = color.white('    Agile Ai Driven Development');
+    const slogan = color.dim('    the agile way to do AiDD');
+    const credit = color.dim('    Build More, Architect Dreams · © BMad Code');
 
-    await prompts.box(`${logo}\n${tagline}`, '', {
+    await prompts.box(`${logo}\n${tagline}\n${slogan}\n${credit}`, '', {
       contentAlign: 'center',
       rounded: true,
       formatBorder: color.blue,

package/tools/installer/prompts.js

@@ -578,10 +578,6 @@ async function autocomplete(options) {
   return result;
 }
 
-function hasPathSeparator(value) {
-  return value.endsWith('/') || value.endsWith('\\');
-}
-
 function expandHome(input) {
   if (!input) return input;
   if (input === '~') return os.homedir();
@@ -591,91 +587,54 @@ function expandHome(input) {
   return input;
 }
 
-function toDirectoryOption(value, label = value, synthetic = false) {
-  return { value, label, synthetic };
-}
-
-function isExistingDirectory(value) {
-  try {
-    return fs.existsSync(value) && fs.statSync(value).isDirectory();
-  } catch {
-    return false;
-  }
-}
-
-function listDirectoryOptions(input, options) {
+/**
+ * Resolve raw prompt input to an absolute directory path.
+ * Mirrors UI.expandUserPath so what the prompt returns matches what the
+ * installer later resolves.
+ */
+function resolveDirectoryInput(input, options = {}) {
   const cwd = options.cwd || process.cwd();
-  const rawInput = input.trim();
-  const expandedInput = expandHome(rawInput);
-  const trailingSep = hasPathSeparator(rawInput) || hasPathSeparator(expandedInput);
-  const resolvedInput = expandedInput ? path.resolve(cwd, expandedInput) : cwd;
-  const browseDir = expandedInput && !trailingSep && !isExistingDirectory(resolvedInput) ? path.dirname(resolvedInput) : resolvedInput;
-  const prefix = expandedInput && browseDir !== resolvedInput ? path.basename(resolvedInput).toLowerCase() : '';
-  const results = [];
-
-  if (!trailingSep && isExistingDirectory(resolvedInput)) {
-    results.push(toDirectoryOption(resolvedInput, `. (use this directory)`));
-  }
-
-  if (isExistingDirectory(browseDir)) {
-    try {
-      for (const entry of fs.readdirSync(browseDir, { withFileTypes: true })) {
-        if (!entry.isDirectory()) continue;
-        if (prefix && !entry.name.toLowerCase().startsWith(prefix)) continue;
-        const fullPath = path.join(browseDir, entry.name);
-        if (!results.some((option) => option.value === fullPath)) {
-          results.push(toDirectoryOption(fullPath));
-        }
-      }
-    } catch {
-      // Skip unreadable directories; validation still reports path issues.
-    }
-  }
-
-  const validation = options.validate?.(rawInput);
-  const hasMatchingOption = results.some((option) => option.value === resolvedInput);
-  if (expandedInput && !validation && !hasMatchingOption) {
-    results.unshift(toDirectoryOption(resolvedInput, `Create/use: ${resolvedInput}`, true));
-  }
-
-  return results;
+  const rawInput = typeof input === 'string' ? input.trim() : '';
+  // An empty line means "use the default", which is resolved the same way as
+  // typed text so a `~/…` or relative default still returns an absolute path.
+  const effective = rawInput || (options.default || '').trim();
+  if (!effective) return cwd;
+  return path.resolve(cwd, expandHome(effective));
 }
 
 /**
- * Directory prompt with autocomplete candidates and create-directory support.
- * Uses @clack/core directly so typed paths that do not exist yet can still be
- * submitted when validation allows creating them.
+ * Directory prompt.
+ *
+ * A plain text entry: what is on the input line is what gets submitted,
+ * resolved to an absolute path.
+ *
+ * The line is pre-filled with the default (the current working directory,
+ * which is where installs usually run from) as real editable text rather than
+ * a placeholder, so it can be edited down or extended instead of retyped.
+ * Clearing it and pressing Enter still accepts the default.
+ *
  * @param {Object} options - Prompt options
  * @param {string} options.message - Prompt message
- * @param {string} [options.default] - Default directory
- * @param {string} [options.placeholder] - Placeholder text
+ * @param {string} [options.default] - Default directory, pre-filled on the input line
+ * @param {string} [options.placeholder] - Placeholder shown only if the line is cleared
  * @param {Function} [options.validate] - Sync validation function
- * @returns {Promise<string>} Selected or typed directory path
+ * @param {Object} [options.input] - Input stream (defaults to process.stdin; tests inject)
+ * @param {Object} [options.output] - Output stream (defaults to process.stdout; tests inject)
+ * @returns {Promise<string>} Resolved absolute directory path
  */
 async function directory(options) {
   const core = await getClackCore();
   const color = await getPicocolors();
-  const tabCompletion = {
-    prefix: '',
-    index: -1,
-    options: [],
-    lastValue: '',
-  };
 
-  let prompt;
-  prompt = new core.AutocompletePrompt({
+  const prompt = new core.TextPrompt({
+    ...(options.input ? { input: options.input } : {}),
+    ...(options.output ? { output: options.output } : {}),
     initialValue: options.default,
-    options: () => listDirectoryOptions(prompt?.userInput || '', options),
-    filter: () => true,
-    validate: (value) => options.validate?.(value ?? prompt.userInput),
+    defaultValue: options.default,
+    validate: options.validate,
     render() {
-      const title = `${color.gray('◆')}  ${options.message}`;
       const bar = color.gray('│');
-      const barEnd = color.gray('└');
       const userInput = this.userInput;
-      const placeholder = options.placeholder || options.default;
-      const inputDisplay = userInput ? this.userInputWithCursor : `${color.inverse(color.hidden('_'))}${color.dim(placeholder || '')}`;
-      const errorLine = this.state === 'error' ? [`${color.yellow('│')}  ${color.yellow(this.error)}`] : [];
 
       switch (this.state) {
         case 'submit': {
@@ -685,42 +644,20 @@ async function directory(options) {
           return `${color.gray('◇')}  ${options.message}\n${bar}  ${color.strikethrough(color.dim(userInput || ''))}`;
         }
         default: {
-          return [title, `${bar}  ${inputDisplay}`, ...errorLine, barEnd].join('\n');
+          const placeholder = options.placeholder || options.default;
+          const inputDisplay = userInput ? this.userInputWithCursor : `${color.inverse(color.hidden('_'))}${color.dim(placeholder || '')}`;
+          const lines = [`${color.gray('◆')}  ${options.message}`, `${bar}  ${inputDisplay}`];
+          if (this.state === 'error') lines.push(`${color.yellow('│')}  ${color.yellow(this.error)}`);
+          lines.push(color.gray('└'));
+          return lines.join('\n');
         }
       }
     },
   });
 
-  const hasSetUserInput = typeof prompt._setUserInput === 'function';
-  const hasClearUserInput = typeof prompt._clearUserInput === 'function';
-
-  prompt.on('key', (_, key) => {
-    if (key?.name !== 'tab') return;
-    if (!hasSetUserInput) return; // @clack/core API surface changed — skip Tab silently.
-    const currentInput = prompt.userInput;
-    const isContinuingCycle = tabCompletion.lastValue && currentInput === tabCompletion.lastValue;
-    const completionOptions = isContinuingCycle ? tabCompletion.options : prompt.filteredOptions.filter((option) => !option.synthetic);
-    if (completionOptions.length === 0) return;
-
-    if (isContinuingCycle) {
-      tabCompletion.index = (tabCompletion.index + 1) % completionOptions.length;
-    } else {
-      tabCompletion.prefix = currentInput;
-      tabCompletion.options = completionOptions;
-      tabCompletion.index = 0;
-    }
-
-    const focusedOption = completionOptions[tabCompletion.index];
-    if (!focusedOption) return;
-    const completedValue = focusedOption.value;
-    tabCompletion.lastValue = completedValue;
-    if (hasClearUserInput) prompt._clearUserInput();
-    prompt._setUserInput(completedValue, true);
-  });
-
   const result = await prompt.prompt();
   await handleCancel(result);
-  return result;
+  return resolveDirectoryInput(result, options);
 }
 
 /**
@@ -843,6 +780,8 @@ module.exports = {
   autocompleteMultiselect,
   autocomplete,
   directory,
+  // Exported for tests
+  resolveDirectoryInput,
   confirm,
   text,
   password,

package/tools/installer/ui.js

@@ -110,6 +110,44 @@ async function getModuleVersion(moduleCode, { repoUrl = null, registryDefault =
  * UI utilities for the installer
  */
 class UI {
+  /**
+   * Warn once for each selected module the registry marks deprecated.
+   *
+   * A deprecated module is never dropped from the selection — an existing
+   * install keeps working and keeps being updated on request. The warning is
+   * the only behavior change, and it is what tells CLI users (`--modules`,
+   * `--yes`) what the interactive picker shows as an option hint.
+   *
+   * @param {Array<string>} selectedModules - Module codes about to be installed
+   * @returns {Promise<Array<string>>} The deprecated codes that were warned about
+   */
+  async _warnDeprecatedModules(selectedModules = []) {
+    const externalManager = new ExternalModuleManager();
+    let registryModules;
+    try {
+      registryModules = await externalManager.listAvailable();
+    } catch {
+      return []; // Registry unreadable — never block an install over a notice.
+    }
+
+    const deprecatedByCode = new Map();
+    for (const mod of registryModules) {
+      if (!mod.deprecated) continue;
+      deprecatedByCode.set(mod.code, mod);
+      for (const alias of mod.aliases) deprecatedByCode.set(alias, mod);
+    }
+
+    const warned = [];
+    for (const code of selectedModules) {
+      const mod = deprecatedByCode.get(code);
+      if (!mod || warned.includes(mod.code)) continue;
+      warned.push(mod.code);
+      const detail = mod.deprecationMessage || 'It is no longer receiving updates.';
+      await prompts.log.warn(`${mod.name} (${mod.code}) is deprecated. ${detail}`);
+    }
+    return warned;
+  }
+
   async _retainUnavailableInstalledModules(selectedModules, installedModuleIds, bmadDir, options = {}) {
     const { OfficialModules } = require('./modules/official-modules');
     const officialCodes = new Set(['core']);
@@ -275,6 +313,9 @@ class UI {
 
       // Handle quick update separately
       if (actionType === 'quick-update') {
+        // Quick update never shows the module picker, so this is the only
+        // place an existing install of a deprecated module hears about it.
+        await this._warnDeprecatedModules(existingInstall.moduleIds || []);
         return {
           actionType: 'quick-update',
           directory: confirmedDirectory,
@@ -339,6 +380,11 @@ class UI {
           );
         }
 
+        // Surface deprecation notices for whatever ended up selected. The
+        // interactive picker only hints at them in the option list, and the
+        // --modules / --yes paths never see that list at all.
+        await this._warnDeprecatedModules(selectedModules);
+
         // For existing installs, resolve per-module update decisions BEFORE
         // we clone anything. Reads the existing manifest's recorded channel
         // per module and prompts the user on available upgrades (patch/minor
@@ -424,6 +470,8 @@ class UI {
       selectedModules.unshift('core');
     }
 
+    await this._warnDeprecatedModules(selectedModules);
+
     // Interactive channel gate: "Ready to install (all stable)? [Y/n]"
     // Only shown for fresh installs with no channel flags and an external module
     // selected. Skipped for prerelease launches because channelOptions.global
@@ -901,7 +949,7 @@ class UI {
    * @param {Set} installedModuleIds - Currently installed module IDs
    * @param {Map<string, string>} installedModuleVersions - Installed module versions from the local manifest
    * @param {Object|null} channelOptions - Parsed installer channel options
-   * @returns {Array} Selected module codes (excluding core)
+   * @returns {Array} Selected module codes, always including core
    */
   async selectAllModules(installedModuleIds = new Set(), installedModuleVersions = new Map(), channelOptions = null) {
     // Phase 1: Official modules
@@ -942,7 +990,6 @@ class UI {
 
     const allOptions = [];
     const initialValues = [];
-    const lockedValues = ['core'];
 
     const buildModuleEntry = async (code, name, description, isDefault, repoUrl = null, registryDefault = null) => {
       const isInstalled = installedModuleIds.has(code);
@@ -959,11 +1006,15 @@ class UI {
       };
     };
 
-    // Add built-in modules first (always available regardless of network)
+    // Add built-in modules first (always available regardless of network).
+    // core is not offered as a row: it is a dependency of every module, always
+    // installed, and was only ever rendered as a locked always-on checkbox.
+    // It is still added back to the result below.
     const builtInCodes = new Set();
     for (const mod of builtInModules) {
       const code = mod.id;
       builtInCodes.add(code);
+      if (code === 'core') continue;
       const entry = await buildModuleEntry(code, mod.name, mod.description, mod.defaultSelected);
       allOptions.push({ label: entry.label, value: entry.value, hint: entry.hint });
       if (entry.selected) {
@@ -1018,22 +1069,24 @@ class UI {
       message: 'Select official modules to install:',
       options: allOptions,
       initialValues: initialValues.length > 0 ? initialValues : undefined,
-      lockedValues,
-      required: true,
+      // Not required: core is installed either way, so an empty selection is a
+      // legitimate "core only" install rather than a mistake to block on.
+      required: false,
       maxItems: allOptions.length,
     });
 
-    const result = selected ? [...selected] : [];
+    const chosen = selected ? [...selected] : [];
 
-    if (result.length > 0) {
-      const moduleLines = result.map((moduleId) => {
+    if (chosen.length > 0) {
+      const moduleLines = chosen.map((moduleId) => {
         const opt = allOptions.find((o) => o.value === moduleId);
         return `  \u2022 ${opt?.label || moduleId}`;
       });
       await prompts.log.message('Selected official modules:\n' + moduleLines.join('\n'));
     }
 
-    return result;
+    // core is never shown but always installed.
+    return chosen.includes('core') ? chosen : ['core', ...chosen];
   }
 
   /**