@zeyue0329/xiaoma-cli 1.7.0 → 1.8.0

package/src/xmc/workflows/4-implementation/xiaoma-create-story/workflow.md

@@ -344,7 +344,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
 </step>
 
 <step n="6" goal="Update sprint status and finalize">
-  <action>Validate the newly created story file {story_file} against `./checklist.md` and apply any required fixes before finalizing</action>
+  <action>Validate the newly created story file {default_output_file} against `./checklist.md` and apply any required fixes before finalizing</action>
   <action>Save story document unconditionally</action>
 
   <!-- Update sprint status -->
@@ -359,7 +359,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
   </check>
 
   <action>Report completion</action>
-  <output>**🎯 ULTIMATE BMad Method STORY CONTEXT CREATED, {user_name}!**
+  <output>**🎯 ULTIMATE XiaoMa Method STORY CONTEXT CREATED, {user_name}!**
 
     **Story Details:**
     - Story ID: {{story_id}}
@@ -371,7 +371,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
     1. Review the comprehensive story in {{story_file}}
     2. Run dev agents `dev-story` for optimized implementation
     3. Run `code-review` when complete (auto-marks done)
-    4. Optional: If Test Architect module installed, run `/bmad:tea:automate` after `dev-story` to generate guardrail tests
+    4. Optional: If Test Architect module installed, run `/xiaoma:tea:automate` after `dev-story` to generate guardrail tests
 
     **The developer now has everything needed for flawless implementation!**
   </output>

package/src/xmc/workflows/4-implementation/xiaoma-dev-story/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-dev-story
 description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/4-implementation/xiaoma-dev-story/workflow.md

@@ -437,7 +437,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
       - Verify all acceptance criteria are met
       - Ensure deployment readiness if applicable
       - Run `code-review` workflow for peer review
-      - Optional: If Test Architect module installed, run `/bmad:tea:automate` to expand guardrail tests
+      - Optional: If Test Architect module installed, run `/xiaoma:tea:automate` to expand guardrail tests
     </action>
 
     <output>💡 **Tip:** For best results, run `code-review` using a **different** LLM than the one that implemented this story.</output>

package/src/xmc/workflows/4-implementation/xiaoma-retrospective/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-retrospective
 description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/4-implementation/xiaoma-sprint-planning/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-sprint-planning
 description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/4-implementation/xiaoma-sprint-planning/workflow.md

@@ -49,7 +49,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
 
 **Epic Discovery Process:**
 
-1. **Search for whole document first** - Look for `epics.md`, `bmm-epics.md`, or any `*epic*.md` file
+1. **Search for whole document first** - Look for `epics.md`, `xmc-epics.md`, or any `*epic*.md` file
 2. **Check for sharded version** - If whole document not found, look for `epics/index.md`
 3. **If sharded version found**:
    - Read `index.md` to understand the document structure
@@ -58,7 +58,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
    - This ensures complete sprint status coverage
 4. **Priority**: If both whole and sharded versions exist, use the whole document
 
-**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `bmm-epics.md`, `user-stories.md`, etc.
+**Fuzzy matching**: Be flexible with document names - users may use variations like `epics.md`, `xmc-epics.md`, `user-stories.md`, etc.
 
 <workflow>
 

package/src/xmc/workflows/4-implementation/xiaoma-sprint-status/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-sprint-status
 description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/4-implementation/xiaoma-sprint-status/workflow.md

@@ -59,7 +59,7 @@ Load config from `{project-root}/_xiaoma/xmc/config.yaml` and resolve:
   <action>Try {sprint_status_file}</action>
   <check if="file not found">
     <output>❌ sprint-status.yaml not found.
-Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
+Run `/xiaoma:xmc:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
     <action>Exit workflow</action>
   </check>
   <action>Continue to Step 2</action>
@@ -112,9 +112,9 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 <action>Detect risks:</action>
 
-- IF any story has status "review": suggest `/bmad:bmm:workflows:code-review`
+- IF any story has status "review": suggest `/xiaoma:xmc:workflows:code-review`
 - IF any story has status "in-progress" AND no stories have status "ready-for-dev": recommend staying focused on active story
-- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/bmad:bmm:workflows:create-story`
+- IF all epics have status "backlog" AND no stories have status "ready-for-dev": prompt `/xiaoma:xmc:workflows:create-story`
 - IF `last_updated` timestamp is more than 7 days old (or `last_updated` is missing, fall back to `generated`): warn "sprint-status.yaml may be stale"
 - IF any story key doesn't match an epic pattern (e.g., story "5-1-..." but no "epic-5"): warn "orphaned story detected"
 - IF any epic has status in-progress but has no associated stories: warn "in-progress epic has no stories"
@@ -144,7 +144,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 
 **Epics:** backlog {{epic_backlog}}, in-progress {{epic_in_progress}}, done {{epic_done}}
 
-**Next Recommendation:** /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
+**Next Recommendation:** /xiaoma:xmc:workflows:{{next_workflow_id}} ({{next_story_id}})
 
 {{#if risks}}
 **Risks:**
@@ -166,7 +166,7 @@ Enter corrections (e.g., "1=in-progress, 2=backlog") or "skip" to continue witho
 Choice:</ask>
 
   <check if="choice == 1">
-    <output>Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
+    <output>Run `/xiaoma:xmc:workflows:{{next_workflow_id}}`.
 If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
   </check>
 

package/src/xmc/workflows/xiaoma-document-project/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-document-project
 description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-document-project/templates/index-template.md

@@ -166,4 +166,4 @@ This documentation was generated specifically to enable AI agents to understand
 
 ---
 
-_Documentation generated by BMAD Method `document-project` workflow_
+_Documentation generated by XiaoMa Method `document-project` workflow_

package/src/xmc/workflows/xiaoma-document-project/templates/project-overview-template.md

@@ -100,4 +100,4 @@ For detailed information, see:
 
 ---
 
-_Generated using BMAD Method `document-project` workflow_
+_Generated using XiaoMa Method `document-project` workflow_

package/src/xmc/workflows/xiaoma-document-project/templates/source-tree-template.md

@@ -132,4 +132,4 @@ This project is organized into {{parts_count}} distinct parts:
 
 ---
 
-_Generated using BMAD Method `document-project` workflow_
+_Generated using XiaoMa Method `document-project` workflow_

package/src/xmc/workflows/xiaoma-generate-project-context/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-generate-project-context
 description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-generate-project-context/steps/step-01-discover.md

@@ -123,7 +123,7 @@ Based on discovery, create or update the context document:
 
 #### A. Fresh Document Setup (if no existing context)
 
-Copy template from `./project-context-template.md` to `{output_folder}/project-context.md`
+Copy template from `../project-context-template.md` to `{output_folder}/project-context.md`
 Initialize frontmatter fields.
 
 #### B. Existing Document Update
@@ -160,6 +160,8 @@ Ready to create/update your project context. This will help AI agents implement
 
 [C] Continue to context generation"
 
+**HALT — wait for user selection before proceeding.**
+
 ## SUCCESS METRICS:
 
 ✅ Existing project context properly detected and handled

package/src/xmc/workflows/xiaoma-generate-project-context/steps/step-02-generate.md

@@ -264,6 +264,8 @@ After each category, show the generated rules and present choices:
 [P] Party Mode - Review from different implementation perspectives
 [C] Continue - Save these rules and move to next category"
 
+**HALT — wait for user selection before proceeding.**
+
 ### 10. Handle Menu Selection
 
 #### If 'A' (Advanced Elicitation):

package/src/xmc/workflows/xiaoma-qa-generate-e2e-tests/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-qa-generate-e2e-tests
 description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-qa-generate-e2e-tests/checklist.md

@@ -30,4 +30,4 @@ Run the tests using your project's test command.
 
 ---
 
-**Need more comprehensive testing?** Install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) for advanced workflows.
+**Need more comprehensive testing?** Install [Test Architect (TEA)](https://xiaoma-code-org.github.io/xiaoma-cli-test-architecture-enterprise/) for advanced workflows.

package/src/xmc/workflows/xiaoma-qa-generate-e2e-tests/workflow.md

@@ -2,7 +2,7 @@
 
 **Goal:** Generate automated API and E2E tests for implemented code.
 
-**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use Code Review `CR` for that).
+**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `xiaoma-code-review` skill for that).
 
 ---
 
@@ -127,7 +127,7 @@ If the project needs:
 - Comprehensive coverage analysis
 - Advanced testing patterns and utilities
 
-> **Install Test Architect (TEA) module**: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
+> **Install Test Architect (TEA) module**: <https://xiaoma-code-org.github.io/xiaoma-cli-test-architecture-enterprise/>
 
 ## Output
 

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-dev/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-quick-dev
 description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-dev/steps/step-01-mode-detection.md

@@ -102,7 +102,7 @@ Present: "This looks like a focused feature with multiple components."
 Display:
 
 **[P] Plan first (tech-spec)** (recommended)
-**[W] Seems bigger than quick-dev** - Recommend the Full BMad Flow PRD Process
+**[W] Seems bigger than quick-dev** - Recommend the Full XiaoMa Flow PRD Process
 **[E] Execute directly**
 
 #### Menu Handling Logic:
@@ -124,7 +124,7 @@ Present: "This sounds like platform/system work."
 
 Display:
 
-**[W] Start BMad Method** (recommended)
+**[W] Start XiaoMa Method** (recommended)
 **[P] Plan first (tech-spec)** (lighter planning)
 **[E] Execute directly** - feeling lucky
 

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-dev-new-preview/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-quick-dev-new-preview
 description: 'Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project''s existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-spec/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-quick-spec
 description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/xiaoma-quick-flow/xiaoma-quick-spec/workflow.md

@@ -1,5 +1,6 @@
 ---
 main_config: '{project-root}/_xiaoma/xmc/config.yaml'
+
 ---
 
 # Quick-Spec Workflow

package/tools/cli/README.md

@@ -1,14 +1,14 @@
-# BMad CLI Tool
+# XiaoMa CLI Tool
 
-## Installing external repo BMad official modules
+## Installing external repo XiaoMa official modules
 
 For external official modules to be discoverable during install, ensure an entry for the external repo is added to external-official-modules.yaml.
 
-For community modules - this will be handled in a different way. This file is only for registration of modules under the bmad-code-org.
+For community modules - this will be handled in a different way. This file is only for registration of modules under the xiaoma-code-org.
 
 ## Post-Install Notes
 
-Modules can display setup guidance to users after configuration is collected during `npx bmad-method install`. Notes are defined in the module's own `module.yaml` — no changes to the installer are needed.
+Modules can display setup guidance to users after configuration is collected during `npx xiaoma-cli install`. Notes are defined in the module's own `module.yaml` — no changes to the installer are needed.
 
 ### Simple Format
 

package/tools/cli/commands/install.js

@@ -29,7 +29,7 @@ module.exports = {
     try {
       // Set debug flag as environment variable for all components
       if (options.debug) {
-        process.env.XIAOMA_DEBUG_MANIFEST = 'true';
+        process.env.XiaoMa_DEBUG_MANIFEST = 'true';
         await prompts.log.info('Debug mode enabled');
       }
 

package/tools/cli/commands/status.js

@@ -10,7 +10,7 @@ const ui = new UI();
 
 module.exports = {
   command: 'status',
-  description: 'Display XIAOMA installation status and module versions',
+  description: 'Display XiaoMa installation status and module versions',
   options: [],
   action: async (options) => {
     try {
@@ -21,7 +21,7 @@ module.exports = {
       // Check if xiaoma directory exists
       const fs = require('fs-extra');
       if (!(await fs.pathExists(xiaomaDir))) {
-        await prompts.log.warn('No XIAOMA installation found in the current directory.');
+        await prompts.log.warn('No XiaoMa installation found in the current directory.');
         await prompts.log.message(`Expected location: ${xiaomaDir}`);
         await prompts.log.message('Run "xiaoma install" to set up a new installation.');
         process.exit(0);
@@ -32,7 +32,7 @@ module.exports = {
       const manifestData = await manifest._readRaw(xiaomaDir);
 
       if (!manifestData) {
-        await prompts.log.warn('No XIAOMA installation manifest found.');
+        await prompts.log.warn('No XiaoMa installation manifest found.');
         await prompts.log.message('Run "xiaoma install" to set up a new installation.');
         process.exit(0);
         return;
@@ -56,7 +56,7 @@ module.exports = {
       process.exit(0);
     } catch (error) {
       await prompts.log.error(`Status check failed: ${error.message}`);
-      if (process.env.XIAOMA_DEBUG) {
+      if (process.env.XiaoMa_DEBUG) {
         await prompts.log.message(error.stack);
       }
       process.exit(1);

package/tools/cli/commands/uninstall.js

@@ -7,9 +7,9 @@ const installer = new Installer();
 
 module.exports = {
   command: 'uninstall',
-  description: 'Remove XIAOMA installation from the current project',
+  description: 'Remove XiaoMa installation from the current project',
   options: [
-    ['-y, --yes', 'Remove all XIAOMA components without prompting (preserves user artifacts)'],
+    ['-y, --yes', 'Remove all XiaoMa components without prompting (preserves user artifacts)'],
     ['--directory <path>', 'Project directory (default: current directory)'],
   ],
   action: async (options) => {
@@ -26,7 +26,7 @@ module.exports = {
         // Interactive: ask user which directory to uninstall from
         // select() handles cancellation internally (exits process)
         const dirChoice = await prompts.select({
-          message: 'Where do you want to uninstall XIAOMA from?',
+          message: 'Where do you want to uninstall XiaoMa from?',
           choices: [
             { value: 'cwd', name: `Current directory (${process.cwd()})` },
             { value: 'other', name: 'Another directory...' },
@@ -57,7 +57,7 @@ module.exports = {
       const { xiaomaDir } = await installer.findXiaomaDir(projectDir);
 
       if (!(await fs.pathExists(xiaomaDir))) {
-        await prompts.log.warn('No XIAOMA installation found.');
+        await prompts.log.warn('No XiaoMa installation found.');
         process.exit(0);
       }
 
@@ -68,7 +68,7 @@ module.exports = {
 
       const outputFolder = await installer.getOutputFolder(projectDir);
 
-      await prompts.intro('XIAOMA Uninstall');
+      await prompts.intro('XiaoMa Uninstall');
       await prompts.note(`Version: ${version}\nModules: ${modules}\nIDE integrations: ${ides}`, 'Current Installation');
 
       let removeModules = true;
@@ -82,7 +82,7 @@ module.exports = {
           options: [
             {
               value: 'modules',
-              label: `XIAOMA Modules & data (${installer.bmadFolderName}/)`,
+              label: `XiaoMa Modules & data (${installer.xiaomaFolderName}/)`,
               hint: 'Core installation, agents, workflows, config',
             },
             { value: 'ide', label: 'IDE integrations', hint: ides || 'No IDEs configured' },
@@ -133,10 +133,10 @@ module.exports = {
         s.stop('User artifacts removed');
       }
 
-      // Phase 3: XIAOMA modules & data (last — other phases may need _xiaoma/)
+      // Phase 3: XiaoMa modules & data (last — other phases may need _xiaoma/)
       if (removeModules) {
         const s = await prompts.spinner();
-        s.start(`Removing XIAOMA modules & data (${installer.bmadFolderName}/)...`);
+        s.start(`Removing XiaoMa modules & data (${installer.xiaomaFolderName}/)...`);
         await installer.uninstallModules(projectDir);
         s.stop('Modules & data removed');
       }
@@ -148,7 +148,7 @@ module.exports = {
       if (!removeOutputFolder) summary.push(`User artifacts preserved in ${outputFolder}/`);
 
       await prompts.note(summary.join('\n'), 'Summary');
-      await prompts.outro('To reinstall, run: npx @zeyue0329/xiaoma-cli install');
+      await prompts.outro('To reinstall, run: npx xiaoma-cli install');
 
       process.exit(0);
     } catch (error) {

package/tools/cli/external-official-modules.yaml

@@ -1,56 +1,4 @@
-# This file allows these modules under xiaoma-code-org to also be installed with the xiaoma installer, while
-# allowing us to keep the source of these projects in separate repos.
+# External modules are not applicable for XiaoMa-CLI
+# These were upstream XiaoMa modules that are not forked
 
 modules: {}
-  # External modules are disabled because they require GitHub access to clone.
-  # To re-enable, uncomment the module entries below and ensure GitHub is accessible.
-  #
-  # xiaoma-builder:
-  #   url: https://github.com/xiaoma-code-org/xiaoma-builder
-  #   module-definition: src/module.yaml
-  #   code: bmb
-  #   name: "XiaoMa Builder"
-  #   description: "Agent and Builder"
-  #   defaultSelected: false
-  #   type: xiaoma-org
-  #   npmPackage: xiaoma-builder
-  #
-  # xiaoma-creative-intelligence-suite:
-  #   url: https://github.com/xiaoma-code-org/xiaoma-module-creative-intelligence-suite
-  #   module-definition: src/module.yaml
-  #   code: cis
-  #   name: "XiaoMa Creative Intelligence Suite"
-  #   description: "Creative tools for writing, brainstorming, and more"
-  #   defaultSelected: false
-  #   type: xiaoma-org
-  #   npmPackage: xiaoma-creative-intelligence-suite
-  #
-  # xiaoma-game-dev-studio:
-  #   url: https://github.com/xiaoma-code-org/xiaoma-module-game-dev-studio.git
-  #   module-definition: src/module.yaml
-  #   code: gds
-  #   name: "XiaoMa Game Dev Studio"
-  #   description: "Game development agents and workflows"
-  #   defaultSelected: false
-  #   type: xiaoma-org
-  #   npmPackage: xiaoma-game-dev-studio
-  #
-  # xiaoma-method-test-architecture-enterprise:
-  #   url: https://github.com/xiaoma-code-org/xiaoma-method-test-architecture-enterprise
-  #   module-definition: src/module.yaml
-  #   code: tea
-  #   name: "Test Architect"
-  #   description: "Master Test Architect for quality strategy, test automation, and release gates"
-  #   defaultSelected: false
-  #   type: xiaoma-org
-  #   npmPackage: xiaoma-method-test-architecture-enterprise
-  #
-  # whiteport-design-studio:
-  #   url: https://github.com/xiaoma-code-org/xiaoma-method-wds-expansion
-  #   module-definition: src/module.yaml
-  #   code: wds
-  #   name: "Whiteport Design Studio (For UX Professionals)"
-  #   description: "Whiteport Design Studio (For UX Professionals)"
-  #   defaultSelected: false
-  #   type: community
-  #   npmPackage: xiaoma-method-wds-expansion

package/tools/cli/installers/install-messages.yaml

@@ -1,4 +1,4 @@
-# BMAD Installer Messages
+# XiaoMa Installer Messages
 # These messages are displayed during installation
 # Edit this file to change what users see during the install process
 
@@ -12,7 +12,7 @@ startMessage: |
     - Select and install modules during setup - customize your experience
     - New XiaoMa Method for Agile AI-Driven Development (the evolution of V4)
     - Exciting new modules available during installation, with community modules coming soon
-    - Documentation: https://docs.xiaoma.org
+    - Documentation: https://docs.xiaoma-cli.org
 
   🌟 XiaoMa is 100% free and open source.
     - No gated Discord. No paywalls. No gated content.
@@ -25,13 +25,13 @@ startMessage: |
     - For speaking inquiries or interviews, reach out to XiaoMa on Discord!
 
   ⭐ HELP US GROW:
-    - Star us on GitHub: https://github.com/xiaoma-code-org/XiaoMa-Cli/
+    - Star us on GitHub: https://github.com/xiaoma-code-org/XiaoMa-CLI/
     - Subscribe on YouTube: https://www.youtube.com/@XiaoMaCode
     - Free Community and Support: https://discord.gg/gk8jAdXWmj
-    - Donate: https://buymeacoffee.com/bmad
+    - Donate: https://buymeacoffee.com/xiaoma
     - Corporate Sponsorship available
 
-  Latest updates: https://github.com/xiaoma-code-org/XiaoMa-Cli/blob/main/CHANGELOG.md
+  Latest updates: https://github.com/xiaoma-code-org/XiaoMa-CLI/blob/main/CHANGELOG.md
 
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 

package/tools/cli/installers/lib/core/config-collector.js

@@ -61,11 +61,11 @@ class ConfigCollector {
   }
 
   /**
-   * Detect the existing BMAD folder name in a project
+   * Detect the existing XiaoMa folder name in a project
    * @param {string} projectDir - Project directory
    * @returns {Promise<string|null>} Folder name (just the name, not full path) or null if not found
    */
-  async detectExistingBmadFolder(projectDir) {
+  async detectExistingXiaomaFolder(projectDir) {
     // Check if project directory exists
     if (!(await fs.pathExists(projectDir))) {
       return null;

package/tools/cli/installers/lib/core/dependency-resolver.js

@@ -5,7 +5,7 @@ const yaml = require('yaml');
 const prompts = require('../../../lib/prompts');
 
 /**
- * Dependency Resolver for BMAD modules
+ * Dependency Resolver for XiaoMa modules
  * Handles cross-module dependencies and ensures all required files are included
  */
 class DependencyResolver {
@@ -17,7 +17,7 @@ class DependencyResolver {
 
   /**
    * Resolve all dependencies for selected modules
-   * @param {string} xiaomaDir - BMAD installation directory
+   * @param {string} xiaomaDir - XiaoMa installation directory
    * @param {Array} selectedModules - Modules explicitly selected by user
    * @param {Object} options - Resolution options
    * @returns {Object} Resolution results with all required files

package/tools/cli/installers/lib/core/detector.js

@@ -5,7 +5,7 @@ const { Manifest } = require('./manifest');
 
 class Detector {
   /**
-   * Detect existing BMAD installation
+   * Detect existing XiaoMa installation
    * @param {string} xiaomaDir - Path to xiaoma directory
    * @returns {Object} Installation status and details
    */
@@ -135,7 +135,7 @@ class Detector {
   }
 
   /**
-   * Detect legacy installation (_xiaoma-method, .bmm, .cis)
+   * Detect legacy installation (_xiaoma-cli, .xmc, .cis)
    * @param {string} projectDir - Project directory to check
    * @returns {Object} Legacy installation details
    */
@@ -147,8 +147,8 @@ class Detector {
       paths: [],
     };
 
-    // Check for legacy core (_xiaoma-method)
-    const legacyCorePath = path.join(projectDir, '_xiaoma-method');
+    // Check for legacy core (_xiaoma-cli)
+    const legacyCorePath = path.join(projectDir, '_xiaoma-cli');
     if (await fs.pathExists(legacyCorePath)) {
       result.hasLegacy = true;
       result.legacyCore = true;
@@ -161,7 +161,7 @@ class Detector {
       if (
         entry.isDirectory() &&
         entry.name.startsWith('.') &&
-        entry.name !== '_xiaoma-method' &&
+        entry.name !== '_xiaoma-cli' &&
         !entry.name.startsWith('.git') &&
         !entry.name.startsWith('.vscode') &&
         !entry.name.startsWith('.idea')
@@ -169,7 +169,7 @@ class Detector {
         const modulePath = path.join(projectDir, entry.name);
         const moduleManifestPath = path.join(modulePath, 'install-manifest.yaml');
 
-        // Check if it's likely a BMAD module
+        // Check if it's likely a XiaoMa module
         if ((await fs.pathExists(moduleManifestPath)) || (await fs.pathExists(path.join(modulePath, 'config.yaml')))) {
           result.hasLegacy = true;
           result.legacyModules.push({
@@ -203,15 +203,15 @@ class Detector {
   }
 
   /**
-   * Detect legacy BMAD v4 .xiaoma-method folder
+   * Detect legacy XiaoMa v4 .xiaoma-cli folder
    * @param {string} projectDir - Project directory to check
    * @returns {{ hasLegacyV4: boolean, offenders: string[] }}
    */
   async detectLegacyV4(projectDir) {
     const offenders = [];
 
-    // Check for .xiaoma-method folder
-    const xiaomaMethodPath = path.join(projectDir, '.xiaoma-method');
+    // Check for .xiaoma-cli folder
+    const xiaomaMethodPath = path.join(projectDir, '.xiaoma-cli');
     if (await fs.pathExists(xiaomaMethodPath)) {
       offenders.push(xiaomaMethodPath);
     }