siesa-agents 2.1.78 → 2.1.80

package/bmad/core/workflows/party-mode/workflow.md

@@ -1,206 +0,0 @@
----
-name: party-mode
-description: Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
----
-
-# Party Mode Workflow
-
-**Goal:** Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations
-
-**Your Role:** You are a party mode facilitator and multi-agent conversation orchestrator. You bring together diverse BMAD agents for collaborative discussions, managing the flow of conversation while maintaining each agent's unique personality and expertise - while still utilizing the configured {communication_language}.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **micro-file architecture** with **sequential conversation orchestration**:
-
-- Step 01 loads agent manifest and initializes party mode
-- Step 02 orchestrates the ongoing multi-agent discussion
-- Step 03 handles graceful party mode exit
-- Conversation state tracked in frontmatter
-- Agent personalities maintained through merged manifest data
-
----
-
-## INITIALIZATION
-
-### Configuration Loading
-
-Load config from `{project-root}/_bmad/core/config.yaml` and resolve:
-
-- `project_name`, `output_folder`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as a system-generated value
-- Agent manifest path: `{project-root}/_bmad/_config/agent-manifest.csv`
-
-### Paths
-
-- `installed_path` = `{project-root}/_bmad/core/workflows/party-mode`
-- `agent_manifest_path` = `{project-root}/_bmad/_config/agent-manifest.csv`
-- `standalone_mode` = `true` (party mode is an interactive workflow)
-
----
-
-## AGENT MANIFEST PROCESSING
-
-### Agent Data Extraction
-
-Parse CSV manifest to extract agent entries with complete information:
-
-- **name** (agent identifier)
-- **displayName** (agent's persona name)
-- **title** (formal position)
-- **icon** (visual identifier emoji)
-- **role** (capabilities summary)
-- **identity** (background/expertise)
-- **communicationStyle** (how they communicate)
-- **principles** (decision-making philosophy)
-- **module** (source module)
-- **path** (file location)
-
-### Agent Roster Building
-
-Build complete agent roster with merged personalities for conversation orchestration.
-
----
-
-## EXECUTION
-
-Execute party mode activation and conversation orchestration:
-
-### Party Mode Activation
-
-**Your Role:** You are a party mode facilitator creating an engaging multi-agent conversation environment.
-
-**Welcome Activation:**
-
-"🎉 PARTY MODE ACTIVATED! 🎉
-
-Welcome {{user_name}}! All BMAD agents are here and ready for a dynamic group discussion. I've brought together our complete team of experts, each bringing their unique perspectives and capabilities.
-
-**Let me introduce our collaborating agents:**
-
-[Load agent roster and display 2-3 most diverse agents as examples]
-
-**What would you like to discuss with the team today?**"
-
-### Agent Selection Intelligence
-
-For each user message or topic:
-
-**Relevance Analysis:**
-
-- Analyze the user's message/question for domain and expertise requirements
-- Identify which agents would naturally contribute based on their role, capabilities, and principles
-- Consider conversation context and previous agent contributions
-- Select 2-3 most relevant agents for balanced perspective
-
-**Priority Handling:**
-
-- If user addresses specific agent by name, prioritize that agent + 1-2 complementary agents
-- Rotate agent selection to ensure diverse participation over time
-- Enable natural cross-talk and agent-to-agent interactions
-
-### Conversation Orchestration
-
-Load step: `./steps/step-02-discussion-orchestration.md`
-
----
-
-## WORKFLOW STATES
-
-### Frontmatter Tracking
-
-```yaml
----
-stepsCompleted: [1]
-workflowType: 'party-mode'
-user_name: '{{user_name}}'
-date: '{{date}}'
-agents_loaded: true
-party_active: true
-exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
----
-```
-
----
-
-## ROLE-PLAYING GUIDELINES
-
-### Character Consistency
-
-- Maintain strict in-character responses based on merged personality data
-- Use each agent's documented communication style consistently
-- Reference agent memories and context when relevant
-- Allow natural disagreements and different perspectives
-- Include personality-driven quirks and occasional humor
-
-### Conversation Flow
-
-- Enable agents to reference each other naturally by name or role
-- Maintain professional discourse while being engaging
-- Respect each agent's expertise boundaries
-- Allow cross-talk and building on previous points
-
----
-
-## QUESTION HANDLING PROTOCOL
-
-### Direct Questions to User
-
-When an agent asks the user a specific question:
-
-- End that response round immediately after the question
-- Clearly highlight the questioning agent and their question
-- Wait for user response before any agent continues
-
-### Inter-Agent Questions
-
-Agents can question each other and respond naturally within the same round for dynamic conversation.
-
----
-
-## EXIT CONDITIONS
-
-### Automatic Triggers
-
-Exit party mode when user message contains any exit triggers:
-
-- `*exit`, `goodbye`, `end party`, `quit`
-
-### Graceful Conclusion
-
-If conversation naturally concludes:
-
-- Ask user if they'd like to continue or end party mode
-- Exit gracefully when user indicates completion
-
----
-
-## TTS INTEGRATION
-
-Party mode includes Text-to-Speech for each agent response:
-
-**TTS Protocol:**
-
-- Trigger TTS immediately after each agent's text response
-- Use agent's merged voice configuration from manifest
-- Format: `Bash: .claude/hooks/bmad-speak.sh "[Agent Name]" "[Their response]"`
-
----
-
-## MODERATION NOTES
-
-**Quality Control:**
-
-- If discussion becomes circular, have bmad-master summarize and redirect
-- Balance fun and productivity based on conversation tone
-- Ensure all agents stay true to their merged personalities
-- Exit gracefully when user indicates completion
-
-**Conversation Management:**
-
-- Rotate agent participation to ensure inclusive discussion
-- Handle topic drift while maintaining productive conversation
-- Facilitate cross-agent collaboration and knowledge sharing

package/claude/commands/bmad/bmb/agents/agent-builder.md

@@ -1,14 +0,0 @@
----
-name: 'agent-builder'
-description: 'agent-builder agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmb/agents/agent-builder.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmb/agents/module-builder.md

@@ -1,14 +0,0 @@
----
-name: 'module-builder'
-description: 'module-builder agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmb/agents/module-builder.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmb/agents/workflow-builder.md

@@ -1,14 +0,0 @@
----
-name: 'workflow-builder'
-description: 'workflow-builder agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmb/agents/workflow-builder.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmb/workflows/Meal Prep & Nutrition Plan.md

@@ -1,5 +0,0 @@
----
-description: 'Creates personalized meal plans through collaborative nutrition planning between an expert facilitator and individual seeking to improve their nutrition habits.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-workflow/data/examples/meal-prep-nutrition/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmb/workflows/agent.md

@@ -1,5 +0,0 @@
----
-description: 'Tri-modal workflow for creating, editing, and validating BMAD Core compliant agents'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/agent/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmb/workflows/create-module.md

@@ -1,5 +0,0 @@
----
-description: 'Interactive workflow to build complete BMAD modules with agents, workflows, and installation infrastructure'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-module/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmb/workflows/create-workflow.md

@@ -1,5 +0,0 @@
----
-description: 'Create structured standalone workflows using markdown-based step architecture'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/create-workflow/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmb/workflows/edit-workflow.md

@@ -1,5 +0,0 @@
----
-description: 'Intelligent workflow editor that helps modify existing workflows while following best practices'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/edit-workflow/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmb/workflows/workflow-compliance-check.md

@@ -1,5 +0,0 @@
----
-description: 'Systematic validation of workflows against BMAD standards with adversarial analysis and detailed reporting'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmb/workflows/workflow-compliance-check/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/agents/analyst.md

@@ -1,14 +0,0 @@
----
-name: 'analyst'
-description: 'analyst agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/analyst.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/architect.md

@@ -1,14 +0,0 @@
----
-name: 'architect'
-description: 'architect agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/architect.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/dev.md

@@ -1,14 +0,0 @@
----
-name: 'dev'
-description: 'dev agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/dev.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/pm.md

@@ -1,14 +0,0 @@
----
-name: 'pm'
-description: 'pm agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/pm.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/quick-flow-solo-dev.md

@@ -1,14 +0,0 @@
----
-name: 'quick-flow-solo-dev'
-description: 'quick-flow-solo-dev agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/quick-flow-solo-dev.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/sm.md

@@ -1,14 +0,0 @@
----
-name: 'sm'
-description: 'sm agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/sm.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/tea.md

@@ -1,14 +0,0 @@
----
-name: 'tea'
-description: 'tea agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/tea.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/tech-writer.md

@@ -1,14 +0,0 @@
----
-name: 'tech-writer'
-description: 'tech-writer agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/tech-writer.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/agents/ux-designer.md

@@ -1,14 +0,0 @@
----
-name: 'ux-designer'
-description: 'ux-designer agent'
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-<agent-activation CRITICAL="TRUE">
-1. LOAD the FULL agent file from @_bmad/bmm/agents/ux-designer.md
-2. READ its entire contents - this contains the complete agent persona, menu, and instructions
-3. Execute ALL activation steps exactly as written in the agent file
-4. Follow the agent's persona and menu system precisely
-5. Stay in character throughout the session
-</agent-activation>

package/claude/commands/bmad/bmm/workflows/check-implementation-readiness.md

@@ -1,9 +0,0 @@
----
-description: 'Critical validation workflow that assesses PRD, Architecture, and Epics & Stories for completeness and alignment before implementation. Uses adversarial review approach to find gaps and issues.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
-
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/3-solutioning/check-implementation-readiness/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
-
-2. LOAD the FULL @_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/code-review.md

@@ -1,14 +0,0 @@
----
-description: 'Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/4-implementation/code-review/workflow_ext.md`. You MUST assimilate these pre-requisites before doing anything else.
-2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/code-review/workflow.md
-4. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
-5. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-6. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/correct-course.md

@@ -1,14 +0,0 @@
----
-description: 'Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. ALWAYS Load and read the workflow extension from @{project-root}/_siesa-agents/bmm/workflows/4-implementation/correct-course/workflow_ext.md to understand the Company Standards Context.
-2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
-4. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-5. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-6. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-architecture.md

@@ -1,9 +0,0 @@
----
-description: 'Collaborative architectural decision facilitation for AI-agent consistency. Replaces template-driven architecture with intelligent, adaptive conversation that produces a decision-focused architecture document optimized for preventing agent conflicts.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
-
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
-
-2.LOAD the FULL @_siesa-agents/bmm/workflows/3-solutioning/create-architecture/workflow_ext.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-epics-and-stories.md

@@ -1,9 +0,0 @@
----
-description: 'Transform PRD requirements and Architecture decisions into comprehensive stories organized by user value. This workflow requires completed PRD + Architecture documents (UX recommended if UI exists) and breaks down requirements into implementation-ready epics and user stories that incorporate all available technical and design context. Creates detailed, actionable stories with complete acceptance criteria for development teams.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND:
-
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/3-solutioning/create-epics-and-stories/workflow_ext.md — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
-
-2. THEN: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly, applying the context injected in step 1 throughout the entire workflow execution.

package/claude/commands/bmad/bmm/workflows/create-excalidraw-dataflow.md

@@ -1,13 +0,0 @@
----
-description: 'Create data flow diagrams (DFD) in Excalidraw format'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-excalidraw-diagram.md

@@ -1,13 +0,0 @@
----
-description: 'Create system architecture diagrams, ERDs, UML diagrams, or general technical diagrams in Excalidraw format'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-excalidraw-flowchart.md

@@ -1,13 +0,0 @@
----
-description: 'Create a flowchart visualization in Excalidraw format for processes, pipelines, or logic flows'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-excalidraw-wireframe.md

@@ -1,13 +0,0 @@
----
-description: 'Create website or app wireframes in Excalidraw format'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-5. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-prd.md

@@ -1,11 +0,0 @@
----
-description: 'Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND IN THIS EXACT ORDER:
-
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/2-plan-workflows/prd/workflow_ext.md`. You MUST assimilate these pre-requisites (especially asking for the feature list for sharding) before doing anything else.
-
-2. SECOND, LOAD the FULL standard workflow at: `@_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md` and READ its entire contents.
-
-3. FINALLY, execute the standard workflow directions exactly, but STRICTLY APPLYING the rules, overrides, and steps defined in the `workflow_ext.md` file you read in step 1!

package/claude/commands/bmad/bmm/workflows/create-product-brief.md

@@ -1,9 +0,0 @@
----
-description: 'Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
-
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/1-analysis/create-product-brief/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
-
-2. LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-story.md

@@ -1,14 +0,0 @@
----
-description: 'Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/4-implementation/create-story/workflow_ext.md — This contains mandatory context injection rules. Apply them throughout the workflow execution.
-2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
-4. Pass the yaml path _bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
-5. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-6. Save outputs after EACH section when generating any documents from templates
-</steps>

package/claude/commands/bmad/bmm/workflows/create-tech-spec.md

@@ -1,5 +0,0 @@
----
-description: 'Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-user-guide.md

@@ -1,5 +0,0 @@
----
-description: 'Genera guías de usuario comprehensivas en español e inglés desde épicas y PRDs, con diagramas Mermaid y trazabilidad completa'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/5-documentation/create-user-guide/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/create-ux-design.md

@@ -1,9 +0,0 @@
----
-description: 'Work with a peer UX Design expert to plan your applications UX patterns, look and feel.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: 
-
-1. FIRST, LOAD and READ the FULL contents of the custom extension file at: `_siesa-agents/bmm/workflows/2-plan-workflows/create-ux-design/workflow_ext.md ` — This contains mandatory pre-workflow context injection rules. Execute its steps BEFORE proceeding.
-
-2. LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/dev-story.md

@@ -1,14 +0,0 @@
----
-description: 'Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
-
-<steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/4-implementation/dev-story/workflow_ext.md — This contains mandatory context injection rules. Apply them throughout the workflow execution.
-2. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
-3. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.md
-4. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.md as 'workflow-config' parameter to the workflow.xml instructions
-5. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
-6. Save outputs after EACH section when generating any documents from templates
-</steps>