@zeyue0329/xiaoma-cli 1.0.49 → 6.0.0-alpha.14

package/src/modules/xmc/workflows/workflow-status/paths/method-brownfield.yaml

@@ -0,0 +1,111 @@
+# XiaoMa Method - Brownfield
+# Full product + architecture planning for complex brownfield additions (10-50+ stories typically)
+
+method_name: "XiaoMa Method"
+track: "xiaoma-cli"
+field_type: "brownfield"
+description: "Complete product and system design for complex brownfield work"
+
+phases:
+  - prerequisite: true
+    name: "Documentation"
+    conditional: "if_undocumented"
+    note: "NOT a phase - prerequisite for brownfield without docs"
+    workflows:
+      - id: "document-project"
+        required: true
+        agent: "analyst"
+        command: "document-project"
+        output: "Comprehensive project documentation"
+        purpose: "Understand existing codebase before planning"
+
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+        note: "Uses core brainstorming workflow with project context template"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+
+      - id: "product-brief"
+        optional: true
+        agent: "analyst"
+        command: "product-brief"
+        included_by: "user_choice"
+        note: "Optional for brownfield, less common than greenfield"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "prd"
+        required: true
+        agent: "pm"
+        command: "prd"
+        output: "PRD focused on new features/changes"
+        note: "Must consider existing system constraints"
+
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
+
+      - id: "create-ux-design"
+        conditional: "if_has_ui"
+        agent: "ux-designer"
+        command: "create-ux-design"
+
+  - phase: 2
+    name: "Solutioning"
+    required: true
+    workflows:
+      - id: "create-architecture"
+        recommended: true
+        agent: "architect"
+        command: "create-architecture"
+        output: "Integration architecture - solution design for THIS project"
+        note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
+
+      - id: "create-epics-and-stories"
+        required: true
+        agent: "pm"
+        command: "create-epics-and-stories"
+        note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
+
+      - id: "test-design"
+        recommended: true
+        agent: "tea"
+        command: "test-design"
+        output: "System-level testability review"
+        note: "Testability assessment before gate check - auto-detects system-level mode"
+
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
+
+      - id: "implementation-readiness"
+        required: true
+        agent: "architect"
+        command: "implementation-readiness"
+        note: "Validates PRD + UX + Architecture + Epics cohesion before implementation"
+
+  - phase: 3
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan with stories"

package/src/modules/xmc/workflows/workflow-status/paths/method-greenfield.yaml

@@ -0,0 +1,102 @@
+# XiaoMa Method - Greenfield
+# Full product + architecture planning for greenfield projects (10-50+ stories typically)
+
+method_name: "XiaoMa Method"
+track: "xiaoma-cli"
+field_type: "greenfield"
+description: "Complete product and system design methodology for greenfield projects"
+
+phases:
+  - phase: 0
+    name: "Discovery (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
+    workflows:
+      - id: "brainstorm-project"
+        optional: true
+        agent: "analyst"
+        command: "brainstorm-project"
+        included_by: "user_choice"
+        note: "Uses core brainstorming workflow with project context template"
+
+      - id: "research"
+        optional: true
+        agent: "analyst"
+        command: "research"
+        included_by: "user_choice"
+        note: "Can have multiple research workflows"
+
+      - id: "product-brief"
+        optional: true
+        agent: "analyst"
+        command: "product-brief"
+        included_by: "user_choice"
+        note: "Recommended for greenfield Method projects"
+
+  - phase: 1
+    name: "Planning"
+    required: true
+    workflows:
+      - id: "prd"
+        required: true
+        agent: "pm"
+        command: "prd"
+        output: "Product Requirements Document with FRs and NFRs"
+
+      - id: "validate-prd"
+        optional: true
+        agent: "pm"
+        command: "validate-prd"
+        note: "Quality check for PRD completeness"
+
+      - id: "create-ux-design"
+        conditional: "if_has_ui"
+        agent: "ux-designer"
+        command: "create-ux-design"
+        note: "Determined after PRD - user/agent decides if needed"
+
+  - phase: 2
+    name: "Solutioning"
+    required: true
+    workflows:
+      - id: "create-architecture"
+        required: true
+        agent: "architect"
+        command: "create-architecture"
+        output: "System architecture document"
+        note: "Complete system design for greenfield projects"
+
+      - id: "create-epics-and-stories"
+        required: true
+        agent: "pm"
+        command: "create-epics-and-stories"
+        note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
+
+      - id: "test-design"
+        recommended: true
+        agent: "tea"
+        command: "test-design"
+        output: "System-level testability review"
+        note: "Testability assessment before gate check - auto-detects system-level mode"
+
+      - id: "validate-architecture"
+        optional: true
+        agent: "architect"
+        command: "validate-architecture"
+        note: "Quality check for architecture completeness"
+
+      - id: "implementation-readiness"
+        required: true
+        agent: "architect"
+        command: "implementation-readiness"
+        note: "Validates PRD + UX + Architecture + Epics + Testability cohesion before implementation"
+
+  - phase: 3
+    name: "Implementation"
+    required: true
+    workflows:
+      - id: "sprint-planning"
+        required: true
+        agent: "sm"
+        command: "sprint-planning"
+        note: "Creates sprint plan - subsequent work tracked there"

package/src/modules/xmc/workflows/workflow-status/project-levels.yaml

@@ -0,0 +1,59 @@
+# XMC Project Scale Levels - Source of Truth
+# Reference: /{xiaoma_folder}/xmc/README.md lines 77-85
+
+levels:
+  0:
+    name: "Level 0"
+    title: "Single Atomic Change"
+    stories: "1 story"
+    description: "Bug fix, tiny feature, one small change"
+    documentation: "Minimal - tech spec only"
+    architecture: false
+
+  1:
+    name: "Level 1"
+    title: "Small Feature"
+    stories: "1-10 stories"
+    description: "Small coherent feature, minimal documentation"
+    documentation: "Tech spec"
+    architecture: false
+
+  2:
+    name: "Level 2"
+    title: "Medium Project"
+    stories: "5-15 stories"
+    description: "Multiple features, focused PRD"
+    documentation: "PRD + optional tech spec"
+    architecture: false
+
+  3:
+    name: "Level 3"
+    title: "Complex System"
+    stories: "12-40 stories"
+    description: "Subsystems, integrations, full architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+  4:
+    name: "Level 4"
+    title: "Enterprise Scale"
+    stories: "40+ stories"
+    description: "Multiple products, enterprise architecture"
+    documentation: "PRD + architecture + JIT tech specs"
+    architecture: true
+
+# Quick detection hints for workflow-init
+detection_hints:
+  keywords:
+    level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
+    level_1: ["simple", "basic", "small feature", "add", "minor"]
+    level_2: ["dashboard", "several features", "admin panel", "medium"]
+    level_3: ["platform", "integration", "complex", "system", "architecture"]
+    level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
+
+  story_counts:
+    level_0: [1, 1]
+    level_1: [1, 10]
+    level_2: [5, 15]
+    level_3: [12, 40]
+    level_4: [40, 999]

package/src/modules/xmc/workflows/workflow-status/workflow-status-template.yaml

@@ -0,0 +1,24 @@
+# Workflow Status Template
+
+# This tracks progress through XMC methodology Analysis, Planning, and Solutioning phases.
+# Implementation phase is tracked separately in sprint-status.yaml
+
+# STATUS DEFINITIONS:
+# ==================
+# Initial Status (before completion):
+#   - required: Must be completed to progress
+#   - optional: Can be completed but not required
+#   - recommended: Strongly suggested but not required
+#   - conditional: Required only if certain conditions met (e.g., if_has_ui)
+#
+# Completion Status:
+#   - {file-path}: File created/found (e.g., "docs/product-brief.md")
+#   - skipped: Optional/conditional workflow that was skipped
+
+generated: "{{generated}}"
+project: "{{project_name}}"
+project_type: "{{project_type}}"
+selected_track: "{{selected_track}}"
+field_type: "{{field_type}}"
+workflow_path: "{{workflow_path_file}}"
+workflow_status: "{{workflow_items}}"

package/src/modules/xmc/workflows/workflow-status/workflow.yaml

@@ -0,0 +1,30 @@
+# Workflow Status - Master Router and Status Tracker
+name: workflow-status
+description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
+author: "XiaoMa"
+
+# Critical variables from config
+config_source: "{project-root}/{xiaoma_folder}/xmc/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/{xiaoma_folder}/xmc/workflows/workflow-status"
+instructions: "{installed_path}/instructions.md"
+
+# Template for status file creation (used by workflow-init)
+template: "{installed_path}/workflow-status-template.yaml"
+
+# Path definitions for project types
+path_files: "{installed_path}/paths/"
+
+# Output configuration - reads existing status
+default_output_file: "{output_folder}/xmc-workflow-status.yaml"
+
+standalone: true
+
+web_bundle: false

package/src/utility/models/agent-activation-ide.xml

@@ -0,0 +1,51 @@
+<activation critical="MANDATORY">
+  <init>
+    <step n="1">Load persona from this current file containing this activation you are reading now</step>
+    <step n="2">Override with {project-root}/{xiaoma_folder}/_cfg/agents/{agent-filename} if exists (replace, not merge)</step>
+    <step n="3">Execute critical-actions section if present in current agent XML</step>
+    <step n="4">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
+    <step n="5">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+  </init>
+  <commands critical="MANDATORY">
+    <input>Number → cmd[n] | Text → fuzzy match *commands</input>
+    <extract>exec, tmpl, data, action, validate-workflow</extract>
+    <handlers>
+      <handler type="progressive-workflow">
+        When command has: run-progressive-workflow="path/to/x.yaml" You MUST:
+        1. CRITICAL: Always LOAD {project-root}/{xiaoma_folder}/core/tasks/workflow.xml
+        2. READ its entire contents - the is the CORE OS for EXECUTING workflows
+        3. Pass the yaml path as 'workflow-config' parameter to those instructions
+        4. Follow workflow.xml instructions EXACTLY as written
+        5. Save outputs after EACH section (never batch)
+      </handler>
+      <handler type="validate-workflow">
+        When command has: validate-workflow="path/to/workflow.yaml" You MUST:
+        1. You MUST LOAD the file at: {project-root}/{xiaoma_folder}/core/tasks/validate-workflow.xml
+        2. READ its entire contents and EXECUTE all instructions in that file
+        3. Pass the workflow, and also check the workflow location for a checklist.md to pass as the checklist
+        4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+      </handler>
+      <handler type="action">
+        When command has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When command has: action="text" → Execute the text directly as a critical action prompt
+      </handler>
+      <handler type="data">
+        When command has: data="path/to/x.json|yaml|yml"
+        Load the file, parse as JSON/YAML, make available as {data} to subsequent operations
+      </handler>
+      <handler type="tmpl">
+        When command has: tmpl="path/to/x.md"
+        Load file, parse as markdown with {{mustache}} templates, make available to action/exec/workflow
+      </handler>
+      <handler type="exec">
+        When command has: exec="path"
+        Actually LOAD and EXECUTE the file at that path - do not improvise
+      </handler>
+    </handlers>
+  </commands>
+  <rules critical="MANDATORY">
+    Stay in character until *exit
+    Number all option lists, use letters for sub-options
+    Load files ONLY when executing
+  </rules>
+</activation>

package/src/utility/models/agent-activation-web.xml

@@ -0,0 +1,50 @@
+<activation critical="MANDATORY">
+  <init>
+    <step n="1">Load persona from this current agent xml block containing this activation you are reading now</step>
+    <step n="2">Show greeting + numbered list of ALL commands IN ORDER from current agent's cmds section</step>
+    <step n="3">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+  </init>
+  <bundled-files critical="MANDATORY">
+    <access-method>
+      All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
+      When you need to access a file path like "{xiaoma_folder}/core/tasks/workflow.xml":
+      1. Find the &lt;file id="{xiaoma_folder}/core/tasks/workflow.xml"&gt; element in this document
+      2. Extract the content from within the CDATA section
+      3. Use that content as if you read it from the filesystem
+    </access-method>
+    <rules>
+      <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
+      <rule>File paths starting with "{xiaoma_folder}/" or "{project-root}/{xiaoma_folder}/" refer to &lt;file id="..."&gt; elements</rule>
+      <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
+      <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
+    </rules>
+  </bundled-files>
+  <commands critical="MANDATORY">
+    <input>Number → cmd[n] | Text → fuzzy match *commands</input>
+    <extract>exec, tmpl, data, action, validate-workflow</extract>
+    <handlers>
+      <handler type="action">
+        When command has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+        When command has: action="text" → Execute the text directly as a critical action prompt
+      </handler>
+      <handler type="data">
+        When command has: data="path/to/x.json|yaml|yml"
+        Locate &lt;file id="path/to/x.json|yaml|yml"&gt; in this bundle, extract CDATA, parse as JSON/YAML, make available as {data}
+      </handler>
+      <handler type="tmpl">
+        When command has: tmpl="path/to/x.md"
+        Locate &lt;file id="path/to/x.md"&gt; in this bundle, extract CDATA, parse as markdown with {{mustache}} templates
+      </handler>
+      <handler type="exec">
+        When command has: exec="path"
+        Locate &lt;file id="path"&gt; in this bundle, extract CDATA, and EXECUTE that content
+      </handler>
+    </handlers>
+  </commands>
+  <rules critical="MANDATORY">
+    Stay in character until *exit
+    Number all option lists, use letters for sub-options
+    All file content is bundled in &lt;file&gt; elements - locate by id attribute
+    NEVER attempt filesystem operations - everything is in this XML
+  </rules>
+</activation>

package/src/utility/models/agent-command-header.md

@@ -0,0 +1 @@
+<critical>You must fully embody this agent's persona and follow all activation instructions, steps and rules exactly as specified. NEVER break character until given an exit command.</critical>

package/src/utility/models/agent-config-template.md

@@ -0,0 +1,23 @@
+```xml
+<agent-config name="" title="">
+
+    <llm critical="true">
+        <i>ALWAYS respond in {core:communication_language}.</i>
+    </llm>
+
+    <!-- Standard Agent Persona Configuration -->
+
+    <role></role>
+    <identity></identity>
+    <communication_style></communication_style>
+    <principles></principles>
+    <memories>
+        <memory>The users name is {core:user_name}</memory>
+    </memories>
+
+    <!-- User Added custom Agent Configuration Nodes -->
+
+    <!-- Agent-specific configuration nodes -->
+
+</agent-config>
+```

package/src/utility/models/agent-in-team-activation.xml

@@ -0,0 +1,3 @@
+<activation critical="MANDATORY">
+
+</activation>

package/src/utility/models/fragments/activation-rules.xml

@@ -0,0 +1,7 @@
+<rules>
+  <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
+  <!-- TTS_INJECTION:agent-tts -->
+  <r> Stay in character until exit selected</r>
+  <r> Display Menu items as the item dictates and in the order given.</r>
+  <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
+</rules>

package/src/utility/models/fragments/activation-steps.xml

@@ -0,0 +1,16 @@
+<step n="1">Load persona from this current agent file (already in context)</step>
+<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+    - Load and read {project-root}/{xiaoma_folder}/{{module}}/config.yaml NOW
+    - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+    - VERIFY: If config not loaded, STOP and report error to user
+    - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
+<step n="3">Remember: user's name is {user_name}</step>
+{AGENT_SPECIFIC_STEPS}
+<step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+    ALL menu items from menu section</step>
+<step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command
+    match</step>
+<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+    to clarify | No match → show "Not recognized"</step>
+<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+    (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

package/src/utility/models/fragments/handler-action.xml

@@ -0,0 +1,4 @@
+    <handler type="action">
+      When menu item has: action="#id" → Find prompt with id="id" in current agent XML, execute its content
+      When menu item has: action="text" → Execute the text directly as an inline instruction
+    </handler>

package/src/utility/models/fragments/handler-data.xml

@@ -0,0 +1,5 @@
+    <handler type="data">
+      When menu item has: data="path/to/file.json|yaml|yml|csv|xml"
+      Load the file first, parse according to extension
+      Make available as {data} variable to subsequent handler operations
+    </handler>

package/src/utility/models/fragments/handler-exec.xml

@@ -0,0 +1,6 @@
+<handler type="exec">
+  When menu item or handler has: exec="path/to/file.md":
+  1. Actually LOAD and read the entire file and EXECUTE the file at that path - do not improvise
+  2. Read the complete file and follow all instructions within it
+  3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
+</handler>

package/src/utility/models/fragments/handler-multi.xml

@@ -0,0 +1,14 @@
+<handler type="multi">
+  When menu item has: type="multi" with nested handlers
+  1. Display the multi item text as a single menu option
+  2. Parse all nested handlers within the multi item
+  3. For each nested handler:
+     - Use the 'match' attribute for fuzzy matching user input (or Exact Match of character code in brackets [])
+     - Execute based on handler attributes (exec, workflow, action)
+  4. When user input matches a handler's 'match' pattern:
+     - For exec="path/to/file.md": follow the `handler type="exec"` instructions
+     - For workflow="path/to/workflow.yaml": follow the `handler type="workflow"` instructions
+     - For action="...": Perform the specified action directly
+  5. Support both exact matches and fuzzy matching based on the match attribute
+  6. If no handler matches, prompt user to choose from available options
+</handler>

package/src/utility/models/fragments/handler-tmpl.xml

@@ -0,0 +1,5 @@
+    <handler type="tmpl">
+      When menu item has: tmpl="path/to/template.md"
+      Load template file, parse as markdown with {{mustache}} style variables
+      Make template content available as {template} to action/exec/workflow handlers
+    </handler>

package/src/utility/models/fragments/handler-validate-workflow.xml

@@ -0,0 +1,7 @@
+<handler type="validate-workflow">
+  When command has: validate-workflow="path/to/workflow.yaml"
+  1. You MUST LOAD the file at: {project-root}/{xiaoma_folder}/core/tasks/validate-workflow.xml
+  2. READ its entire contents and EXECUTE all instructions in that file
+  3. Pass the workflow, and also check the workflow yaml validation property to find and load the validation schema to pass as the checklist
+  4. The workflow should try to identify the file to validate based on checklist context or else you will ask the user to specify
+</handler>

package/src/utility/models/fragments/handler-workflow.xml

@@ -0,0 +1,9 @@
+<handler type="workflow">
+  When menu item has: workflow="path/to/workflow.yaml"
+  1. CRITICAL: Always LOAD {project-root}/{xiaoma_folder}/core/tasks/workflow.xml
+  2. Read the complete file - this is the CORE OS for executing XIAOMA workflows
+  3. Pass the yaml path as 'workflow-config' parameter to those instructions
+  4. Execute workflow.xml instructions precisely following all steps
+  5. Save outputs after completing EACH workflow step (never batch multiple steps together)
+  6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
+</handler>

package/src/utility/models/fragments/menu-handlers.xml

@@ -0,0 +1,6 @@
+<menu-handlers>
+  <extract>{DYNAMIC_EXTRACT_LIST}</extract>
+  <handlers>
+{DYNAMIC_HANDLERS}
+  </handlers>
+</menu-handlers>

package/src/utility/models/fragments/web-bundle-activation-steps.xml

@@ -0,0 +1,32 @@
+<step n="1">Load persona from this current agent XML block containing this activation you are reading now</step>
+{AGENT_SPECIFIC_STEPS}
+<step n="{MENU_STEP}">Show greeting + numbered list of ALL commands IN ORDER from current agent's menu section</step>
+<step n="{HALT_STEP}">CRITICAL HALT. AWAIT user input. NEVER continue without it.</step>
+<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+  to clarify | No match → show "Not recognized"</step>
+<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+  (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
+
+<bundled-files critical="MANDATORY">
+  <access-method>
+    All dependencies are bundled within this XML file as &lt;file&gt; elements with CDATA content.
+    When you need to access a file path like "{xiaoma_folder}/core/tasks/workflow.xml":
+    1. Find the &lt;file id="{xiaoma_folder}/core/tasks/workflow.xml"&gt; element in this document
+    2. Extract the content from within the CDATA section
+    3. Use that content as if you read it from the filesystem
+  </access-method>
+  <rules>
+    <rule>NEVER attempt to read files from filesystem - all files are bundled in this XML</rule>
+    <rule>File paths starting with "{xiaoma_folder}/" refer to &lt;file id="..."&gt; elements</rule>
+    <rule>When instructions reference a file path, locate the corresponding &lt;file&gt; element by matching the id attribute</rule>
+    <rule>YAML files are bundled with only their web_bundle section content (flattened to root level)</rule>
+  </rules>
+</bundled-files>
+
+<rules>
+  Stay in character until *exit
+  Number all option lists, use letters for sub-options
+  All file content is bundled in &lt;file&gt; elements - locate by id attribute
+  NEVER attempt filesystem operations - everything is in this XML
+  Menu triggers use asterisk (*) - display exactly as shown
+</rules>

package/src/utility/templates/agent.customize.template.yaml

@@ -0,0 +1,42 @@
+# Agent Customization
+# Customize any section below - all are optional
+# After editing: npx xiaoma-cli build <agent-name>
+
+# Override agent name
+agent:
+  metadata:
+    name: ""
+
+# Replace entire persona (not merged)
+persona:
+  role: ""
+  identity: ""
+  communication_style: ""
+  principles: []
+
+# Add custom critical actions (appended after standard config loading)
+critical_actions: []
+
+# Add persistent memories for the agent
+memories: []
+# Example:
+# memories:
+#   - "User prefers detailed technical explanations"
+#   - "Current project uses React and TypeScript"
+
+# Add custom menu items (appended to base menu)
+# Don't include * prefix or help/exit - auto-injected
+menu: []
+# Example:
+# menu:
+#   - trigger: my-workflow
+#     workflow: "{project-root}/custom/my.yaml"
+#     description: My custom workflow
+
+# Add custom prompts (for action="#id" handlers)
+prompts: []
+# Example:
+# prompts:
+# - id: my-prompt
+#   content: |
+#     Prompt instructions here