@zeyue0329/xiaoma-cli 1.6.4 → 1.7.0

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/prompts/guided-elicitation.md

@@ -0,0 +1,70 @@
+**Language:** Use `{communication_language}` for all output.
+**Output Language:** Use `{document_output_language}` for documents.
+
+# Stage 3: Guided Elicitation
+
+**Goal:** Fill the gaps in what you know. By now you have the user's brain dump, artifact analysis, and web research. This stage is about smart, targeted questioning — not rote section-by-section interrogation.
+
+**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `prompts/draft-and-review.md`.
+
+## Approach
+
+You are NOT walking through a rigid questionnaire. You're having a conversation that covers the substance of a great product brief. The topics below are your mental checklist, not a script. Adapt to:
+- What you already know (don't re-ask what's been covered)
+- What the user is excited about (follow their energy)
+- What's genuinely unclear (focus questions where they matter)
+
+## Topics to Cover (flexibly, conversationally)
+
+### Vision & Problem
+- What core problem does this solve? For whom?
+- How do people solve this today? What's frustrating about current approaches?
+- What would success look like for the people this helps?
+- What's the insight or angle that makes this approach different?
+
+### Users & Value
+- Who experiences this problem most acutely?
+- Are there different user types with different needs?
+- What's the "aha moment" — when does a user realize this is what they needed?
+- How does this fit into their existing workflow or life?
+
+### Market & Differentiation
+- What competitive or alternative solutions exist? (Leverage web research findings)
+- What's the unfair advantage or defensible moat?
+- Why is now the right time for this?
+
+### Success & Scope
+- How will you know this is working? What metrics matter?
+- What's the minimum viable version that creates real value?
+- What's explicitly NOT in scope for the first version?
+- If this is wildly successful, what does it become in 2-3 years?
+
+## The Flow
+
+For each topic area where you have gaps:
+
+1. **Lead with what you know** — "Based on your input and my research, it sounds like [X]. Is that right?"
+2. **Ask the gap question** — targeted, specific, not generic
+3. **Reflect and confirm** — paraphrase what you heard
+4. **"Anything else on this, or shall we move on?"** — the soft gate
+
+If the user is giving you detail beyond brief scope (requirements, architecture, platform details, timelines), **capture it silently** for the distillate. Acknowledge it briefly ("Good detail, I'll capture that") but don't derail the conversation.
+
+## When to Move On
+
+When you have enough substance to draft a compelling 1-2 page executive brief covering:
+- Clear problem and who it affects
+- Proposed solution and what makes it different
+- Target users (at least primary)
+- Some sense of success criteria or business objectives
+- MVP-level scope thinking
+
+You don't need perfection — you need enough to draft well. Missing details can be surfaced during the review stage.
+
+If the user is providing complete, confident answers and you have solid coverage across all four topic areas after fewer than 3-4 exchanges, proactively offer to draft early.
+
+**Transition:** "I think I have a solid picture. Ready for me to draft the brief, or is there anything else you'd like to add?"
+
+## Stage Complete
+
+This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `prompts/draft-and-review.md`.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/resources/brief-template.md

@@ -0,0 +1,60 @@
+# Product Brief Template
+
+This is a flexible guide for the executive product brief — adapt it to serve the product's story. Merge sections, add new ones, reorder as needed. The product determines the structure, not the template.
+
+## Sensible Default Structure
+
+```markdown
+# Product Brief: {Product Name}
+
+## Executive Summary
+
+[2-3 paragraph narrative: What is this? What problem does it solve? Why does it matter? Why now?
+This should be compelling enough to stand alone — if someone reads only this section, they should understand the vision.]
+
+## The Problem
+
+[What pain exists? Who feels it? How are they coping today? What's the cost of the status quo?
+Be specific — real scenarios, real frustrations, real consequences.]
+
+## The Solution
+
+[What are we building? How does it solve the problem?
+Focus on the experience and outcome, not the implementation.]
+
+## What Makes This Different
+
+[Key differentiators. Why this approach vs alternatives? What's the unfair advantage?
+Be honest — if the moat is execution speed, say so. Don't fabricate technical moats.]
+
+## Who This Serves
+
+[Primary users — vivid but brief. Who are they, what do they need, what does success look like for them?
+Secondary users if relevant.]
+
+## Success Criteria
+
+[How do we know this is working? What metrics matter?
+Mix of user success signals and business objectives. Be measurable.]
+
+## Scope
+
+[What's in for the first version? What's explicitly out?
+Keep this tight — it's a boundary document, not a feature list.]
+
+## Vision
+
+[Where does this go if it succeeds? What does it become in 2-3 years?
+Inspiring but grounded.]
+```
+
+## Adaptation Guidelines
+
+- **For B2B products:** Consider adding a "Buyer vs User" section if they're different people
+- **For platforms/marketplaces:** Consider a "Network Effects" or "Ecosystem" section
+- **For technical products:** May need a brief "Technical Approach" section (keep it high-level)
+- **For regulated industries:** Consider a "Compliance & Regulatory" section
+- **If scope is well-defined:** Merge "Scope" and "Vision" into "Roadmap Thinking"
+- **If the problem is well-known:** Shorten "The Problem" and expand "What Makes This Different"
+
+The brief should be 1-2 pages. If it's longer, you're putting in too much detail — that's what the distillate is for.

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/xiaoma-manifest.json

@@ -0,0 +1,17 @@
+{
+  "module-code": "bmm",
+  "replaces-skill": "bmad-create-product-brief",
+  "capabilities": [
+    {
+      "name": "create-brief",
+      "menu-code": "CB",
+      "description": "Produces executive product brief and optional LLM distillate for PRD input.",
+      "supports-headless": true,
+      "phase-name": "1-analysis",
+      "after": ["brainstorming, perform-research"],
+      "before": ["create-prd"],
+      "is-required": true,
+      "output-location": "{planning_artifacts}"
+    }
+  ]
+}

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/xiaoma-skill-manifest.yaml

@@ -0,0 +1 @@
+type: skill

package/src/xmc/workflows/2-plan-workflows/create-prd/data/prd-purpose.md

@@ -1,10 +1,10 @@
-# XiaoMa PRD Purpose
+# BMAD PRD Purpose
 
-**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw XiaoMa Method.**
+**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw BMad Method.**
 
 ---
 
-## What is a XiaoMa PRD?
+## What is a BMAD PRD?
 
 A dual-audience document serving:
 1. **Human Product Managers and builders** - Vision, strategy, stakeholder communication
@@ -182,7 +182,7 @@ Certain industries have mandatory requirements that must be present:
 
 ---
 
-## Summary: What Makes a Great XiaoMa PRD?
+## Summary: What Makes a Great BMAD PRD?
 
 ✅ **High Information Density** - Every sentence carries weight, zero fluff
 ✅ **Measurable Requirements** - All FRs and NFRs are testable with specific criteria

package/src/xmc/workflows/2-plan-workflows/create-prd/data/project-types.csv

@@ -5,7 +5,7 @@ saas_b2b,"SaaS,B2B,platform,dashboard,teams,enterprise","Multi-tenant?;Permissio
 developer_tool,"SDK,library,package,npm,pip,framework","Language support?;Package managers?;IDE integration?;Documentation?;Examples?","language_matrix;installation_methods;api_surface;code_examples;migration_guide","visual_design;store_compliance","package manager best practices;API design patterns","New paradigm;DSL creation"
 cli_tool,"CLI,command,terminal,bash,script","Interactive or scriptable?;Output formats?;Config method?;Shell completion?","command_structure;output_formats;config_schema;scripting_support","visual_design;ux_principles;touch_interactions","CLI design patterns;shell integration","Natural language CLI;AI commands"
 web_app,"website,webapp,browser,SPA,PWA","SPA or MPA?;Browser support?;SEO needed?;Real-time?;Accessibility?","browser_matrix;responsive_design;performance_targets;seo_strategy;accessibility_level","native_features;cli_commands","web standards;WCAG guidelines","New interaction;WebAssembly use"
-game,"game,player,gameplay,level,character","REDIRECT TO USE THE XiaoMa Method Game Module Agent and Workflows - HALT","game-brief;GDD","most_sections","game design patterns","Novel mechanics;Genre mixing"
+game,"game,player,gameplay,level,character","REDIRECT TO USE THE BMad Method Game Module Agent and Workflows - HALT","game-brief;GDD","most_sections","game design patterns","Novel mechanics;Genre mixing"
 desktop_app,"desktop,Windows,Mac,Linux,native","Cross-platform?;Auto-update?;System integration?;Offline?","platform_support;system_integration;update_strategy;offline_capabilities","web_seo;mobile_features","desktop guidelines;platform requirements","Desktop AI;System automation"
 iot_embedded,"IoT,embedded,device,sensor,hardware","Hardware specs?;Connectivity?;Power constraints?;Security?;OTA updates?","hardware_reqs;connectivity_protocol;power_profile;security_model;update_mechanism","visual_ui;browser_support","IoT standards;protocol specs","Edge AI;New sensors"
 blockchain_web3,"blockchain,crypto,DeFi,NFT,smart contract","Chain selection?;Wallet integration?;Gas optimization?;Security audit?","chain_specs;wallet_support;smart_contracts;security_audit;gas_optimization","traditional_auth;centralized_db","blockchain standards;security patterns","Novel tokenomics;DAO structure"

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md

@@ -4,8 +4,6 @@ description: 'Document Discovery & Confirmation - Handle fresh context validatio
 
 # File references (ONLY variables used in this step)
 nextStepFile: './step-v-02-format-detection.md'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
-partyModeWorkflow: '{project-root}/_xiaoma/core/workflows/party-mode/workflow.md'
 prdPurpose: '../data/prd-purpose.md'
 ---
 
@@ -63,7 +61,7 @@ Handle fresh context validation by confirming PRD path, discovering and loading
 Load and read the complete file at:
 `{prdPurpose}`
 
-This file contains the XiaoMa PRD philosophy, standards, and validation criteria that will guide all validation checks. Internalize this understanding - it defines what makes a great XiaoMa PRD.
+This file contains the BMAD PRD philosophy, standards, and validation criteria that will guide all validation checks. Internalize this understanding - it defines what makes a great BMAD PRD.
 
 ### 2. Discover PRD to Validate
 
@@ -195,8 +193,8 @@ Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Conti
 
 #### Menu Handling Logic:
 
-- IF A: Read fully and follow: {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Read fully and follow: {partyModeWorkflow}, and when finished redisplay the menu
+- IF A: Invoke the `xiaoma-advanced-elicitation` skill, and when finished redisplay the menu
+- IF P: Invoke the `xiaoma-party-mode` skill, and when finished redisplay the menu
 - IF C: Read fully and follow: {nextStepFile} to begin format detection
 - IF user provides additional document: Load it, update report, redisplay summary
 - IF Any other: help user, then redisplay menu

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-02-format-detection.md

@@ -13,7 +13,7 @@ validationReportPath: '{validation_report_path}'
 
 ## STEP GOAL:
 
-Detect if PRD follows XiaoMa format and route appropriately - classify as XiaoMa Standard / XiaoMa Variant / Non-Standard, with optional parity check for non-standard formats.
+Detect if PRD follows BMAD format and route appropriately - classify as BMAD Standard / BMAD Variant / Non-Standard, with optional parity check for non-standard formats.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -72,9 +72,9 @@ Load the complete PRD file and extract:
 - Extract classification.projectType if present
 - Note any other relevant metadata
 
-### 2. Check for XiaoMa PRD Core Sections
+### 2. Check for BMAD PRD Core Sections
 
-Check if the PRD contains the following XiaoMa PRD core sections:
+Check if the PRD contains the following BMAD PRD core sections:
 
 1. **Executive Summary** (or variations: ## Executive Summary, ## Overview, ## Introduction)
 2. **Success Criteria** (or: ## Success Criteria, ## Goals, ## Objectives)
@@ -92,18 +92,18 @@ Check if the PRD contains the following XiaoMa PRD core sections:
 
 Based on core section count, classify:
 
-**XiaoMa Standard:**
+**BMAD Standard:**
 - 5-6 core sections present
-- Follows XiaoMa PRD structure closely
+- Follows BMAD PRD structure closely
 
-**XiaoMa Variant:**
+**BMAD Variant:**
 - 3-4 core sections present
-- Generally follows XiaoMa patterns but may have structural differences
-- Missing some sections but recognizable as XiaoMa-style
+- Generally follows BMAD patterns but may have structural differences
+- Missing some sections but recognizable as BMAD-style
 
 **Non-Standard:**
 - Fewer than 3 core sections present
-- Does not follow XiaoMa PRD structure
+- Does not follow BMAD PRD structure
 - May be completely custom format, legacy format, or from another framework
 
 ### 4. Report Format Findings to Validation Report
@@ -116,7 +116,7 @@ Append to validation report:
 **PRD Structure:**
 [List all ## Level 2 headers found]
 
-**XiaoMa Core Sections Present:**
+**BMAD Core Sections Present:**
 - Executive Summary: [Present/Missing]
 - Success Criteria: [Present/Missing]
 - Product Scope: [Present/Missing]
@@ -124,13 +124,13 @@ Append to validation report:
 - Functional Requirements: [Present/Missing]
 - Non-Functional Requirements: [Present/Missing]
 
-**Format Classification:** [XiaoMa Standard / XiaoMa Variant / Non-Standard]
+**Format Classification:** [BMAD Standard / BMAD Variant / Non-Standard]
 **Core Sections Present:** [count]/6
 ```
 
 ### 5. Route Based on Format Classification
 
-**IF format is XiaoMa Standard or XiaoMa Variant:**
+**IF format is BMAD Standard or BMAD Variant:**
 
 Display: "**Format Detected:** {classification}
 
@@ -142,7 +142,7 @@ Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validati
 
 Display: "**Format Detected:** Non-Standard PRD
 
-This PRD does not follow XiaoMa standard structure (only {count}/6 core sections present).
+This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
 
 You have options:"
 
@@ -150,7 +150,7 @@ Present MENU OPTIONS below for user selection
 
 ### 6. Present MENU OPTIONS (Non-Standard PRDs Only)
 
-**[A] Parity Check** - Analyze gaps and estimate effort to reach XiaoMa PRD parity
+**[A] Parity Check** - Analyze gaps and estimate effort to reach BMAD PRD parity
 **[B] Validate As-Is** - Proceed with validation using current structure
 **[C] Exit** - Exit validation and review format findings
 
@@ -173,10 +173,10 @@ Present MENU OPTIONS below for user selection
 ### ✅ SUCCESS:
 
 - All ## Level 2 headers extracted successfully
-- XiaoMa core sections checked systematically
+- BMAD core sections checked systematically
 - Format classified correctly based on section count
 - Findings reported to validation report
-- XiaoMa Standard/Variant PRDs proceed directly to next validation step
+- BMAD Standard/Variant PRDs proceed directly to next validation step
 - Non-Standard PRDs pause and present options to user
 - User can choose parity check, validate as-is, or exit
 

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-02b-parity-check.md

@@ -1,6 +1,6 @@
 ---
 name: 'step-v-02b-parity-check'
-description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve XiaoMa PRD parity'
+description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity'
 
 # File references (ONLY variables used in this step)
 nextStepFile: './step-v-03-density-validation.md'
@@ -12,7 +12,7 @@ validationReportPath: '{validation_report_path}'
 
 ## STEP GOAL:
 
-Analyze non-standard PRD and identify gaps to achieve XiaoMa PRD parity, presenting user with options for how to proceed.
+Analyze non-standard PRD and identify gaps to achieve BMAD PRD parity, presenting user with options for how to proceed.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -29,7 +29,7 @@ Analyze non-standard PRD and identify gaps to achieve XiaoMa PRD parity, present
 - ✅ You are a Validation Architect and Quality Assurance Specialist
 - ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
 - ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring XiaoMa PRD standards expertise and gap analysis
+- ✅ You bring BMAD PRD standards expertise and gap analysis
 - ✅ User brings domain knowledge and PRD context
 
 ### Step-Specific Rules:
@@ -41,7 +41,7 @@ Analyze non-standard PRD and identify gaps to achieve XiaoMa PRD parity, present
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Analyze each XiaoMa PRD section for gaps
+- 🎯 Analyze each BMAD PRD section for gaps
 - 💾 Append parity analysis to validation report
 - 📖 Present options and await user decision
 - 🚫 FORBIDDEN to proceed without user selection
@@ -57,9 +57,9 @@ Analyze non-standard PRD and identify gaps to achieve XiaoMa PRD parity, present
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
 
-### 1. Analyze Each XiaoMa PRD Section
+### 1. Analyze Each BMAD PRD Section
 
-For each of the 6 XiaoMa PRD core sections, analyze:
+For each of the 6 BMAD PRD core sections, analyze:
 
 **Executive Summary:**
 - Does PRD have vision/overview?
@@ -147,7 +147,7 @@ Append to validation report:
 
 ### Overall Parity Assessment
 
-**Overall Effort to Reach XiaoMa Standard:** [Quick/Moderate/Substantial]
+**Overall Effort to Reach BMAD Standard:** [Quick/Moderate/Substantial]
 **Recommendation:** [Brief recommendation based on analysis]
 ```
 
@@ -157,7 +157,7 @@ Display:
 
 "**Parity Analysis Complete**
 
-Your PRD is missing {count} of 6 core XiaoMa PRD sections. The overall effort to reach XiaoMa standard is: **{effort level}**
+Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}**
 
 **Quick Summary:**
 [2-3 sentence summary of key gaps]
@@ -191,7 +191,7 @@ Your PRD is missing {count} of 6 core XiaoMa PRD sections. The overall effort to
 
 ### ✅ SUCCESS:
 
-- All 6 XiaoMa PRD sections analyzed for gaps
+- All 6 BMAD PRD sections analyzed for gaps
 - Effort estimates provided for each gap
 - Overall parity effort assessed correctly
 - Parity analysis reported to validation report

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-03-density-validation.md

@@ -12,7 +12,7 @@ validationReportPath: '{validation_report_path}'
 
 ## STEP GOAL:
 
-Validate PRD meets XiaoMa information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.
+Validate PRD meets BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-10-smart-validation.md

@@ -6,7 +6,6 @@ description: 'SMART Requirements Validation - Validate Functional Requirements m
 nextStepFile: './step-v-11-holistic-quality-validation.md'
 prdFile: '{prd_file_path}'
 validationReportPath: '{validation_report_path}'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
 ---
 
 # Step 10: SMART Requirements Validation
@@ -24,6 +23,7 @@ Validate Functional Requirements meet SMART quality criteria (Specific, Measurab
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-11-holistic-quality-validation.md

@@ -6,14 +6,13 @@ description: 'Holistic Quality Assessment - Assess PRD as cohesive, compelling d
 nextStepFile: './step-v-12-completeness-validation.md'
 prdFile: '{prd_file_path}'
 validationReportPath: '{validation_report_path}'
-advancedElicitationTask: '{project-root}/_xiaoma/core/workflows/advanced-elicitation/workflow.md'
 ---
 
 # Step 11: Holistic Quality Assessment
 
 ## STEP GOAL:
 
-Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), XiaoMa PRD principles compliance, and overall quality rating.
+Assess the PRD as a cohesive, compelling document - evaluating document flow, dual audience effectiveness (humans and LLMs), BMAD PRD principles compliance, and overall quality rating.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -24,6 +23,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 
@@ -44,7 +44,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 ## EXECUTION PROTOCOLS:
 
 - 🎯 Use Advanced Elicitation for multi-perspective assessment
-- 🎯 Evaluate document flow, dual audience, XiaoMa principles
+- 🎯 Evaluate document flow, dual audience, BMAD principles
 - 💾 Append comprehensive assessment to validation report
 - 📖 Display "Proceeding to next check..." and load next step
 - 🚫 FORBIDDEN to pause or request user input
@@ -66,8 +66,8 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 
 "Perform holistic quality assessment on this PRD using multi-perspective evaluation:
 
-**Read fully and follow the Advanced Elicitation workflow:**
-{advancedElicitationTask}
+**Advanced Elicitation workflow:**
+Invoke the `xiaoma-advanced-elicitation` skill
 
 **Evaluate the PRD from these perspectives:**
 
@@ -92,7 +92,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
 - Architecture readiness: Can an LLM generate architecture from this?
 - Epic/Story readiness: Can an LLM break down into epics and stories?
 
-**3. XiaoMa PRD Principles Compliance:**
+**3. BMAD PRD Principles Compliance:**
 - Information density: Every sentence carries weight?
 - Measurability: Requirements testable?
 - Traceability: Requirements trace to sources?
@@ -119,7 +119,7 @@ Return comprehensive assessment with all perspectives, rating, and top 3 improve
 - Read complete PRD
 - Evaluate document flow, coherence, transitions
 - Assess dual audience effectiveness
-- Check XiaoMa principles compliance
+- Check BMAD principles compliance
 - Assign overall quality rating
 - Identify top 3 improvements
 
@@ -137,7 +137,7 @@ Return comprehensive assessment with all perspectives, rating, and top 3 improve
 - For LLMs: [assessment]
 - Overall dual audience score: [1-5]
 
-**XiaoMa Principles Compliance:**
+**BMAD Principles Compliance:**
 - Principles met: [count]/7
 - Principles with issues: [list]
 
@@ -181,7 +181,7 @@ Append to validation report:
 
 **Dual Audience Score:** {score}/5
 
-### XiaoMa PRD Principles Compliance
+### BMAD PRD Principles Compliance
 
 | Principle | Status | Notes |
 |-----------|--------|-------|
@@ -243,7 +243,7 @@ Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-val
 - Advanced Elicitation used for multi-perspective evaluation (or graceful degradation)
 - Document flow & coherence assessed
 - Dual audience effectiveness evaluated (humans and LLMs)
-- XiaoMa PRD principles compliance checked
+- BMAD PRD principles compliance checked
 - Overall quality rating assigned (1-5 scale)
 - Top 3 improvements identified
 - Comprehensive assessment reported to validation report
@@ -255,7 +255,7 @@ Without delay, read fully and follow: {nextStepFile} (step-v-12-completeness-val
 - Not using Advanced Elicitation for multi-perspective evaluation
 - Missing document flow assessment
 - Missing dual audience evaluation
-- Not checking all XiaoMa principles
+- Not checking all BMAD principles
 - Not assigning overall quality rating
 - Missing top 3 improvements
 - Not reporting comprehensive assessment to validation report

package/src/xmc/workflows/2-plan-workflows/create-prd/steps-v/step-v-13-report-complete.md

@@ -22,6 +22,7 @@ Finalize validation report, summarize all findings from steps 1-12, present summ
 - 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
 - 📋 YOU ARE A FACILITATOR, not a content generator
 - ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
 
 ### Role Reinforcement:
 

package/src/xmc/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md

@@ -1,13 +1,14 @@
 ---
 name: validate-prd
 description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
+standalone: false
 main_config: '{project-root}/_xiaoma/xmc/config.yaml'
 validateWorkflow: './steps-v/step-v-01-discovery.md'
 ---
 
 # PRD Validate Workflow
 
-**Goal:** Validate existing PRDs against XiaoMa standards through comprehensive review.
+**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
 
 **Your Role:** Validation Architect and Quality Assurance Specialist.
 
@@ -55,9 +56,10 @@ Load and read full config from {main_config} and resolve:
 - `date` as system-generated current datetime
 
 ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
+✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
 
 ### 2. Route to Validate Workflow
 
-"**Validate Mode: Validating an existing PRD against XiaoMa standards.**"
+"**Validate Mode: Validating an existing PRD against BMAD standards.**"
 
 Then read fully and follow: `{validateWorkflow}` (steps-v/step-v-01-discovery.md)

package/src/xmc/workflows/2-plan-workflows/xiaoma-create-ux-design/SKILL.md

@@ -0,0 +1,6 @@
+---
+name: xiaoma-create-ux-design
+description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
+---
+
+Follow the instructions in [workflow.md](workflow.md).

package/src/xmc/workflows/2-plan-workflows/xiaoma-create-ux-design/SKILL.md.bak

@@ -0,0 +1,6 @@
+---
+name: bmad-create-ux-design
+description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
+---
+
+Follow the instructions in [workflow.md](workflow.md).