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

package/src/modules/xmb/workflows/create-workflow/steps/step-05-memory-requirements.md

@@ -0,0 +1,136 @@
+---
+name: 'step-05-memory-requirements'
+description: 'Assess memory requirements and configure memory implementation'
+
+# Path Definitions
+workflow_path: '{project-root}/{xiaoma_folder}/xmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-memory-requirements.md'
+nextStepFile: '{project_path}/steps/step-06-external-tools.md'
+workflowFile: '{workflow_path}/workflow.md'
+workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
+
+# Documentation References
+commonToolsCsv: '{project-root}/{xiaoma_folder}/xmb/docs/workflows/common-workflow-tools.csv'
+---
+
+# Step 5: Memory Requirements Assessment
+
+## STEP GOAL:
+
+Assess whether the workflow needs memory capabilities and configure appropriate memory implementation.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a workflow architect and integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in memory implementation patterns
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Assess memory needs based on workflow requirements
+- 💾 Present memory options from CSV
+- 📖 Configure memory implementation if needed
+- 🚫 FORBIDDEN to push memory when not required
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize Memory Assessment
+
+"Assessing **Memory Requirements**
+
+Most workflows complete their task and exit without needing persistent memory. However, some specialized workflows benefit from session-to-session continuity."
+
+### 2. Present Memory Options from CSV
+
+Load `{commonToolsCsv}` and filter for `type='tool-memory'`:
+
+"**Memory Options:**
+
+**Available Memory Types:**
+
+- [List tool-memory options from CSV with descriptions]
+
+**Key Question:** Does your workflow need to maintain state across multiple sessions?"
+
+### 3. Memory Requirements Analysis
+
+"**Memory Assessment Questions:**
+
+1. **Session Continuity:** Will your workflow need to resume where it left off?
+2. **Agent Initialization:** Will your workflow initialize agents with previous context?
+3. **Pattern Recognition:** Would semantic search of past experiences be valuable?
+4. **Self-Improvement:** Will your workflow learn from previous executions?
+
+**Most workflows:** No memory needed (they complete and exit)
+**Some workflows:** Sidecar files for history tracking
+**Advanced workflows:** Vector database for semantic learning"
+
+### 4. Configure Memory (If Needed)
+
+If user selects memory:
+
+"**Memory Configuration:**
+
+Based on your needs, which memory type?
+
+1. **Sidecar File** - History tracking and session continuity
+2. **Vector Database** - Semantic search and pattern recognition
+3. **Both** - Comprehensive memory capabilities
+4. **None** - No persistent memory required
+
+**Memory Management:** Privacy controls, cleanup strategies, access patterns"
+
+### 5. Document Memory Configuration
+
+Append to {workflowPlanFile}:
+
+```markdown
+## Memory Configuration
+
+### Memory Requirements
+
+**Sidecar File:** [selected/not selected] - Use case: [specific implementation]
+**Vector Database:** [selected/not selected] - Use case: [specific implementation]
+**Memory Management:** [cleanup, privacy, access patterns]
+**Integration:** [how memory enhances workflow continuity]
+```
+
+### 6. Menu Options
+
+Display: **Select an Option:** [C] Continue to External Tools [M] Modify Memory
+
+#### Menu Handling Logic:
+
+- IF C: Append memory configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
+- IF M: Refine memory requirements
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and memory is documented will you load {nextStepFile} to configure external tools.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Memory options presented from CSV
+- User's memory needs properly assessed
+- Configuration documented appropriately
+- No memory pushed when not needed
+
+### ❌ SYSTEM FAILURE:
+
+- Assuming memory is needed without assessment
+- Duplicating CSV descriptions in step file
+- Not documenting memory management strategies

package/src/modules/xmb/workflows/create-workflow/steps/step-06-external-tools.md

@@ -0,0 +1,154 @@
+---
+name: 'step-06-external-tools'
+description: 'Configure MCP integrations and installation requirements'
+
+# Path Definitions
+workflow_path: '{project-root}/{xiaoma_folder}/xmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-external-tools.md'
+nextStepFile: '{workflow_path}/steps/step-07-installation-guidance.md'
+workflowFile: '{workflow_path}/workflow.md'
+workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
+
+# Documentation References
+commonToolsCsv: '{project-root}/{xiaoma_folder}/xmb/docs/workflows/common-workflow-tools.csv'
+---
+
+# Step 6: External Tools Configuration
+
+## STEP GOAL:
+
+Identify and configure MCP integrations and external tools that the workflow requires.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a workflow architect and integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in MCP integrations and external tools
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load external tools from CSV
+- 💾 Identify specific MCP needs for workflow
+- 📖 Document which tools require installation
+- 🚫 FORBIDDEN to proceed without confirming tool selections
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize External Tools Assessment
+
+"Configuring **External Tools and MCP Integrations**
+
+These tools extend workflow capabilities but typically require installation. Let's identify what your workflow actually needs."
+
+### 2. Present External Tools from CSV
+
+Load `{commonToolsCsv}` and filter for `propose='example'` and `type='mcp'`:
+
+"**Available External Tools:**
+
+**MCP Integrations (Require Installation):**
+
+- [List MCP tools from CSV with URLs and descriptions]
+
+**Example Workflows/Tasks:**
+
+- [List example workflows/tasks from CSV with descriptions]
+
+**Installation Note:** Tools marked with `requires_install=yes` will need setup steps."
+
+### 3. Identify Specific Tool Needs
+
+"**External Tool Requirements:**
+
+Based on your workflow goals, which external tools do you need?
+
+**Common MCP Needs:**
+
+- **Documentation Access:** Context-7 for current API docs
+- **Browser Automation:** Playwright for web interactions
+- **Git Operations:** Direct version control integration
+- **Database Access:** Multiple database connectivity
+- **Custom Tools:** Any domain-specific MCPs you need
+
+**Your Requirements:**
+
+1. What external data or APIs will your workflow access?
+2. Does your workflow need web browser automation?
+3. Will it interact with version control systems?
+4. Are database connections required?
+5. Any custom MCPs you plan to use?"
+
+### 4. Document External Tools Selection
+
+Append to {workflowPlanFile}:
+
+```markdown
+## External Tools Configuration
+
+### MCP Integrations
+
+**Selected Tools:** [list from CSV]
+**Purpose:** [how each MCP enhances workflow]
+**Integration Points:** [where external tools are essential]
+**Installation Required:** [yes/no, which tools]
+
+### Example Workflows/Tasks
+
+**Selected:** [list chosen workflows/tasks]
+**Purpose:** [how they enhance workflow capabilities]
+**Integration:** [where they fit in workflow flow]
+```
+
+### 5. Installation Assessment
+
+"**Installation Requirements Assessment:**
+
+**Tools Requiring Installation:** [list from CSV where requires_install=yes]
+
+**Installation Guidance Options:**
+
+1. Include detailed setup steps in workflow
+2. Provide user installation checklist
+3. Assume tools are pre-installed
+
+**Your Preference:** [ask user how to handle installation]"
+
+### 6. Menu Options
+
+Display: **Select an Option:** [C] Continue to Installation Guidance [M] Modify External Tools
+
+#### Menu Handling Logic:
+
+- IF C: Append external tools configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
+- IF M: Refine external tool requirements
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and external tools are documented will you load {nextStepFile} to configure installation guidance.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- External tools presented from CSV with installation requirements
+- User's specific tool needs identified and documented
+- Installation requirements clearly marked
+- User understands which tools need setup
+
+### ❌ SYSTEM FAILURE:
+
+- Not filtering CSV for relevant tool types
+- Missing installation requirement information
+- Proceeding without confirming tool selections

package/src/modules/xmb/workflows/create-workflow/steps/step-07-installation-guidance.md

@@ -0,0 +1,159 @@
+---
+name: 'step-07-installation-guidance'
+description: 'Configure installation guidance for tools that require setup'
+
+# Path Definitions
+workflow_path: '{project-root}/{xiaoma_folder}/xmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-07-installation-guidance.md'
+nextStepFile: '{workflow_path}/steps/step-08-tools-summary.md'
+workflowFile: '{workflow_path}/workflow.md'
+workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
+
+# Documentation References
+commonToolsCsv: '{project-root}/{xiaoma_folder}/xmb/docs/workflows/common-workflow-tools.csv'
+---
+
+# Step 7: Installation Guidance Configuration
+
+## STEP GOAL:
+
+Configure installation guidance for any selected tools that require setup, ensuring users can successfully prepare their environment.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a workflow architect and integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in tool installation and setup procedures
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Identify tools requiring installation from CSV
+- 💾 Configure installation approach based on user preference
+- 📖 Generate or skip installation guidance as appropriate
+- 🚫 FORBIDDEN to proceed without confirming installation approach
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize Installation Guidance
+
+"Configuring **Installation Guidance**
+
+Let's ensure users can successfully set up any tools your workflow requires. This prevents runtime errors and improves user experience."
+
+### 2. Identify Installation Requirements
+
+Load `{commonToolsCsv}` and filter for selected tools with `requires_install=yes`:
+
+"**Installation Requirements:**
+
+**Tools Requiring Installation:**
+
+- [List selected tools from CSV where requires_install=yes]
+- [Include URLs from CSV for each tool]
+
+**No Installation Required:**
+
+- [List selected tools from CSV where requires_install=no]
+- All XIAOMA core tools, LLM features, and sidecar file memory"
+
+### 3. Installation Approach Options
+
+"**Installation Guidance Options:**
+
+Based on your selected tools, how should the workflow handle installation?
+
+1. **Include Installation Steps** - Add detailed setup instructions in early workflow step
+2. **User Instructions Only** - Provide guidance but don't embed in workflow
+3. **Assume Pre-Installed** - Skip installation guidance (advanced users)
+
+**Installation Prerequisites (if included):**
+
+- Node.js 18+ (for Node.js-based MCPs)
+- Python 3.8+ (for Python-based MCPs)
+- Git for cloning repositories
+- MCP-compatible AI client (Claude Desktop or similar)"
+
+### 4. Configure Installation Guidance
+
+If user chooses installation guidance:
+
+"**Installation Step Configuration:**
+
+For each tool requiring installation, the workflow will include:
+
+- Clone/download instructions using URL from CSV
+- Dependency installation commands
+- Configuration file setup
+- Server startup procedures
+- Claude Desktop configuration steps
+
+**Installation Checklist (if included):**
+
+- [ ] Download and install Claude Desktop
+- [ ] Clone MCP repositories
+- [ ] Install required dependencies
+- [ ] Configure MCP servers
+- [ ] Add to Claude configuration
+- [ ] Test connectivity
+- [ ] Verify functionality"
+
+### 5. Document Installation Configuration
+
+Append to {workflowPlanFile}:
+
+```markdown
+## Installation Guidance Configuration
+
+### Installation Approach
+
+**Selected Approach:** [detailed steps/user instructions/assume pre-installed]
+**Tools Requiring Installation:** [list with URLs]
+**Installation Step Placement:** [early in workflow, after setup]
+
+### Installation Content
+
+**Prerequisites:** [system requirements]
+**Setup Steps:** [commands and procedures]
+**Verification:** [testing procedures]
+**User Support:** [troubleshooting guidance]
+```
+
+### 6. Menu Options
+
+Display: **Select an Option:** [C] Continue to Tools Summary [M] Modify Installation Approach
+
+#### Menu Handling Logic:
+
+- IF C: Append installation configuration to {workflowPlanFile}, update frontmatter, then load {nextStepFile}
+- IF M: Refine installation approach
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and installation guidance is documented will you load {nextStepFile} to complete tools configuration.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Installation requirements clearly identified from CSV
+- Installation approach configured based on user preference
+- Documentation prepared for setup procedures
+- User understands how tools will be installed
+
+### ❌ SYSTEM FAILURE:
+
+- Missing installation requirement assessment
+- Not using URLs from CSV for installation guidance
+- Proceeding without confirming installation approach

package/src/modules/xmb/workflows/create-workflow/steps/step-08-tools-summary.md

@@ -0,0 +1,167 @@
+---
+name: 'step-08-tools-summary'
+description: 'Summarize tools configuration and proceed to workflow design'
+
+# Path Definitions
+workflow_path: '{project-root}/{xiaoma_folder}/xmb/workflows/create-workflow'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-08-tools-summary.md'
+nextStepFile: '{workflow_path}/steps/step-09-design.md'
+workflowFile: '{workflow_path}/workflow.md'
+workflowPlanFile: '{output_folder}/workflow-plan-{new_workflow_name}.md'
+
+# Documentation References
+commonToolsCsv: '{project-root}/{xiaoma_folder}/xmb/docs/workflows/common-workflow-tools.csv'
+---
+
+# Step 8: Tools Configuration Summary
+
+## STEP GOAL:
+
+Summarize the complete tools configuration and confirm readiness to proceed to workflow design.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📋 YOU ARE A FACILITATOR, not a content generator
+
+### Role Reinforcement:
+
+- ✅ You are a workflow architect and integration specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in tools integration and workflow optimization
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Compile complete tools configuration summary
+- 💾 Present final configuration for user confirmation
+- 📖 Update workflow plan with comprehensive summary
+- 🚫 FORBIDDEN to proceed to design without user confirmation
+
+## SEQUENCE OF INSTRUCTIONS:
+
+### 1. Initialize Tools Summary
+
+"**Tools Configuration Summary**
+
+Let's review your complete tools configuration before proceeding to workflow design. This ensures all integrations are properly planned."
+
+### 2. Present Complete Configuration
+
+Load all previous configurations from {workflowPlanFile} and CSV:
+
+"**Complete Tools Configuration:**
+
+**Core XIAOMA Tools:**
+
+- [List selected core tools with integration points]
+- [Load descriptions from CSV for confirmation]
+
+**LLM Tool Features:**
+
+- [List selected LLM features with integration points]
+- [Load descriptions from CSV for confirmation]
+
+**Tool-Memory:**
+
+- [Selected memory types with implementation details]
+- [Load descriptions from CSV for confirmation]
+
+**External Tools:**
+
+- [List selected MCP integrations with URLs]
+- [Load descriptions from CSV for confirmation]
+- [Mark which require installation]
+
+**Installation Guidance:**
+
+- [Approach selected and tools included]
+- [Setup steps configured as needed]
+
+**Integration Strategy:**
+
+- [How tools enhance rather than disrupt workflow]
+- [Checkpoint approaches and user choice points]
+- [Performance optimization opportunities]"
+
+### 3. Final Configuration Confirmation
+
+"**Final Configuration Review:**
+
+**Your workflow will include:**
+
+- **Total Tools:** [count of selected tools]
+- **Core Tools:** [number selected]
+- **External Tools:** [number selected]
+- **Installation Required:** [yes/no, which tools]
+
+**Key Integration Points:**
+
+- [Major phases where tools enhance workflow]
+- [User experience considerations]
+- [Performance optimizations]
+
+**Ready to proceed with this configuration?**"
+
+### 4. Update Workflow Plan with Final Summary
+
+Append to {workflowPlanFile}:
+
+```markdown
+## Final Tools Configuration Summary
+
+### Tools Inventory
+
+**Core XIAOMA Tools:** [count and list]
+**LLM Features:** [count and list]
+**Memory Implementation:** [type and use case]
+**External Tools:** [count and list with URLs]
+**Installation Required:** [tools and setup complexity]
+
+### Integration Strategy
+
+**User Experience:** [how tools enhance workflow]
+**Checkpoint Approach:** [when tools are offered]
+**Performance Optimization:** [efficiency improvements]
+**Installation Strategy:** [how users prepare environment]
+
+### Ready for Design
+
+All tools configured and ready for workflow design phase.
+```
+
+### 5. Menu Options
+
+Display: **Select an Option:** [C] Continue to Workflow Design [M] Modify Configuration
+
+#### Menu Handling Logic:
+
+- IF C: Save final summary, update frontmatter stepsCompleted: [3, 4, 5, 6, 7, 8], then load {nextStepFile}
+- IF M: Return to specific configuration step
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and summary is saved will you load {nextStepFile} to begin workflow design phase.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Complete tools configuration summarized clearly
+- All descriptions loaded from CSV (not duplicated)
+- User confirms configuration before proceeding
+- Frontmatter updated with completed steps
+- Ready to proceed to workflow design
+
+### ❌ SYSTEM FAILURE:
+
+- Not presenting complete configuration summary
+- Duplicating CSV content instead of referencing it
+- Proceeding to design without user confirmation
+- Not updating workflow plan with final summary