@zeyue0329/xiaoma-cli 1.7.0 → 1.8.0

package/src/xmc/workflows/1-analysis/xiaoma-product-brief-preview/prompts/draft-and-review.md

@@ -8,7 +8,7 @@
 
 ## Step 1: Draft the Executive Brief
 
-Use `resources/brief-template.md` as a guide — adapt structure to fit the product's story.
+Use `../resources/brief-template.md` as a guide — adapt structure to fit the product's story.
 
 **Writing principles:**
 - **Executive audience** — persuasive, clear, concise. 1-2 pages.
@@ -36,9 +36,9 @@ Before showing the draft to the user, run it through multiple review lenses in p
 
 **Launch in parallel:**
 
-1. **Skeptic Reviewer** (`agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
+1. **Skeptic Reviewer** (`../agents/skeptic-reviewer.md`) — "What's missing? What assumptions are untested? What could go wrong? Where is the brief vague or hand-wavy?"
 
-2. **Opportunity Reviewer** (`agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
+2. **Opportunity Reviewer** (`../agents/opportunity-reviewer.md`) — "What adjacent value propositions are being missed? What market angles or partnerships could strengthen this? What's underemphasized?"
 
 3. **Contextual Reviewer** — You (the main agent) pick the most useful third lens based on THIS specific product. Choose the lens that addresses the SINGLE BIGGEST RISK that the skeptic and opportunity reviewers won't naturally catch. Examples:
    - For healthtech: "Regulatory and compliance risk reviewer"
@@ -65,7 +65,7 @@ After all reviews complete:
 
 ## Step 4: Present to User
 
-**Headless mode:** Skip to `prompts/finalize.md` — no user interaction. Save the improved draft directly.
+**Headless mode:** Skip to `finalize.md` — no user interaction. Save the improved draft directly.
 
 **Yolo and Guided modes:**
 
@@ -83,4 +83,4 @@ Present reviewer findings with brief rationale, then offer: "Want me to dig into
 
 ## Stage Complete
 
-This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `prompts/finalize.md`.
+This stage is complete when: (a) the draft has been reviewed by all three lenses and improvements integrated, AND either (autonomous) save and route directly, or (guided/yolo) the user is satisfied. Route to `finalize.md`.

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

@@ -72,4 +72,4 @@ purpose: "Token-efficient context for downstream PRD creation"
 
 ## Stage Complete
 
-This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `prompts/draft-and-review.md`. Otherwise, exit.
+This is the terminal stage. After delivering the completion message and file paths, the workflow is done. If the user requests further revisions, loop back to `draft-and-review.md`. Otherwise, exit.

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

@@ -5,7 +5,7 @@
 
 **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`.
+**Skip this stage entirely in Yolo and Autonomous modes** — go directly to `draft-and-review.md`.
 
 ## Approach
 
@@ -67,4 +67,4 @@ If the user is providing complete, confident answers and you have solid coverage
 
 ## 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`.
+This stage is complete when sufficient substance exists to draft a compelling brief and the user confirms readiness. Route to `draft-and-review.md`.

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

@@ -1,6 +1,6 @@
 {
-  "module-code": "bmm",
-  "replaces-skill": "bmad-create-product-brief",
+  "module-code": "xmc",
+  "replaces-skill": "xiaoma-create-product-brief",
   "capabilities": [
     {
       "name": "create-brief",

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

@@ -1,10 +1,10 @@
-# BMAD PRD Purpose
+# XiaoMa PRD Purpose
 
-**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw BMad Method.**
+**The PRD is the top of the required funnel that feeds all subsequent product development work in rhw XiaoMa Method.**
 
 ---
 
-## What is a BMAD PRD?
+## What is a XiaoMa 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 BMAD PRD?
+## Summary: What Makes a Great XiaoMa 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 BMad 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 XiaoMa 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

@@ -61,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 BMAD PRD philosophy, standards, and validation criteria that will guide all validation checks. Internalize this understanding - it defines what makes a great BMAD PRD.
+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.
 
 ### 2. Discover PRD to Validate
 

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 BMAD format and route appropriately - classify as BMAD Standard / BMAD Variant / Non-Standard, with optional parity check for non-standard formats.
+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.
 
 ## 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 BMAD PRD Core Sections
+### 2. Check for XiaoMa PRD Core Sections
 
-Check if the PRD contains the following BMAD PRD core sections:
+Check if the PRD contains the following XiaoMa 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 BMAD PRD core sections:
 
 Based on core section count, classify:
 
-**BMAD Standard:**
+**XiaoMa Standard:**
 - 5-6 core sections present
-- Follows BMAD PRD structure closely
+- Follows XiaoMa PRD structure closely
 
-**BMAD Variant:**
+**XiaoMa Variant:**
 - 3-4 core sections present
-- Generally follows BMAD patterns but may have structural differences
-- Missing some sections but recognizable as BMAD-style
+- Generally follows XiaoMa patterns but may have structural differences
+- Missing some sections but recognizable as XiaoMa-style
 
 **Non-Standard:**
 - Fewer than 3 core sections present
-- Does not follow BMAD PRD structure
+- Does not follow XiaoMa 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]
 
-**BMAD Core Sections Present:**
+**XiaoMa 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:** [BMAD Standard / BMAD Variant / Non-Standard]
+**Format Classification:** [XiaoMa Standard / XiaoMa Variant / Non-Standard]
 **Core Sections Present:** [count]/6
 ```
 
 ### 5. Route Based on Format Classification
 
-**IF format is BMAD Standard or BMAD Variant:**
+**IF format is XiaoMa Standard or XiaoMa 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 BMAD standard structure (only {count}/6 core sections present).
+This PRD does not follow XiaoMa 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 BMAD PRD parity
+**[A] Parity Check** - Analyze gaps and estimate effort to reach XiaoMa 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
-- BMAD core sections checked systematically
+- XiaoMa core sections checked systematically
 - Format classified correctly based on section count
 - Findings reported to validation report
-- BMAD Standard/Variant PRDs proceed directly to next validation step
+- XiaoMa 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 BMAD PRD parity'
+description: 'Document Parity Check - Analyze non-standard PRD and identify gaps to achieve XiaoMa 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 BMAD PRD parity, presenting user with options for how to proceed.
+Analyze non-standard PRD and identify gaps to achieve XiaoMa 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 BMAD PRD parity, presentin
 - ✅ 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 BMAD PRD standards expertise and gap analysis
+- ✅ You bring XiaoMa 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 BMAD PRD parity, presentin
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Analyze each BMAD PRD section for gaps
+- 🎯 Analyze each XiaoMa 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 BMAD PRD parity, presentin
 
 **CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
 
-### 1. Analyze Each BMAD PRD Section
+### 1. Analyze Each XiaoMa PRD Section
 
-For each of the 6 BMAD PRD core sections, analyze:
+For each of the 6 XiaoMa 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 BMAD Standard:** [Quick/Moderate/Substantial]
+**Overall Effort to Reach XiaoMa 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 BMAD PRD sections. The overall effort to reach BMAD standard is: **{effort level}**
+Your PRD is missing {count} of 6 core XiaoMa PRD sections. The overall effort to reach XiaoMa 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 BMAD PRD sections. The overall effort to r
 
 ### ✅ SUCCESS:
 
-- All 6 BMAD PRD sections analyzed for gaps
+- All 6 XiaoMa 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 BMAD information density standards by scanning for conversational filler, wordy phrases, and redundant expressions that violate conciseness principles.
+Validate PRD meets XiaoMa 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-11-holistic-quality-validation.md

@@ -12,7 +12,7 @@ validationReportPath: '{validation_report_path}'
 
 ## STEP GOAL:
 
-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.
+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.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -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, BMAD principles
+- 🎯 Evaluate document flow, dual audience, XiaoMa principles
 - 💾 Append comprehensive assessment to validation report
 - 📖 Display "Proceeding to next check..." and load next step
 - 🚫 FORBIDDEN to pause or request user input
@@ -92,7 +92,7 @@ Invoke the `xiaoma-advanced-elicitation` skill
 - Architecture readiness: Can an LLM generate architecture from this?
 - Epic/Story readiness: Can an LLM break down into epics and stories?
 
-**3. BMAD PRD Principles Compliance:**
+**3. XiaoMa 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 BMAD principles compliance
+- Check XiaoMa 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]
 
-**BMAD Principles Compliance:**
+**XiaoMa Principles Compliance:**
 - Principles met: [count]/7
 - Principles with issues: [list]
 
@@ -181,7 +181,7 @@ Append to validation report:
 
 **Dual Audience Score:** {score}/5
 
-### BMAD PRD Principles Compliance
+### XiaoMa 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)
-- BMAD PRD principles compliance checked
+- XiaoMa 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 BMAD principles
+- Not checking all XiaoMa 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

@@ -182,7 +182,7 @@ Display:
 - **IF E (Use Edit Workflow):**
   - Explain: "The Edit workflow (steps-e/) can use this validation report to systematically address issues. Edit mode will guide you through discovering what to edit, reviewing the PRD, and applying targeted improvements."
   - Offer: "Would you like to launch Edit mode now? It will help you fix validation findings systematically."
-  - If yes: Read fully and follow: steps-e/step-e-01-discovery.md
+  - If yes: Read fully and follow: `./steps-e/step-e-01-discovery.md`
   - If no: Return to menu
 
 - **IF F (Fix Simpler Items):**

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

@@ -8,7 +8,7 @@ validateWorkflow: './steps-v/step-v-01-discovery.md'
 
 # PRD Validate Workflow
 
-**Goal:** Validate existing PRDs against BMAD standards through comprehensive review.
+**Goal:** Validate existing PRDs against XiaoMa standards through comprehensive review.
 
 **Your Role:** Validation Architect and Quality Assurance Specialist.
 
@@ -60,6 +60,6 @@ Load and read full config from {main_config} and resolve:
 
 ### 2. Route to Validate Workflow
 
-"**Validate Mode: Validating an existing PRD against BMAD standards.**"
+"**Validate Mode: Validating an existing PRD against XiaoMa 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

@@ -3,4 +3,4 @@ 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).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/2-plan-workflows/xiaoma-edit-prd/SKILL.md

@@ -3,4 +3,4 @@ name: xiaoma-edit-prd
 description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
 ---
 
-Follow the instructions in [workflow.md](workflow.md).
+Follow the instructions in ./workflow.md.

package/src/xmc/workflows/2-plan-workflows/xiaoma-edit-prd/steps-e/step-e-01-discovery.md

@@ -1,9 +1,5 @@
 ---
-name: 'step-e-01-discovery'
-description: 'Discovery & Understanding - Understand what user wants to edit and detect PRD format'
-
 # File references (ONLY variables used in this step)
-altStepFile: './step-e-01b-legacy-conversion.md'
 prdPurpose: '{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 ---
 
@@ -44,7 +40,7 @@ Understand what the user wants to edit in the PRD, detect PRD format/type, check
 - 🎯 Discover user's edit requirements
 - 🎯 Auto-detect validation reports in PRD folder (use as guide)
 - 🎯 Load validation report if provided (use as guide)
-- 🎯 Detect PRD format (BMAD/legacy)
+- 🎯 Detect PRD format (XiaoMa/legacy)
 - 🎯 Route appropriately based on format
 - 💾 Document discoveries for next step
 - 🚫 FORBIDDEN to proceed without understanding requirements
@@ -65,7 +61,7 @@ Understand what the user wants to edit in the PRD, detect PRD format/type, check
 Load and read the complete file at:
 `{prdPurpose}` (data/prd-purpose.md)
 
-This file defines what makes a great BMAD PRD. Internalize this understanding - it will guide improvement recommendations.
+This file defines what makes a great XiaoMa PRD. Internalize this understanding - it will guide improvement recommendations.
 
 ### 2. Discover PRD to Edit
 
@@ -149,7 +145,7 @@ Please describe the changes you want to make. For example:
 - Fix specific issues (information density, implementation leakage, etc.)
 - Add missing sections or content
 - Improve structure and flow
-- Convert to BMAD format (if legacy PRD)
+- Convert to XiaoMa format (if legacy PRD)
 - General improvements
 - Other changes
 
@@ -163,7 +159,7 @@ Analyze the loaded PRD:
 
 **Extract all ## Level 2 headers** from PRD
 
-**Check for BMAD PRD core sections:**
+**Check for XiaoMa PRD core sections:**
 1. Executive Summary
 2. Success Criteria
 3. Product Scope
@@ -172,13 +168,13 @@ Analyze the loaded PRD:
 6. Non-Functional Requirements
 
 **Classify format:**
-- **BMAD Standard:** 5-6 core sections present
-- **BMAD Variant:** 3-4 core sections present, generally follows BMAD patterns
-- **Legacy (Non-Standard):** Fewer than 3 core sections, does not follow BMAD structure
+- **XiaoMa Standard:** 5-6 core sections present
+- **XiaoMa Variant:** 3-4 core sections present, generally follows XiaoMa patterns
+- **Legacy (Non-Standard):** Fewer than 3 core sections, does not follow XiaoMa structure
 
 ### 8. Route Based on Format and Context
 
-**IF validation report provided OR PRD is BMAD Standard/Variant:**
+**IF validation report provided OR PRD is XiaoMa Standard/Variant:**
 
 Display: "**Edit Requirements Understood**
 
@@ -188,13 +184,13 @@ Display: "**Edit Requirements Understood**
 
 **Proceeding to deep review and analysis...**"
 
-Read fully and follow: next step (step-e-02-review.md)
+Read fully and follow: `./step-e-02-review.md`
 
 **IF PRD is Legacy (Non-Standard) AND no validation report:**
 
 Display: "**Format Detected:** Legacy PRD
 
-This PRD does not follow BMAD standard structure (only {count}/6 core sections present).
+This PRD does not follow XiaoMa standard structure (only {count}/6 core sections present).
 
 **Your edit goals:** {user's requirements}
 
@@ -204,7 +200,7 @@ Present MENU OPTIONS below for user selection
 
 ### 9. Present MENU OPTIONS (Legacy PRDs Only)
 
-**[C] Convert to BMAD Format** - Convert PRD to BMAD standard structure, then apply your edits
+**[C] Convert to XiaoMa Format** - Convert PRD to XiaoMa standard structure, then apply your edits
 **[E] Edit As-Is** - Apply your edits without converting the format
 **[X] Exit** - Exit and review conversion options
 
@@ -215,7 +211,7 @@ Present MENU OPTIONS below for user selection
 
 #### Menu Handling Logic:
 
-- IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md)
+- IF C (Convert): Read fully and follow: `./step-e-01b-legacy-conversion.md`
 - IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
 - IF X (Exit): Display summary and exit
 - IF Any other: help user, then redisplay menu
@@ -230,7 +226,7 @@ Present MENU OPTIONS below for user selection
 - Auto-detected validation reports loaded and analyzed (when found)
 - Manual validation report loaded and analyzed (if provided)
 - PRD format detected correctly
-- BMAD PRDs proceed directly to review step
+- XiaoMa PRDs proceed directly to review step
 - Legacy PRDs pause and present conversion options
 - User can choose conversion path or edit as-is
 

package/src/xmc/workflows/2-plan-workflows/xiaoma-edit-prd/steps-e/step-e-01b-legacy-conversion.md

@@ -1,9 +1,5 @@
 ---
-name: 'step-e-01b-legacy-conversion'
-description: 'Legacy PRD Conversion Assessment - Analyze legacy PRD and propose conversion strategy'
-
 # File references (ONLY variables used in this step)
-nextStepFile: './step-e-02-review.md'
 prdFile: '{prd_file_path}'
 prdPurpose: '{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
 ---
@@ -12,7 +8,7 @@ prdPurpose: '{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-prd/da
 
 ## STEP GOAL:
 
-Analyze legacy PRD against BMAD standards, identify gaps, propose conversion strategy, and let user choose how to proceed.
+Analyze legacy PRD against XiaoMa standards, identify gaps, propose conversion strategy, and let user choose how to proceed.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -29,7 +25,7 @@ Analyze legacy PRD against BMAD standards, identify gaps, propose conversion str
 - ✅ You are a Validation Architect and PRD Improvement 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 BMAD standards expertise and conversion guidance
+- ✅ You bring XiaoMa standards expertise and conversion guidance
 - ✅ User brings domain knowledge and edit requirements
 
 ### Step-Specific Rules:
@@ -41,7 +37,7 @@ Analyze legacy PRD against BMAD standards, identify gaps, propose conversion str
 
 ## EXECUTION PROTOCOLS:
 
-- 🎯 Analyze legacy PRD against BMAD standard
+- 🎯 Analyze legacy PRD against XiaoMa standard
 - 💾 Identify gaps and estimate conversion effort
 - 📖 Present conversion options with effort estimates
 - 🚫 FORBIDDEN to proceed without user selection
@@ -65,7 +61,7 @@ Analyze legacy PRD against BMAD standards, identify gaps, propose conversion str
 
 **Load the PRD and prd-purpose.md**
 
-**For each BMAD PRD section, analyze:**
+**For each XiaoMa PRD section, analyze:**
 1. Does PRD have this section? (Executive Summary, Success Criteria, Product Scope, User Journeys, Functional Requirements, Non-Functional Requirements)
 2. If present: Is it complete and well-structured?
 3. If missing: What content exists that could migrate to this section?
@@ -80,14 +76,14 @@ Analyze legacy PRD against BMAD standards, identify gaps, propose conversion str
 Return conversion assessment with gap analysis and effort estimate."
 
 **Graceful degradation (if no Task tool):**
-- Manually check PRD for each BMAD section
+- Manually check PRD for each XiaoMa section
 - Note what's present and what's missing
 - Estimate conversion effort
 - Identify best conversion approach
 
 ### 2. Build Gap Analysis
 
-**For each BMAD core section:**
+**For each XiaoMa core section:**
 
 **Executive Summary:**
 - Present: [Yes/No/Partial]
@@ -150,7 +146,7 @@ Display:
 
 ### 4. Present MENU OPTIONS
 
-**[R] Restructure to BMAD** - Full conversion to BMAD format, then apply your edits
+**[R] Restructure to XiaoMa** - Full conversion to XiaoMa format, then apply your edits
 **[I] Targeted Improvements** - Apply your edits to existing structure without restructuring
 **[E] Edit & Restructure** - Do both: convert format AND apply your edits
 **[X] Exit** - Review assessment and decide
@@ -182,7 +178,7 @@ Edit goals: {summary}
 
 **Proceeding to deep review...**"
 
-Read fully and follow: {nextStepFile} (step-e-02-review.md)
+Read fully and follow: `./step-e-02-review.md`
 
 ---
 
@@ -190,7 +186,7 @@ Read fully and follow: {nextStepFile} (step-e-02-review.md)
 
 ### ✅ SUCCESS:
 
-- All 6 BMAD core sections analyzed for gaps
+- All 6 XiaoMa core sections analyzed for gaps
 - Effort estimates provided for each section
 - Overall conversion effort assessed correctly
 - Clear recommendation provided based on effort and user goals

package/src/xmc/workflows/2-plan-workflows/xiaoma-edit-prd/steps-e/step-e-02-review.md

@@ -1,9 +1,5 @@
 ---
-name: 'step-e-02-review'
-description: 'Deep Review & Analysis - Thoroughly review existing PRD and prepare detailed change plan'
-
 # File references (ONLY variables used in this step)
-nextStepFile: './step-e-03-edit.md'
 prdFile: '{prd_file_path}'
 validationReport: '{validation_report_path}'  # If provided
 prdPurpose: '{project-root}/_xiaoma/xmc/workflows/2-plan-workflows/create-prd/data/prd-purpose.md'
@@ -69,7 +65,7 @@ Thoroughly review the existing PRD, analyze validation report findings (if provi
 
 **Context from step e-01:**
 - User's edit requirements: {user_requirements}
-- PRD format: {BMAD/legacy}
+- PRD format: {XiaoMa/legacy}
 - Validation report provided: {yes/no}
 - Conversion mode: {restructure/targeted/both} (if legacy)
 
@@ -82,7 +78,7 @@ Thoroughly review the existing PRD, analyze validation report findings (if provi
 
 **IF no validation report:**
 1. Read entire PRD thoroughly
-2. Analyze against BMAD standards (from prd-purpose.md)
+2. Analyze against XiaoMa standards (from prd-purpose.md)
 3. Identify issues in:
    - Information density (anti-patterns)
    - Structure and flow
@@ -204,7 +200,7 @@ Display: "**Change Plan Approved**
 
 **Proceeding to edit step...**"
 
-Read fully and follow: {nextStepFile} (step-e-03-edit.md)
+Read fully and follow: `./step-e-03-edit.md`
 
 ### 7. Present MENU OPTIONS (If User Wants Discussion)
 
@@ -221,7 +217,7 @@ Read fully and follow: {nextStepFile} (step-e-03-edit.md)
 
 - IF A: Invoke the `xiaoma-advanced-elicitation` skill, then return to discussion
 - IF P: Invoke the `xiaoma-party-mode` skill, then return to discussion
-- IF C: Document approval, then load {nextStepFile}
+- IF C: Document approval, then load step-e-03-edit.md
 - IF Any other: discuss, then redisplay menu
 
 ---