siesa-agents 2.1.35 → 2.1.37

package/_bmad/bmb/workflows/create-module/steps/step-01b-continue.md

@@ -0,0 +1,170 @@
+---
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+---
+
+# Step 1b: Continue Module Creation
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Module Architect and BMAD Systems Specialist
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring expertise in BMAD architecture and module creation, user brings their module requirements
+- ✅ Maintain collaborative, guiding tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on handling continuation and resuming workflow
+- 🚫 FORBIDDEN to modify existing work without user consent
+- 💬 Present status clearly and get user direction
+- 📋 Track completion status accurately
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and analyze existing module plan
+- 💾 Update frontmatter with continuation status
+- 📖 Route to appropriate next step based on progress
+- 🚫 FORBIDDEN to skip steps just because they exist
+
+## CONTEXT BOUNDARIES:
+
+- Module plan document exists with previous work
+- Focus on understanding what's been done and what remains
+- Don't assume completion without verification
+- User direction guides next actions
+
+## STEP GOAL:
+
+To resume module creation by presenting current status, understanding what's been accomplished, and determining the next step in the process.
+
+## CONTINUATION HANDLING SEQUENCE:
+
+### 1. Load and Analyze Existing Module Plan
+
+Load module plan from: {modulePlanFile}
+Read entire document including frontmatter
+Extract current status from frontmatter fields:
+
+- stepsCompleted array
+- lastStep (the final item in the stepsCompleted array)
+- module_name
+- module_code
+- date
+- inputDocuments
+
+### 2. Present Current Status
+
+"Welcome back! I found your in-progress module creation for **{module_name}**.
+
+**Current Status:**
+
+- **Module Code:** {module_code}
+- **Started:** {date}
+- **Last Step:** {lastStep}
+- **Steps Completed:** {stepsCompleted count}/{total steps}
+- **Location:** {bmb_creations_output_folder}/{module_name}
+
+Progress Summary:"
+
+Based on stepsCompleted, show:
+
+- [✅] Step 1: Init - Complete
+- [ ] Step 2: Concept - {status}
+- [ ] Step 3: Components - {status}
+- [ ] Step 4: Structure - {status}
+- [ ] Step 5: Configuration - {status}
+- [ ] Step 6: Agents - {status}
+- [ ] Step 7: Workflows - {status}
+- [ ] Step 8: Installer - {status}
+- [ ] Step 9: Documentation - {status}
+- [ ] Step 10: Roadmap - {status}
+- [ ] Step 11: Validation - {status}
+
+### 3. Review What's Been Done
+
+Read content sections of module plan
+Summarize what's been accomplished:
+
+"**Completed Work:**
+
+- Module identity defined
+- Component planning complete
+- [Other completed items based on content]"
+
+### 4. Determine Next Step
+
+Based on stepsCompleted array:
+Find highest completed step number
+Next step = highest completed + 1
+
+"**Ready to Continue:**
+Your next step would be: **Step {nextStep} - [step name]**
+
+What would you like to do?
+
+1. **Continue** from where you left off
+2. **Review** what's been done so far
+3. **Modify** previous work
+4. **Start over** with a new plan"
+
+### 5. Handle User Choice
+
+User your best judgement in how to handle the users choice
+
+### 6. Update Continuation Status
+
+Update modulePlanFile frontmatter:
+
+- Set lastStep: 'continued'
+- Add note about continuation date
+- Keep stepsCompleted unchanged
+
+## ✅ SUCCESS METRICS:
+
+- User understands current progress
+- Next step identified correctly
+- User choice handled appropriately
+- Module plan updated with continuation status
+- Workflow resumed at correct location
+
+## ❌ FAILURE MODES TO AVOID:
+
+- Not accurately reading previous status
+- Skipping steps just because they exist
+- Not offering review option
+- Losing previous work
+- Not updating continuation tracking
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Existing work properly loaded and analyzed
+- User clearly understands current status
+- Continuation options presented clearly
+- Next step determined correctly
+- Module plan updated with continuation information
+
+### ❌ SYSTEM FAILURE:
+
+- Not reading existing plan completely
+- Misrepresenting progress status
+- Losing track of what's been done
+- Not offering appropriate continuation options
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN user selects 'C' (Continue) and appropriate updates are saved to modulePlanFile, will you then load, read entire file, then execute the determined next step file to resume the module creation workflow.

package/_bmad/bmb/workflows/create-module/steps/step-02-concept.md

@@ -0,0 +1,218 @@
+---
+installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
+nextStepFile: '{installed_path}/steps/step-03-components.md'
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+moduleStructureGuide: '{project-root}/bmb/workflows/create-agent-legacy/create-module/module-structure.md'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Define Module Concept and Scope
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Module Architect and Business Analyst
+- ✅ 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 expertise in module design and BMAD patterns, user brings their domain knowledge
+- ✅ Maintain collaborative, educational tone
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on defining the module concept and scope
+- 🚫 FORBIDDEN to start designing components in this step
+- 💬 Ask questions conversationally to understand vision
+- 🚫 FORBIDDEN to proceed without clear module identity
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Load and study module structure guide for context
+- 💾 Document all module identity details in plan
+- 📖 Add "step-02-concept" to stepsCompleted array` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C'
+
+## CONTEXT BOUNDARIES:
+
+- Module name and location from step 1
+- Input documents (brief/brainstorming) if any
+- Focus ONLY on concept and scope definition
+- Don't assume module details beyond what user provides
+
+## STEP GOAL:
+
+To articulate the module's vision, define its identity, and establish clear boundaries for what it will and won't do.
+
+## MODULE CONCEPT DEFINITION PROCESS:
+
+### 1. Load Context and Briefs
+
+"Let's define your module's concept and identity. This will guide all the decisions we make about agents, workflows, and features."
+
+Load module-plan.md and check inputDocuments field
+
+Read the module brief completely
+"I see you have a module brief. Let me review that to understand your vision..."
+Use brief content to inform concept development questions
+
+Load and study the module structure guide for context
+
+### 2. Guide Concept Development
+
+Ask conversationally:
+
+"**Understanding Your Vision:**
+
+1. **What problem will this module solve?** - What pain point or need are you addressing?
+
+2. **Who is the primary user?** - Who will benefit most from this module?
+
+3. **What's the main outcome?** - What will users be able to do after using your module?
+
+4. **Why is this important?** - What makes this module valuable or unique?"
+
+### 3. Module Identity Development
+
+Based on their responses, collaboratively develop:
+
+**Module Name:**
+
+- Start with their module code: {module_name}
+- Suggest a display name in Title Case
+- Get user confirmation or refinement
+
+**Module Purpose:**
+
+- Distill their problem statement into 1-2 clear sentences
+- Focus on value and outcomes
+- Get user validation
+
+**Target Audience:**
+
+- Identify primary user persona
+- Consider skill level (beginner/intermediate/advanced)
+- Note any secondary audiences
+
+**Module Scope:**
+
+- What's IN scope (core features)
+- What's OUT of scope (explicitly state what it won't do)
+- Success criteria (how will we know it works?)
+
+### 4. Module Theme and Category
+
+"**Module Classification:**
+
+Based on your description, this seems to fit in the [Domain-Specific/Creative/Technical/Business/Personal] category.
+
+Does this sound right? Or would you categorize it differently?
+
+**Example Categories:**
+
+- **Domain-Specific**: Legal, Medical, Finance, Education
+- **Creative**: RPG/Gaming, Story Writing, Music Production
+- **Technical**: DevOps, Testing, Architecture, Security
+- **Business**: Project Management, Marketing, Sales
+- **Personal**: Journaling, Learning, Productivity"
+
+### 5. Module Type Estimation
+
+"Based on what you've described, I'm thinking this might be a:
+
+- **Simple Module** (1-2 agents, 2-3 workflows) - Focused, single-purpose
+- **Standard Module** (3-5 agents, 5-10 workflows) - Comprehensive solution
+- **Complex Module** (5+ agents, 10+ workflows) - Full platform/framework
+
+Which feels right for your vision? We'll confirm this after planning components."
+
+### 6. Document Module Concept
+
+Update module-plan.md with concept section:
+
+```markdown
+## Module Concept
+
+**Module Name:** {module_display_name}
+**Module Code:** {module_name}
+**Category:** [category]
+**Type:** [estimated type]
+
+**Purpose Statement:**
+[1-2 sentence clear purpose]
+
+**Target Audience:**
+
+- Primary: [description]
+- Secondary: [if any]
+
+**Scope Definition:**
+
+**In Scope:**
+
+- [core feature 1]
+- [core feature 2]
+- [core feature 3]
+
+**Out of Scope:**
+
+- [explicitly excluded item 1]
+- [explicitly excluded item 2]
+
+**Success Criteria:**
+
+- [measurable outcome 1]
+- [measurable outcome 2]
+- [user satisfaction indicator]
+```
+
+### 7. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask} to explore alternative concept approaches
+- IF P: Execute {partyModeWorkflow} to get creative input on module identity
+- IF C: Save concept to module-plan.md, add step-02-concept to the end of the stepsCompleted array in frontmatter, then load nextStepFile
+- IF Any other comments or queries: help user respond then redisplay menu
+
+#### 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 then end with display again of the menu options
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Module purpose clearly articulated
+- Module identity established (name, audience, scope)
+- Category and type determined
+- Concept documented in module plan
+- User feels the concept matches their vision
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding without clear module purpose
+- Not defining scope boundaries
+- Skipping user validation of concept
+- Not documenting concept details
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and module concept is saved to module-plan.md with stepsCompleted updated to [1, 2], will you then load, read entire file, then execute `{nextStepFile}` to begin component planning.

package/_bmad/bmb/workflows/create-module/steps/step-03-components.md

@@ -0,0 +1,268 @@
+---
+installed_path: '{project-root}/_bmad/bmb/workflows/create-module'
+nextStepFile: '{installed_path}/steps/step-04-structure.md'
+modulePlanFile: '{bmb_creations_output_folder}/{module_name}/module-plan-{module_name}.md'
+agent_examples_path: '{project-root}/bmb/reference/agents/module-examples'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 3: Plan Module Components
+
+## 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
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a Module Architect and Systems Designer
+- ✅ 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 expertise in BMAD component design patterns, user brings their domain requirements
+- ✅ Maintain collaborative, design-focused tone
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on planning component architecture
+- 🚫 FORBIDDEN to create actual components in this step
+- 💬 Present component options with reasoning
+- 🚫 FORBIDDEN to finalize component list without user agreement
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Reference agent examples for patterns
+- 💾 Document component plan in detail
+- 📖 Add "step-03-components" to stepsCompleted array` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C'
+
+## CONTEXT BOUNDARIES:
+
+- Module concept from step 2 is available
+- Focus on planning, not implementation
+- Consider BMAD patterns and best practices
+- Reference examples but don't copy exactly
+
+## STEP GOAL:
+
+To design the component architecture for the module, determining what agents, workflows, and tasks are needed to fulfill the module's purpose.
+
+## COMPONENT PLANNING PROCESS:
+
+### 1. Initialize Component Planning
+
+"Now that we have a clear module concept, let's plan the components that will bring it to life.
+
+Based on your module's purpose and scope, we'll design:
+
+- **Agents** - The AI personas that will help users
+- **Workflows** - The step-by-step processes for accomplishing tasks
+- **Tasks** - Quick utilities and supporting functions"
+
+### 2. Agent Planning
+
+"**Agent Architecture:**
+
+Think about the different roles or perspectives needed to accomplish your module's goals. Each agent should have a clear, distinct purpose."
+
+Reference agent examples for patterns
+Load and browse agent examples: {agent_examples_path}
+
+"**Common Agent Patterns:**
+
+- **Primary Agent** - The main interface/orchestrator
+- **Specialist Agents** - Domain-specific experts
+- **Utility Agents** - Helper/support functions
+
+**Example by Module Type:**
+
+**Technical Modules (e.g., DevOps, Testing):**
+
+- Implementation Specialist
+- Reviewer/Auditor
+- Documentation Expert
+
+**Creative Modules (e.g., Story Writing, Game Design):**
+
+- Creative Director
+- World Builder
+- Content Generator
+
+**Business Modules (e.g., Project Management):**
+
+- Project Coordinator
+- Facilitator
+- Analyst"
+
+"**For your {module_category} module, I suggest considering:**
+
+[Suggest 2-4 specific agent types based on module concept]
+
+**What resonates with your vision?** Which of these agents would be most valuable, and are there any others you'd like to add?"
+
+### 3. Workflow Planning
+
+"**Workflow Design:**
+
+Workflows are the step-by-step processes that users will follow to accomplish specific tasks. Each workflow should solve a specific problem or achieve a particular outcome."
+
+**Types of Workflows:**
+
+- **Document Workflows** - Generate reports, plans, specifications
+- **Action Workflows** - Perform operations, create structures
+- **Interactive Workflows** - Guided sessions, coaching, training
+
+**Example Workflow Patterns:**
+
+"For your module's purpose, consider these potential workflows:
+
+1. **[Primary Workflow Name]** - Main workflow for core functionality
+2. **[Supporting Workflow 1]** - For specific use case
+3. **[Supporting Workflow 2]** - For another use case
+
+Remember: We'll create workflow PLANS first, not full implementations. These plans can be used later with the create-workflow workflow."
+
+### 4. Task Planning (Optional)
+
+"**Task Planning (if needed):**
+
+Tasks are single-operation utilities that don't need full workflows. They're good for:
+
+- Quick actions
+- Shared subroutines
+- Helper functions
+
+Does your module need any tasks? For example:
+
+- Status checking
+- Quick formatting
+- Validation utilities"
+
+### 5. Component Integration Planning
+
+"**How Components Work Together:**
+
+Let's think about how your components will interact:
+
+- **Agent Collaboration**: Will agents work together or independently?
+- **Workflow Dependencies**: Do workflows need to call each other?
+- **Task Usage**: Which workflows will use which tasks?"
+
+### 6. Component Priority and MVP
+
+"**Starting Point (MVP):**
+
+To ensure success, let's identify the minimum viable set:
+
+**Must Have (Phase 1):**
+
+- [List essential agents]
+- [List essential workflows]
+
+**Nice to Have (Phase 2):**
+
+- [Additional agents]
+- [Additional workflows]
+- [Tasks if any]
+
+This approach lets you launch with core functionality and expand later."
+
+### 7. Document Component Plan
+
+Update module-plan.md with component section:
+
+```markdown
+## Component Architecture
+
+### Agents (N planned)
+
+1. **[Agent Name]** - [Brief purpose]
+   - Type: [Primary/Specialist/Utility]
+   - Role: [Specific role description]
+
+2. **[Agent Name]** - [Brief purpose]
+   - Type: [Primary/Specialist/Utility]
+   - Role: [Specific role description]
+
+### Workflows (N planned)
+
+1. **[Workflow Name]** - [Purpose]
+   - Type: [Document/Action/Interactive]
+   - Primary user: [Who uses this]
+   - Key output: [What it produces]
+
+2. **[Workflow Name]** - [Purpose]
+   - Type: [Document/Action/Interactive]
+   - Primary user: [Who uses this]
+   - Key output: [What it produces]
+
+### Tasks (N planned)
+
+1. **[Task Name]** - [Single-purpose function]
+   - Used by: [Which workflows/agents]
+
+### Component Integration
+
+- Agents collaborate via: [description]
+- Workflow dependencies: [description]
+- Task usage patterns: [description]
+
+### Development Priority
+
+**Phase 1 (MVP):**
+
+- [List of components to create first]
+
+**Phase 2 (Enhancement):**
+
+- [List of components for later]
+```
+
+### 8. Present MENU OPTIONS
+
+Display: **Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
+
+#### Menu Handling Logic:
+
+- IF A: Execute {advancedElicitationTask} to explore alternative component architectures
+- IF P: Execute {partyModeWorkflow} to get creative input on component design
+- IF C: Save component plan to module-plan.md, add step-03-components to the end of the stepsCompleted array in frontmatter, then load nextStepFile
+- IF Any other comments or queries: help user respond then redisplay menu
+
+#### 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 then end with display again of the menu options
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Component architecture planned and documented
+- Agent types and purposes clearly defined
+- Workflow requirements identified
+- Integration patterns established
+- Development priority set (MVP vs enhancements)
+
+### ❌ SYSTEM FAILURE:
+
+- Planning components without module purpose context
+- Not considering BMAD patterns and examples
+- Over-engineering (too many components)
+- Under-planning (missing essential components)
+- Not establishing development priorities
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and component plan is saved to module-plan.md with stepsCompleted updated to [1, 2, 3], will you then load, read entire file, then execute `{nextStepFile}` to begin creating the module structure.