siesa-agents 2.1.78 → 2.1.79

package/claude/commands/bmad/bmm/workflows/document-project.md

@@ -1,13 +0,0 @@
----
-description: 'Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development'
----
-
-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/document-project/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/document-project/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/fast-track-dev.md

@@ -1,5 +0,0 @@
----
-description: 'Automated execution of the full story development cycle (create-story → dev-story → code-review).'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/bmm/workflows/fast-track-dev/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/generate-project-context.md

@@ -1,11 +0,0 @@
----
-description: 'Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing code. Optimized for LLM context efficiency.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THESE STEPS:
-
-<steps CRITICAL="TRUE">
-1. FIRST: LOAD and READ the FULL @_siesa-agents/bmm/workflows/generate-project-context/workflow_ext.md — This contains mandatory context injection rules and an interactive menu. Apply them BEFORE proceeding.
-2. AFTER the menu choices are handled: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md
-3. READ its entire contents and follow its directions exactly, making sure to apply the output file path constraints derived from STEP 1!
-</steps>

package/claude/commands/bmad/bmm/workflows/quality-process.md

@@ -1,5 +0,0 @@
----
-description: 'QA Quality Process — Phase 1 Planning or Phase 2 Design (QA Test Plan & Strategy). Asks at startup which phase to execute.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_siesa-agents/bmm/workflows/3-solutioning/quality-process/workflow.md, READ its entire contents and follow its directions exactly!

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

@@ -1,5 +0,0 @@
----
-description: 'Flexible development - execute tech-specs OR direct instructions with optional planning.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/research.md

@@ -1,5 +0,0 @@
----
-description: 'Conduct comprehensive research across multiple domains using current web data and verified sources - Market, Technical, Domain and other research types.'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/bmm/workflows/retrospective.md

@@ -1,13 +0,0 @@
----
-description: 'Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic'
----
-
-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/4-implementation/retrospective/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/4-implementation/retrospective/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/sprint-planning.md

@@ -1,14 +0,0 @@
----
-description: 'Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle'
----
-
-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/sprint-planning/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/sprint-planning/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-planning/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/sprint-status.md

@@ -1,14 +0,0 @@
----
-description: 'Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.'
----
-
-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/sprint-status/workflow_ext.md — This contains mandatory sync rules for feature-status.yaml. 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/sprint-status/workflow.yaml
-4. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-status/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/testarch-atdd.md

@@ -1,13 +0,0 @@
----
-description: 'Generate failing acceptance tests before implementation using TDD red-green-refactor cycle'
----
-
-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/testarch/atdd/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/atdd/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/testarch-automate.md

@@ -1,13 +0,0 @@
----
-description: 'Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite'
----
-
-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/testarch/automate/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/automate/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/testarch-ci.md

@@ -1,13 +0,0 @@
----
-description: 'Scaffold CI/CD quality pipeline with test execution, burn-in loops, and artifact collection'
----
-
-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/testarch/ci/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/ci/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/testarch-framework.md

@@ -1,13 +0,0 @@
----
-description: 'Initialize production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration'
----
-
-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/testarch/framework/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/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/testarch-nfr.md

@@ -1,13 +0,0 @@
----
-description: 'Assess non-functional requirements (performance, security, reliability, maintainability) before release with evidence-based validation'
----
-
-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/testarch/nfr-assess/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/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/testarch-test-design.md

@@ -1,13 +0,0 @@
----
-description: 'Dual-mode workflow: (1) System-level testability review in Solutioning phase, or (2) Epic-level test planning in Implementation phase. Auto-detects mode based on project phase.'
----
-
-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/testarch/test-design/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/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/testarch-test-review.md

@@ -1,13 +0,0 @@
----
-description: 'Review test quality using comprehensive knowledge base and best practices validation'
----
-
-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/testarch/test-review/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/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/testarch-trace.md

@@ -1,13 +0,0 @@
----
-description: 'Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)'
----
-
-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/testarch/trace/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/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/workflow-init.md

@@ -1,14 +0,0 @@
----
-description: 'Initialize a new BMM project by determining level, type, and creating workflow path'
----
-
-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/workflow-status/Init/workflow_ext.md — This contains mandatory pre-workflow context injection rules and contains mandatory extension rules for cloning Siesa base repositories at Step 10. Hold them in memory and apply them at the end of the workflow.
-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/workflow-status/init/workflow.yaml
-4. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/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/workflow-status.md

@@ -1,13 +0,0 @@
----
-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.'
----
-
-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/workflow-status/workflow.yaml
-3. Pass the yaml path _bmad/bmm/workflows/workflow-status/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/cis/agents/brainstorming-coach.md

@@ -1,14 +0,0 @@
----
-name: 'brainstorming-coach'
-description: 'brainstorming-coach 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/cis/agents/brainstorming-coach.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/cis/agents/creative-problem-solver.md

@@ -1,14 +0,0 @@
----
-name: 'creative-problem-solver'
-description: 'creative-problem-solver 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/cis/agents/creative-problem-solver.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/cis/agents/design-thinking-coach.md

@@ -1,14 +0,0 @@
----
-name: 'design-thinking-coach'
-description: 'design-thinking-coach 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/cis/agents/design-thinking-coach.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/cis/agents/innovation-strategist.md

@@ -1,14 +0,0 @@
----
-name: 'innovation-strategist'
-description: 'innovation-strategist 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/cis/agents/innovation-strategist.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/cis/agents/presentation-master.md

@@ -1,14 +0,0 @@
----
-name: 'presentation-master'
-description: 'presentation-master 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/cis/agents/presentation-master.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/cis/agents/storyteller.md

@@ -1,14 +0,0 @@
----
-name: 'storyteller'
-description: 'storyteller 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/cis/agents/storyteller/storyteller.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/cis/workflows/design-thinking.md

@@ -1,13 +0,0 @@
----
-description: 'Guide human-centered design processes using empathy-driven methodologies. This workflow walks through the design thinking phases - Empathize, Define, Ideate, Prototype, and Test - to create solutions deeply rooted in user needs.'
----
-
-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/cis/workflows/design-thinking/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/design-thinking/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/cis/workflows/innovation-strategy.md

@@ -1,13 +0,0 @@
----
-description: 'Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.'
----
-
-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/cis/workflows/innovation-strategy/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/innovation-strategy/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/cis/workflows/problem-solving.md

@@ -1,13 +0,0 @@
----
-description: 'Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.'
----
-
-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/cis/workflows/problem-solving/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/problem-solving/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/cis/workflows/storytelling.md

@@ -1,13 +0,0 @@
----
-description: 'Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.'
----
-
-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/cis/workflows/storytelling/workflow.yaml
-3. Pass the yaml path _bmad/cis/workflows/storytelling/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/core/agents/bmad-master.md

@@ -1,14 +0,0 @@
----
-name: 'bmad-master'
-description: 'bmad-master 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/core/agents/bmad-master.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/core/tasks/index-docs.md

@@ -1,9 +0,0 @@
----
-description: 'Generates or updates an index.md of all documents in the specified directory'
----
-
-# Index Docs
-
-LOAD and execute the task at: _bmad/core/tasks/index-docs.xml
-
-Follow all instructions in the task file exactly as written.

package/claude/commands/bmad/core/workflows/brainstorming.md

@@ -1,5 +0,0 @@
----
-description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/core/workflows/party-mode.md

@@ -1,5 +0,0 @@
----
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations'
----
-
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!

package/claude/commands/bmad/core/workflows/shard-docs.md

@@ -1,10 +0,0 @@
----
-name: 'shard-doc'
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections'
----
-
-# shard-doc
-
-Read the entire task file at: {project-root}/_siesa-agents/core/tasks/shard-doc.md
-
-Follow all instructions in the task file exactly as written.

package/siesa-agents/bmm/workflows/fast-track-dev/completion-summary-fast-track-dev.md

@@ -1,76 +0,0 @@
----
-workflowName: fast-track-dev
-creationDate: 2026-03-16
-module: bmm
-status: COMPLETE
-stepsCompleted: [1, 2, 3, 4, 6, 7, 8, 9]
----
-
-# Workflow Creation Summary: fast-track-dev
-
-## Workflow Information
-
-- **Name:** fast-track-dev
-- **Module:** bmm
-- **Created:** 2026-03-16
-- **Location:** `_siesa-agents/bmm/workflows/fast-track-dev/`
-- **Python Executable:** `C:\Users\sebas\AppData\Local\Programs\Python\Python310\python.exe`
-- **Script:** `C:\labs\siesaAgentsAlpha\_siesa-agents\scripts\bmad_orchestrator.py`
-
-## Generated Files
-
-| Archivo | Propósito |
-|---|---|
-| `workflow.md` | Archivo principal del workflow — configura nombre, rol y punto de entrada |
-| `steps/step-01-init.md` | Validación de prerequisitos + detección y oferta de resume |
-| `steps/step-02-configure.md` | Menú de opciones del script + construcción del comando + confirmación |
-| `steps/step-03-execute.md` | Ejecución del script vía Bash + reporte de resultado |
-
-## Quick Start Guide
-
-### Instalación en módulo bmm
-
-1. Copiar la carpeta `fast-track-dev/` a `_bmad/bmm/workflows/fast-track-dev/`
-2. Actualizar `workflow_path` en los 3 step files apuntando a la nueva ubicación:
-   ```
-   workflow_path: '{project-root}/_bmad/bmm/workflows/fast-track-dev'
-   ```
-3. Registrar el workflow en el sistema de skills de BMAD
-
-### Invocación
-
-```
-/bmad:bmm:workflows:fast-track-dev
-```
-
-### Flujo de ejecución típico
-
-1. El workflow valida que `sprint-status.yaml` existe
-2. Detecta si hay una ejecución anterior pausada (ofrece resume si aplica)
-3. Presenta menú: procesar todo, por épica, por historia, dry-run, opciones avanzadas
-4. Construye el comando Python y pide confirmación
-5. Ejecuta el script — el orquestador toma el control
-6. Reporta éxito o error con instrucciones de acción
-
-## Scenarios de uso
-
-| Escenario | Opción a elegir |
-|---|---|
-| Procesar todo el sprint | [1] Todas las historias pendientes |
-| Procesar solo la épica 2 | [2] Por épica → `2` |
-| Procesar solo la historia 3-1 | [3] Solo una historia → `3-1` |
-| Ver qué se va a ejecutar sin correr | [5] Dry-run |
-| Retomar una ejecución interrumpida | [R] Resume (aparece automáticamente) |
-| Empezar desde el paso dev de la historia 2-3 | [4] + [6] Avanzadas |
-
-## Known Issues / Post-Install Fixes
-
-1. **workflow_path** — actualizar en los 3 step files tras instalar en ubicación final
-2. **Sub-menú avanzado** — renombrar opción `[C]` a `[S]` en step-02 para evitar confusión con `[C]` de Confirmar
-
-## Next Steps
-
-1. Instalar en `_bmad/bmm/workflows/fast-track-dev/`
-2. Actualizar `workflow_path` en los step files
-3. Ejecutar compliance check: `/bmad:bmm:workflows:workflow-compliance-check`
-4. Probar con un sprint activo (dry-run primero)