@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.3

package/src/bmb/workflows/workflow/data/architecture.md

@@ -1,150 +1,150 @@
-# Workflow Architecture
-
-**Purpose:** Core structural patterns for BMAD workflows.
-
----
-
-## Structure
-
-```
-workflow-folder/
-├── workflow.md              # Entry point, configuration
-├── steps-c/                 # Create flow steps
-│   ├── step-01-init.md
-│   ├── step-02-[name].md
-│   └── step-N-[name].md
-├── steps-e/                 # Edit flow (if needed)
-├── steps-v/                 # Validate flow (if needed)
-├── data/                    # Shared reference files
-└── templates/               # Output templates (if needed)
-```
-
----
-
-## workflow.md Standards
-
-**CRITICAL:** workflow.md MUST be lean — entry point only.
-
-**❌ PROHIBITED:**
-- Listing all steps (defeats progressive disclosure)
-- Detailed step descriptions (steps are self-documenting)
-- Validation checklists (belong in steps-v/)
-- Implementation details (belong in step files)
-
-**✅ REQUIRED:**
-- Frontmatter: name, description, web_bundle
-- Goal: What the workflow accomplishes
-- Role: Who the AI embodies
-- Meta-context: Architecture background (if pattern demo)
-- Core principles (step-file design, JIT loading, etc.)
-- Initialization/routing: How to start, which step first
-
-**Progressive Disclosure:** Users ONLY know about current step. workflow.md routes to first step, each step routes to next. No step lists in workflow.md!
-
----
-
-## Core Principles
-
-### 1. Micro-File Design
-- Each step: ~80-200 lines, focused
-- One concept per step
-- Self-contained instructions
-
-### 2. Just-In-Time Loading
-- Only current step in memory
-- Never load future steps until 'C' selected
-- Progressive disclosure = LLM focus
-
-### 3. Sequential Enforcement
-- Steps execute in order
-- No skipping, no optimization
-- Each step completes before next loads
-
-### 4. State Tracking
-For continuable workflows:
-```yaml
-stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
-lastStep: 'step-03-design'
-lastContinued: '2025-01-02'
-```
-Each step appends its name to `stepsCompleted` before loading next.
-
----
-
-## Execution Flow
-
-**Fresh Start:**
-```
-workflow.md → step-01-init.md → step-02-[name].md → ... → step-N-final.md
-```
-
-**Continuation:**
-```
-workflow.md → step-01-init.md (detects existing) → step-01b-continue.md → [next step]
-```
-
----
-
-## Frontmatter Variables
-
-### Standard
-```yaml
-workflow_path: '{project-root}/_bmad/[module]/workflows/[name]'
-thisStepFile: './step-[N]-[name].md'
-nextStepFile: './step-[N+1]-[name].md'
-outputFile: '{output_folder}/[output].md'
-```
-
-### Module-Specific
-```yaml
-bmb_creations_output_folder: '{project-root}/_bmad/bmb-creations'
-```
-
-### Rules
-- ONLY variables used in step body go in frontmatter
-- All file references use `{variable}` format
-- Paths within workflow folder are relative
-
----
-
-## Menu Pattern
-
-```markdown
-### N. Present MENU OPTIONS
-
-Display: "**Select:** [A] [action] [P] [action] [C] Continue"
-
-#### Menu Handling Logic:
-- IF A: Execute {task}, then redisplay menu
-- IF P: Execute {task}, then redisplay menu
-- IF C: Save to {outputFile}, update frontmatter, then load {nextStepFile}
-- IF Any other: help user, then redisplay menu
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input
-- ONLY proceed to next step when user selects 'C'
-```
-
-**A/P not needed in:** Step 1 (init), validation sequences, simple data gathering
-
----
-
-## Output Pattern
-
-Every step writes BEFORE loading next:
-
-1. **Plan-then-build:** Steps append to plan.md → build step consumes plan
-2. **Direct-to-final:** Steps append directly to final document
-
-See: `output-format-standards.md`
-
----
-
-## Critical Rules
-
-- 🛑 NEVER load multiple step files simultaneously
-- 📖 ALWAYS read entire step file before execution
-- 🚫 NEVER skip steps or optimize the sequence
-- 💾 ALWAYS update frontmatter when step completes
-- ⏸️ ALWAYS halt at menus and wait for input
-- 📋 NEVER create mental todos from future steps
+# Workflow Architecture
+
+**Purpose:** Core structural patterns for BMAD workflows.
+
+---
+
+## Structure
+
+```
+workflow-folder/
+├── workflow.md              # Entry point, configuration
+├── steps-c/                 # Create flow steps
+│   ├── step-01-init.md
+│   ├── step-02-[name].md
+│   └── step-N-[name].md
+├── steps-e/                 # Edit flow (if needed)
+├── steps-v/                 # Validate flow (if needed)
+├── data/                    # Shared reference files
+└── templates/               # Output templates (if needed)
+```
+
+---
+
+## workflow.md Standards
+
+**CRITICAL:** workflow.md MUST be lean — entry point only.
+
+**❌ PROHIBITED:**
+- Listing all steps (defeats progressive disclosure)
+- Detailed step descriptions (steps are self-documenting)
+- Validation checklists (belong in steps-v/)
+- Implementation details (belong in step files)
+
+**✅ REQUIRED:**
+- Frontmatter: name, description, web_bundle
+- Goal: What the workflow accomplishes
+- Role: Who the AI embodies
+- Meta-context: Architecture background (if pattern demo)
+- Core principles (step-file design, JIT loading, etc.)
+- Initialization/routing: How to start, which step first
+
+**Progressive Disclosure:** Users ONLY know about current step. workflow.md routes to first step, each step routes to next. No step lists in workflow.md!
+
+---
+
+## Core Principles
+
+### 1. Micro-File Design
+- Each step: ~80-200 lines, focused
+- One concept per step
+- Self-contained instructions
+
+### 2. Just-In-Time Loading
+- Only current step in memory
+- Never load future steps until 'C' selected
+- Progressive disclosure = LLM focus
+
+### 3. Sequential Enforcement
+- Steps execute in order
+- No skipping, no optimization
+- Each step completes before next loads
+
+### 4. State Tracking
+For continuable workflows:
+```yaml
+stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
+lastStep: 'step-03-design'
+lastContinued: '2025-01-02'
+```
+Each step appends its name to `stepsCompleted` before loading next.
+
+---
+
+## Execution Flow
+
+**Fresh Start:**
+```
+workflow.md → step-01-init.md → step-02-[name].md → ... → step-N-final.md
+```
+
+**Continuation:**
+```
+workflow.md → step-01-init.md (detects existing) → step-01b-continue.md → [next step]
+```
+
+---
+
+## Frontmatter Variables
+
+### Standard
+```yaml
+workflow_path: '{project-root}/_bmad/[module]/workflows/[name]'
+thisStepFile: './step-[N]-[name].md'
+nextStepFile: './step-[N+1]-[name].md'
+outputFile: '{output_folder}/[output].md'
+```
+
+### Module-Specific
+```yaml
+bmb_creations_output_folder: '{project-root}/_bmad/bmb-creations'
+```
+
+### Rules
+- ONLY variables used in step body go in frontmatter
+- All file references use `{variable}` format
+- Paths within workflow folder are relative
+
+---
+
+## Menu Pattern
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Select:** [A] [action] [P] [action] [C] Continue"
+
+#### Menu Handling Logic:
+- IF A: Execute {task}, then redisplay menu
+- IF P: Execute {task}, then redisplay menu
+- IF C: Save to {outputFile}, update frontmatter, then load {nextStepFile}
+- IF Any other: help user, then redisplay menu
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input
+- ONLY proceed to next step when user selects 'C'
+```
+
+**A/P not needed in:** Step 1 (init), validation sequences, simple data gathering
+
+---
+
+## Output Pattern
+
+Every step writes BEFORE loading next:
+
+1. **Plan-then-build:** Steps append to plan.md → build step consumes plan
+2. **Direct-to-final:** Steps append directly to final document
+
+See: `output-format-standards.md`
+
+---
+
+## Critical Rules
+
+- 🛑 NEVER load multiple step files simultaneously
+- 📖 ALWAYS read entire step file before execution
+- 🚫 NEVER skip steps or optimize the sequence
+- 💾 ALWAYS update frontmatter when step completes
+- ⏸️ ALWAYS halt at menus and wait for input
+- 📋 NEVER create mental todos from future steps

package/src/bmb/workflows/workflow/data/common-workflow-tools.csv

@@ -1,19 +1,19 @@
-propose,type,tool_name,description,url,requires_install
-always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
-always,workflow,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs.",{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml,no
-always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions and synthesizing concepts into actionable insights.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
-always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches and incorporate current information.",,no
-always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files.",,no
-always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents for parallel processing and modular task delegation.",,no
-always,llm-tool-feature,sub-processes,"Enables LLM to initiate and manage subprocesses for parallel processing of complex tasks.",,no
-always,tool-memory,sidecar-file,"Creates a persistent history file for session-to-session state management, enabling continuity through workflow initialization with previous context.",,no
-example,tool-memory,vector-database,"Stores and retrieves semantic information through embeddings for intelligent memory access based on meaning rather than exact matches.",https://github.com/modelcontextprotocol/servers/tree/main/src/rag-agent,yes
-example,mcp,context-7,"A curated knowledge base of API documentation and third-party tool references for integration and development tasks.",https://github.com/modelcontextprotocol/servers/tree/main/src/context-7,yes
-example,mcp,playwright,"Provides capabilities for web browser automation including navigation, form submission, and data extraction.",https://github.com/modelcontextprotocol/servers/tree/main/src/playwright,yes
-example,workflow,security-auditor,"Analyzes workflows and code for security vulnerabilities, compliance issues, and best practices violations.",,no
-example,task,code-review,"Performs systematic code analysis identifying bugs, performance issues, style violations, and architectural problems.",,no
-example,mcp,git-integration,"Enables direct Git repository operations including commits, branches, merges, and history analysis.",https://github.com/modelcontextprotocol/servers/tree/main/src/git,yes
-example,mcp,database-connector,"Provides direct database connectivity for querying, updating, and managing data across multiple database types.",https://github.com/modelcontextprotocol/servers/tree/main/src/postgres,yes
-example,task,api-testing,"Automated API endpoint testing with request/response validation and authentication handling for REST and GraphQL.",,no
-example,workflow,deployment-manager,"Orchestrates application deployment across multiple environments with rollback capabilities and health checks.",,no
-example,task,data-validator,"Validates data quality, schema compliance, and business rules through comprehensive data profiling.",,no
+propose,type,tool_name,description,url,requires_install
+always,workflow,party-mode,"Enables collaborative idea generation by managing turn-taking, summarizing contributions, and synthesizing ideas from multiple AI personas in structured conversation sessions.",{project-root}/_bmad/core/workflows/party-mode/workflow.md,no
+always,workflow,advanced-elicitation,"Employs diverse elicitation strategies such as Socratic questioning, role-playing, and counterfactual analysis to critically evaluate and enhance LLM outputs.",{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml,no
+always,task,brainstorming,"Facilitates idea generation by prompting users with targeted questions and synthesizing concepts into actionable insights.",{project-root}/_bmad/core/tasks/brainstorming.xml,no
+always,llm-tool-feature,web-browsing,"Provides LLM with capabilities to perform real-time web searches and incorporate current information.",,no
+always,llm-tool-feature,file-io,"Enables LLM to manage file operations such as creating, reading, updating, and deleting files.",,no
+always,llm-tool-feature,sub-agents,"Allows LLM to create and manage specialized sub-agents for parallel processing and modular task delegation.",,no
+always,llm-tool-feature,sub-processes,"Enables LLM to initiate and manage subprocesses for parallel processing of complex tasks.",,no
+always,tool-memory,sidecar-file,"Creates a persistent history file for session-to-session state management, enabling continuity through workflow initialization with previous context.",,no
+example,tool-memory,vector-database,"Stores and retrieves semantic information through embeddings for intelligent memory access based on meaning rather than exact matches.",https://github.com/modelcontextprotocol/servers/tree/main/src/rag-agent,yes
+example,mcp,context-7,"A curated knowledge base of API documentation and third-party tool references for integration and development tasks.",https://github.com/modelcontextprotocol/servers/tree/main/src/context-7,yes
+example,mcp,playwright,"Provides capabilities for web browser automation including navigation, form submission, and data extraction.",https://github.com/modelcontextprotocol/servers/tree/main/src/playwright,yes
+example,workflow,security-auditor,"Analyzes workflows and code for security vulnerabilities, compliance issues, and best practices violations.",,no
+example,task,code-review,"Performs systematic code analysis identifying bugs, performance issues, style violations, and architectural problems.",,no
+example,mcp,git-integration,"Enables direct Git repository operations including commits, branches, merges, and history analysis.",https://github.com/modelcontextprotocol/servers/tree/main/src/git,yes
+example,mcp,database-connector,"Provides direct database connectivity for querying, updating, and managing data across multiple database types.",https://github.com/modelcontextprotocol/servers/tree/main/src/postgres,yes
+example,task,api-testing,"Automated API endpoint testing with request/response validation and authentication handling for REST and GraphQL.",,no
+example,workflow,deployment-manager,"Orchestrates application deployment across multiple environments with rollback capabilities and health checks.",,no
+example,task,data-validator,"Validates data quality, schema compliance, and business rules through comprehensive data profiling.",,no

package/src/bmb/workflows/workflow/data/csv-data-file-standards.md

@@ -1,53 +1,53 @@
-# CSV Data File Standards
-
-## When to Use CSV
-
-Use for:
-- Domain-specific data not in training data
-- Too large for prompt context
-- Structured lookup/reference needs
-- Cross-session consistency required
-
-**Don't use for:** Web-searchable info, common syntax, general knowledge, LLM-generatable content
-
-## CSV Structure
-
-```csv
-category,name,pattern,description
-"collaboration","Think Aloud Protocol","user speaks thoughts → facilitator captures","Make thinking visible during work"
-```
-
-**Rules:**
-- Header row required, descriptive column names
-- Consistent data types per column
-- UTF-8 encoding
-- All columns must be used in workflow
-
-## Common Use Cases
-
-### Method Registry
-```csv
-category,name,pattern
-collaboration,Think Aloud,user speaks thoughts → facilitator captures
-advanced,Six Thinking Hats,view problem from 6 perspectives
-```
-
-### Knowledge Base Index
-```csv
-keywords,document_path,section
-"nutrition,macros",data/nutrition-reference.md,## Daily Targets
-```
-
-### Configuration Lookup
-```csv
-scenario,required_steps,output_sections
-"2D Platformer",step-01,step-03,step-07,movement,physics,collision
-```
-
-## Best Practices
-
-- Keep files small (<1MB preferred)
-- No unused columns
-- Use efficient encoding (codes vs full descriptions)
-- Document purpose
-- Validate data quality
+# CSV Data File Standards
+
+## When to Use CSV
+
+Use for:
+- Domain-specific data not in training data
+- Too large for prompt context
+- Structured lookup/reference needs
+- Cross-session consistency required
+
+**Don't use for:** Web-searchable info, common syntax, general knowledge, LLM-generatable content
+
+## CSV Structure
+
+```csv
+category,name,pattern,description
+"collaboration","Think Aloud Protocol","user speaks thoughts → facilitator captures","Make thinking visible during work"
+```
+
+**Rules:**
+- Header row required, descriptive column names
+- Consistent data types per column
+- UTF-8 encoding
+- All columns must be used in workflow
+
+## Common Use Cases
+
+### Method Registry
+```csv
+category,name,pattern
+collaboration,Think Aloud,user speaks thoughts → facilitator captures
+advanced,Six Thinking Hats,view problem from 6 perspectives
+```
+
+### Knowledge Base Index
+```csv
+keywords,document_path,section
+"nutrition,macros",data/nutrition-reference.md,## Daily Targets
+```
+
+### Configuration Lookup
+```csv
+scenario,required_steps,output_sections
+"2D Platformer",step-01,step-03,step-07,movement,physics,collision
+```
+
+## Best Practices
+
+- Keep files small (<1MB preferred)
+- No unused columns
+- Use efficient encoding (codes vs full descriptions)
+- Document purpose
+- Validate data quality