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

package/src/modules/xmb/workflows/create-workflow/templates/requirements-section.md

@@ -0,0 +1,47 @@
+## Requirements Summary
+
+### Workflow Purpose
+
+- **Problem to Solve**: {{problemStatement}}
+- **Primary Users**: {{targetUsers}}
+- **Main Outcome**: {{primaryOutcome}}
+- **Usage Frequency**: {{usageFrequency}}
+
+### Workflow Classification
+
+- **Type**: {{workflowType}}
+- **Flow Pattern**: {{flowPattern}}
+- **Interaction Style**: {{interactionStyle}}
+- **Instruction Style**: {{instructionStyle}}
+- **Autonomy Level**: {{autonomyLevel}}
+
+### Input Requirements
+
+- **Required Inputs**: {{requiredInputs}}
+- **Optional Inputs**: {{optionalInputs}}
+- **Prerequisites**: {{prerequisites}}
+
+### Output Specifications
+
+- **Primary Output**: {{primaryOutput}}
+- **Intermediate Outputs**: {{intermediateOutputs}}
+- **Output Format**: {{outputFormat}}
+
+### Technical Constraints
+
+- **Dependencies**: {{dependencies}}
+- **Integrations**: {{integrations}}
+- **Performance Requirements**: {{performanceRequirements}}
+
+### Target Location
+
+- **Module**: {{targetModule}}
+- **Folder Name**: {{workflowFolderName}}
+- **Target Path**: {{targetWorkflowPath}}
+- **Custom Workflow Location**: {{customWorkflowLocation}}
+
+### Success Criteria
+
+- **Quality Metrics**: {{qualityMetrics}}
+- **Success Indicators**: {{successIndicators}}
+- **User Satisfaction**: {{userSatisfactionCriteria}}

package/src/modules/xmb/workflows/create-workflow/templates/review-section.md

@@ -0,0 +1,56 @@
+## Workflow Review Results
+
+### File Structure Review
+
+**Status**: {{fileStructureStatus}}
+
+- Required Files: {{requiredFilesStatus}}
+- Directory Structure: {{directoryStructureStatus}}
+- Naming Conventions: {{namingConventionsStatus}}
+
+### Configuration Validation
+
+**Status**: {{configValidationStatus}}
+
+- Metadata Completeness: {{metadataStatus}}
+- Path Variables: {{pathVariablesStatus}}
+- Dependencies: {{dependenciesStatus}}
+
+### Step File Compliance
+
+**Status**: {{stepComplianceStatus}}
+
+- Template Structure: {{templateStructureStatus}}
+- Mandatory Rules: {{mandatoryRulesStatus}}
+- Menu Implementation: {{menuImplementationStatus}}
+
+### Cross-File Consistency
+
+**Status**: {{consistencyStatus}}
+
+- Variable Naming: {{variableNamingStatus}}
+- Path References: {{pathReferencesStatus}}
+- Step Sequence: {{stepSequenceStatus}}
+
+### Requirements Verification
+
+**Status**: {{requirementsVerificationStatus}}
+
+- Problem Addressed: {{problemAddressedStatus}}
+- User Types Supported: {{userTypesStatus}}
+- Inputs/Outputs: {{inputsOutputsStatus}}
+
+### Best Practices Adherence
+
+**Status**: {{bestPracticesStatus}}
+
+- File Size Limits: {{fileSizeStatus}}
+- Collaborative Dialogue: {{collaborativeDialogueStatus}}
+- Error Handling: {{errorHandlingStatus}}
+
+### Issues Found
+
+{{#issues}}
+
+- **{{severity}}**: {{description}}
+  {{/issues}}

package/src/modules/xmb/workflows/create-workflow/templates/step-file.md

@@ -0,0 +1,139 @@
+---
+name: "step-{{stepNumber}}-{{stepName}}"
+description: "{{stepDescription}}"
+
+# Path Definitions
+workflow_path: "{project-root}/{xiaoma_folder}/{{targetModule}}/workflows/{{workflowName}}"
+
+# File References
+thisStepFile: "{workflow_path}/steps/step-{{stepNumber}}-{{stepName}}.md"
+{{#hasNextStep}}
+nextStepFile: "{workflow_path}/steps/step-{{nextStepNumber}}-{{nextStepName}}.md"
+{{/hasNextStep}}
+workflowFile: "{workflow_path}/workflow.md"
+{{#hasOutput}}
+outputFile: "{output_folder}/{{outputFileName}}-{project_name}.md"
+{{/hasOutput}}
+
+# Task References
+advancedElicitationTask: "{project-root}/{xiaoma_folder}/core/tasks/advanced-elicitation.xml"
+partyModeWorkflow: "{project-root}/{xiaoma_folder}/core/workflows/party-mode/workflow.md"
+
+{{#hasTemplates}}
+# Template References
+{{#templates}}
+{{name}}: "{workflow_path}/templates/{{file}}"
+{{/templates}}
+{{/hasTemplates}}
+---
+
+# Step {{stepNumber}}: {{stepTitle}}
+
+## STEP GOAL:
+
+{{stepGoal}}
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a {{aiRole}}
+- ✅ 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 {{aiExpertise}}, user brings {{userExpertise}}
+- ✅ Maintain collaborative {{collaborationStyle}} tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on {{stepFocus}}
+- 🚫 FORBIDDEN to {{forbiddenAction}}
+- 💬 Approach: {{stepApproach}}
+- 📋 {{additionalRule}}
+
+## EXECUTION PROTOCOLS:
+
+{{#executionProtocols}}
+
+- 🎯 {{.}}
+  {{/executionProtocols}}
+
+## CONTEXT BOUNDARIES:
+
+- Available context: {{availableContext}}
+- Focus: {{contextFocus}}
+- Limits: {{contextLimits}}
+- Dependencies: {{contextDependencies}}
+
+## SEQUENCE OF INSTRUCTIONS (Do not deviate, skip, or optimize)
+
+{{#instructions}}
+
+### {{number}}. {{title}}
+
+{{content}}
+
+{{#hasContentToAppend}}
+
+#### Content to Append (if applicable):
+
+```markdown
+{{contentToAppend}}
+```
+
+{{/hasContentToAppend}}
+
+{{/instructions}}
+
+{{#hasMenu}}
+
+### {{menuNumber}}. Present MENU OPTIONS
+
+Display: **{{menuDisplay}}**
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+- Use menu handling logic section below
+
+#### Menu Handling Logic:
+
+{{#menuOptions}}
+
+- IF {{key}}: {{action}}
+  {{/menuOptions}}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#{{menuNumber}}-present-menu-options)
+  {{/hasMenu}}
+
+## CRITICAL STEP COMPLETION NOTE
+
+{{completionNote}}
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+{{#successCriteria}}
+
+- {{.}}
+  {{/successCriteria}}
+
+### ❌ SYSTEM FAILURE:
+
+{{#failureModes}}
+
+- {{.}}
+  {{/failureModes}}
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/xmb/workflows/create-workflow/templates/workflow-plan.md

@@ -0,0 +1,54 @@
+# Workflow Creation Plan: {{workflowName}}
+
+**Created:** {{date}}
+**Author:** {{user_name}}
+**Module:** {{targetModule}}
+**Type:** {{workflowType}}
+
+## Executive Summary
+
+{{executiveSummary}}
+
+## Requirements Analysis
+
+[Requirements will be appended here from step 2]
+
+## Detailed Design
+
+[Design details will be appended here from step 3]
+
+## Implementation Plan
+
+[Implementation plan will be appended here from step 4]
+
+## Review and Validation
+
+[Review results will be appended here from step 5]
+
+---
+
+## Final Configuration
+
+### Output Files to Generate
+
+{{#outputFiles}}
+
+- {{type}}: {{path}}
+  {{/outputFiles}}
+
+### Target Location
+
+- **Folder**: {{targetWorkflowPath}}
+- **Module**: {{targetModule}}
+- **Custom Location**: {{customWorkflowLocation}}
+
+### Final Checklist
+
+- [ ] All requirements documented
+- [ ] Workflow designed and approved
+- [ ] Files generated successfully
+- [ ] Workflow tested and validated
+
+## Ready for Implementation
+
+When you approve this plan, I'll generate all the workflow files in the specified location with the exact structure and content outlined above.

package/src/modules/xmb/workflows/create-workflow/templates/workflow.md

@@ -0,0 +1,58 @@
+---
+name: { { workflowDisplayName } }
+description: { { workflowDescription } }
+web_bundle: { { webBundleFlag } }
+---
+
+# {{workflowDisplayName}}
+
+**Goal:** {{workflowGoal}}
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a {{aiRole}} collaborating with {{userType}}. This is a partnership, not a client-vendor relationship. You bring {{aiExpertise}}, while the user brings {{userExpertise}}. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/{xiaoma_folder}/{{targetModule}}/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.

package/src/modules/xmb/workflows/create-workflow/workflow.md

@@ -0,0 +1,58 @@
+---
+name: Create Workflow
+description: Create structured standalone workflows using markdown-based step architecture
+web_bundle: true
+---
+
+# Create Workflow
+
+**Goal:** Create structured, repeatable standalone workflows through collaborative conversation and step-by-step guidance.
+
+**Your Role:** In addition to your name, communication_style, and persona, you are also a workflow architect and systems designer collaborating with a workflow creator. This is a partnership, not a client-vendor relationship. You bring expertise in workflow design patterns, step architecture, and collaborative facilitation, while the user brings their domain knowledge and specific workflow requirements. Work together as equals.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/{xiaoma_folder}/xmb/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `custom_workflow_location`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.

package/src/modules/xmb/workflows/edit-agent/steps/step-01-discover-intent.md

@@ -0,0 +1,134 @@
+---
+name: 'step-01-discover-intent'
+description: 'Get agent path and user editing goals'
+
+# Path Definitions
+workflow_path: '{project-root}/src/modules/xmb/workflows/edit-agent'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-discover-intent.md'
+nextStepFile: '{workflow_path}/steps/step-02-analyze-agent.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/.xiaoma/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/.xiaoma/core/workflows/party-mode/workflow.md'
+---
+
+# Step 1: Discover Edit Intent
+
+## STEP GOAL:
+
+Get the agent path to edit and understand what the user wants to accomplish before proceeding to targeted analysis.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are an agent editor who helps users improve their XIAOMA agents
+- ✅ If you already have a name, communication_style and identity, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring agent architecture expertise, user brings their agent and goals, together we improve the agent
+- ✅ Maintain collaborative guiding tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on getting agent path and understanding user goals
+- 🚫 FORBIDDEN to load any documentation or analyze the agent yet
+- 💬 Approach: Direct questions to understand what needs fixing
+- 🚫 FORBIDDEN to make suggestions or propose solutions
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask clear questions to get agent path and user goals
+- 💾 Store path and goals for next step
+- 📖 Do NOT load any references in this step
+- 🚫 FORBIDDEN to analyze agent content yet
+
+## CONTEXT BOUNDARIES:
+
+- Available context: User wants to edit an existing agent
+- Focus: Get path and understand goals ONLY
+- Limits: No analysis, no documentation loading, no suggestions
+- Dependencies: User must provide agent path
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Get Agent Path
+
+Ask the user:
+"What agent do you want to edit? Please provide the path to:
+
+- A .agent.yaml file (Simple agent)
+- A folder containing .agent.yaml (Expert agent with sidecar files)"
+
+Wait for user response with the path.
+
+### 2. Understand Editing Goals
+
+Ask clear questions to understand what they want to accomplish:
+"What do you want to change about this agent?"
+
+Listen for specific goals such as:
+
+- Fix broken functionality
+- Update personality/communication style
+- Add or remove commands
+- Fix references or paths
+- Reorganize sidecar files (Expert agents)
+- Update for new standards
+
+Continue asking clarifying questions until goals are clear.
+
+### 3. Confirm Understanding
+
+Summarize back to user:
+"So you want to edit the agent at {{agent_path}} to {{user_goals}}. Is that correct?"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then redisplay menu options
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution, return to this menu
+- User can chat or ask questions - always respond and then end with display again of the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [C continue option] is selected and [agent path and goals obtained], will you then load and read fully `{nextStepFile}` to execute and begin agent analysis.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Agent path clearly obtained and validated
+- User editing goals understood completely
+- User confirms understanding is correct
+- Menu presented and user input handled correctly
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without agent path
+- Making suggestions or analyzing agent
+- Loading documentation in this step
+- Not confirming user goals clearly
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.