@devo-bmad-custom/agent-orchestration 1.0.0

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

@@ -0,0 +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

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

@@ -0,0 +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

package/src/bmb/workflows/workflow/data/frontmatter-standards.md

@@ -0,0 +1,184 @@
+# Frontmatter Standards
+
+**Purpose:** Variables, paths, and frontmatter rules for workflow steps.
+
+---
+
+## Golden Rules
+
+1. **Only variables USED in the step** may be in frontmatter
+2. **All file references MUST use `{variable}` format** - no hardcoded paths
+3. **Paths within workflow folder MUST be relative** - NO `workflow_path` variable allowed
+
+---
+
+## Standard Variables
+
+| Variable | Example |
+|----------|---------|
+| `{project-root}` | `/Users/user/dev/BMAD-METHOD` <!-- validate-file-refs:ignore --> |
+| `{project_name}` | `my-project` |
+| `{output_folder}` | `/Users/user/dev/BMAD-METHOD/output` <!-- validate-file-refs:ignore --> |
+| `{user_name}` | `Brian` |
+| `{communication_language}` | `english` |
+| `{document_output_language}` | `english` |
+
+---
+
+## Module-Specific Variables
+
+Workflows in a MODULE can access additional variables from its `module.yaml`.
+
+**Example:**
+```yaml
+bmb_creations_output_folder: '{project-root}/_bmad/bmb-creations'
+```
+
+**Standalone workflows:** Only have access to standard variables.
+
+---
+
+## Frontmatter Structure
+
+### Required Fields
+```yaml
+---
+name: 'step-[N]-[name]'
+description: '[what this step does]'
+---
+```
+
+### File References - ONLY variables used in this step
+```yaml
+---
+# Step to step (SAME folder) - use ./filename.md
+nextStepFile: './step-02-vision.md'
+
+# Step to template (PARENT folder) - use ../filename.md
+productBriefTemplate: '../product-brief.template.md'
+
+# Step to data (SUBFOLDER) - use ./data/filename.md
+someData: './data/config.csv'
+
+# Output files - use variable
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+# External references - use {project-root}
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+---
+```
+
+---
+
+## Critical Rule: Unused Variables Forbidden
+
+**Detection Rule:** For EVERY variable in frontmatter, search the step body for `{variableName}`. If not found, it's a violation.
+
+### ❌ VIOLATION
+```yaml
+---
+outputFile: '{output_folder}/output.md'
+thisStepFile: './step-01-init.md'      # ❌ NEVER USED
+workflowFile: './workflow.md'           # ❌ NEVER USED
+---
+```
+
+### ✅ CORRECT
+```yaml
+---
+outputFile: '{output_folder}/output.md'
+nextStepFile: './step-02-foo.md'
+---
+```
+
+---
+
+## Path Rules
+
+| Type | Format | Example |
+|------|--------|---------|
+| Step to Step (same folder) | `./filename.md` | `./step-02-vision.md` |
+| Step to Template (parent) | `../filename.md` | `../template.md` |
+| Step to Subfolder | `./subfolder/file.md` | `./data/config.csv` |
+| External References | `{project-root}/...` | `{project-root}/_bmad/core/workflows/...` |
+| Output Files | `{folder_variable}/...` | `{planning_artifacts}/output.md` |
+
+---
+
+## ❌ FORBIDDEN Patterns
+
+| Pattern | Why |
+|---------|-----|
+| `workflow_path: '{project-root}/...'` | Use relative paths |
+| `thisStepFile: './step-XX.md'` | Remove unless referenced <!-- validate-file-refs:ignore --> |
+| `workflowFile: './workflow.md'` | Remove unless referenced <!-- validate-file-refs:ignore --> |
+| `{workflow_path}/templates/...` | Use `../template.md` |
+| `{workflow_path}/data/...` | Use `./data/file.md` |
+
+---
+
+## Variable Naming
+
+Use `snake_case` with descriptive prefixes:
+
+| Suffix | Usage | Example |
+|--------|-------|---------|
+| `*_File` | File references | `outputFile`, `nextStepFile` |
+| `*_Task` | Task references | `advancedElicitationTask` |
+| `*_Workflow` | Workflow references | `partyModeWorkflow` |
+| `*_Template` | Templates | `productBriefTemplate` |
+| `*_Data` | Data files | `dietaryData` |
+
+---
+
+## Defining New Variables
+
+Steps can define NEW variables for future steps.
+
+**Step 01 defines:**
+```yaml
+---
+targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{workflow_name}'
+---
+```
+
+**Step 02 uses:**
+```yaml
+---
+targetWorkflowPath: '{bmb_creations_output_folder}/workflows/{workflow_name}'
+workflowPlanFile: '{targetWorkflowPath}/plan.md'
+---
+```
+
+---
+
+## Continuable Workflow Frontmatter
+
+```yaml
+---
+stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
+lastStep: 'step-03-design'
+lastContinued: '2025-01-02'
+date: '2025-01-01'
+---
+```
+
+**Step tracking:** Each step appends its NAME to `stepsCompleted`.
+
+---
+
+## Validation Checklist
+
+For EVERY step frontmatter, verify:
+
+- [ ] `name` present, kebab-case format
+- [ ] `description` present
+- [ ] Extract ALL variable names from frontmatter
+- [ ] For EACH variable, search body: is `{variableName}` present?
+- [ ] If variable NOT in body → ❌ VIOLATION, remove from frontmatter
+- [ ] All step-to-step paths use `./filename.md` format
+- [ ] All parent-folder paths use `../filename.md` format
+- [ ] All subfolder paths use `./subfolder/filename.md` format
+- [ ] NO `{workflow_path}` variable exists
+- [ ] External paths use `{project-root}` variable
+- [ ] Module variables only used if workflow belongs to that module

package/src/bmb/workflows/workflow/data/input-discovery-standards.md

@@ -0,0 +1,191 @@
+# Input Document Discovery Standards
+
+**Purpose:** Workflow input discovery, validation, and selection from prior workflows or external sources.
+
+---
+
+## Discovery Patterns
+
+1. **Prior Workflow Output** - Sequential workflows (e.g., PRD → Architecture → Epics)
+2. **Module Folder Search** - Known project locations
+3. **User-Specified Paths** - User-provided document locations
+4. **Pattern-Based Discovery** - File naming pattern matching (e.g., `*-brief.md`)
+
+---
+
+## Discovery Step Pattern
+
+**When:** Step 1 (init) or Step 2 (discovery)
+
+**Frontmatter:**
+```yaml
+---
+# Input discovery variables
+inputDocuments: []           # Discovered docs
+requiredInputCount: 1         # Minimum required
+optionalInputCount: 0        # Additional optional docs
+moduleInputFolder: '{planning_artifacts}'
+inputFilePatterns:
+  - '*-prd.md'
+  - '*-ux.md'
+---
+```
+
+**Discovery Logic:**
+```markdown
+## 1. Check Known Prior Workflow Outputs
+Search order:
+1. {module_output_folder}/[known-prior-workflow-output].md
+2. {project_folder}/[standard-locations]/
+3. {planning_artifacts}/
+4. User-provided paths
+
+## 2. Pattern-Based Search
+If no known prior workflow: match {inputFilePatterns} in {moduleInputFolder} and {project_folder}/docs/
+
+## 3. Present Findings
+"Found these documents:
+- [1] prd-my-project.md (3 days ago)
+- [2] ux-research.md (1 week ago)
+
+Select multiple or provide additional paths."
+
+## 4. Confirm and Load
+Add selections to {inputDocuments} array in output frontmatter
+```
+
+---
+
+## Required vs Optional Inputs
+
+**Required:** Workflow cannot proceed without these.
+```markdown
+## INPUT REQUIREMENT:
+Requires PRD to proceed.
+
+Searching: {bmm_creations_output_folder}/prd-*.md, {planning_artifacts}/*-prd.md
+
+[Found:] "Found PRD: prd-my-project.md. Use this?"
+[Missing:] "No PRD found. Run PRD workflow first or provide path."
+```
+
+**Optional:** Workflow can proceed without these.
+```markdown
+## OPTIONAL INPUTS:
+Can incorporate research if available.
+
+Searching: {bmm_creations_output_folder}/research-*.md, {project_folder}/research/
+
+[Found:] "Found research documents. Include any? (None required)"
+```
+
+---
+
+## Module Workflow Chaining
+
+**Frontmatter in workflow.md:**
+```yaml
+---
+## INPUT FROM PRIOR WORKFLOWS
+
+### Required Inputs:
+- {module_output_folder}/prd-{project_name}.md
+
+### Optional Inputs:
+- {module_output_folder}/ux-research-{project_name}.md
+---
+```
+
+**Step 1 discovery:**
+```markdown
+## 1. Discover Prior Workflow Outputs
+
+Check required: {module_output_folder}/prd-{project_name}.md
+- Missing → Error: "Run PRD workflow first"
+- Found → Confirm with user
+
+Check optional: Search for patterns, present findings, add selections to {inputDocuments}
+```
+
+---
+
+## Input Validation
+
+```markdown
+## INPUT VALIDATION:
+
+For each discovered document:
+1. Load frontmatter
+2. Check workflowType matches expected
+3. Check stepsCompleted == complete
+4. Check date (warn if old)
+
+[Fail:] "Document appears incomplete. Last step: step-06 (of 11). Proceed anyway?"
+```
+
+---
+
+## Multiple Input Selection
+
+```markdown
+## Document Selection
+
+"Found relevant documents:
+[1] prd-my-project.md (3 days ago) ✓ Recommended
+[2] prd-v1.md (2 months ago) ⚠ Older
+
+Enter numbers (comma-separated): > 1, 3"
+```
+
+**Track in frontmatter:**
+```yaml
+---
+inputDocuments:
+  - path: '{output_folder}/prd-my-project.md'
+    type: 'prd'
+    source: 'prior-workflow'
+    selected: true
+---
+```
+
+---
+
+## Search Path Variables
+
+| Variable                 | Purpose                    |
+| ------------------------ | -------------------------- |
+| `{module_output_folder}` | Prior workflow outputs     |
+| `{planning_artifacts}`   | General planning docs      |
+| `{project_folder}/docs`  | Project documentation      |
+| `{product_knowledge}`    | Product-specific knowledge |
+| `{user_documents}`       | User-provided location     |
+
+---
+
+## Discovery Step Template
+
+```markdown
+---
+name: 'step-01-init'
+description: 'Initialize and discover input documents'
+
+# Input Discovery
+inputDocuments: []
+requiredInputCount: 1
+moduleInputFolder: '{module_output_folder}'
+inputFilePatterns:
+  - '*-prd.md'
+---
+```
+
+---
+
+## Validation Checklist
+
+- [ ] Required inputs defined in step frontmatter
+- [ ] Search paths defined (module variables or patterns)
+- [ ] User confirmation before using documents
+- [ ] Validation of document completeness
+- [ ] Clear error messages when required inputs missing
+- [ ] Support for multiple document selection
+- [ ] Optional inputs clearly marked

package/src/bmb/workflows/workflow/data/intent-vs-prescriptive-spectrum.md

@@ -0,0 +1,44 @@
+# Intent vs Prescriptive Spectrum
+
+**Principle:** Workflows lean toward **intent** (goals) not **prescription** (exact wording). The more intent-based, the more adaptive and creative the LLM can be.
+
+## When to Use Each
+
+### Intent-Based (Default)
+**Use for:** Most workflows - creative, exploratory, collaborative
+**Step instruction:** "Help the user understand X using multi-turn conversation. Probe to get good answers. Ask 1-2 questions at a time, not a laundry list."
+**LLM figures out:** Exact wording, question order, how to respond
+
+### Prescriptive (Exception)
+**Use for:** Compliance, safety, legal, medical, regulated industries
+**Step instruction:** "Say exactly: 'Do you currently experience fever, cough, or fatigue?' Wait for response. Then ask exactly: 'When did symptoms begin?'"
+**LLM follows:** Exact script, specific order, no deviation
+
+## Examples
+
+### Intent-Based (Good for most)
+```
+"Guide the user through discovering their ideal nutrition plan.
+Use multi-turn conversation. Ask 1-2 questions at a time.
+Think about their responses before asking follow-ups.
+Probe to understand preferences, restrictions, goals."
+```
+
+### Prescriptive (Only when required)
+```
+"Medical intake - ask exactly:
+1. 'Do you have any of these symptoms: fever, cough, fatigue?'
+2. 'When did symptoms begin?'
+3. 'Have you traveled recently in the last 14 days?'
+Follow sequence precisely. Do not deviate."
+```
+
+## Step Writing Tips
+
+- **Default to intent** - give goals, not scripts
+- **Use "think"** - "Think about their response before..."
+- **Multi-turn** - "Use conversation, not interrogation"
+- **Progressive** - "Ask 1-2 questions at a time"
+- **Probe** - "Ask follow-ups to understand deeper"
+
+Only use prescriptive when compliance/regulation requires it.

package/src/bmb/workflows/workflow/data/menu-handling-standards.md

@@ -0,0 +1,133 @@
+# Menu Handling Standards
+
+**CRITICAL:** Every menu MUST have a handler section. No exceptions.
+
+## Reserved Letters
+
+| Letter | Purpose              | After Execution                |
+| ------ | -------------------- | ------------------------------ |
+| **A**  | Advanced Elicitation | Redisplay menu                |
+| **P**  | Party Mode           | Redisplay menu                |
+| **C**  | Continue/Accept      | Save → update → load next step |
+| **X**  | Exit/Cancel          | End workflow                  |
+
+**Custom letters** allowed (L/R/F/etc.) but don't conflict with reserved.
+
+## Required Structure
+
+### Section 1: Display
+```markdown
+### N. Present MENU OPTIONS
+Display: "**Select:** [A] [action] [P] [action] [C] Continue"
+```
+
+### Section 2: Handler (MANDATORY)
+```markdown
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user, then [Redisplay Menu Options](#n-present-menu-options)
+```
+
+### Section 3: Execution Rules
+```markdown
+#### 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
+```
+
+## When To Include A/P
+
+**DON'T Include A/P:** Step 1 (init), Step 2 if only loading documents, validation sequences, simple data gathering
+
+**DO Include A/P:** Collaborative content creation, user might want alternatives, quality gate before proceeding, creative exploration valuable
+
+## Menu Patterns
+
+### Pattern 1: Standard A/P/C
+```markdown
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
+- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user, then [Redisplay Menu Options](#n-present-menu-options)
+
+#### 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
+```
+
+### Pattern 2: C Only (No A/P)
+```markdown
+Display: "**Select:** [C] Continue"
+
+#### Menu Handling Logic:
+- IF C: Save content to {outputFile}, update frontmatter, then load, read entire file, then execute {nextStepFile}
+- IF Any other: help user, then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+```
+
+**Use for:** Step 1, document discovery, simple progression
+
+### Pattern 3: Auto-Proceed (No Menu)
+```markdown
+Display: "**Proceeding to [next step]...**"
+
+#### Menu Handling Logic:
+- After [completion condition], immediately load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- This is an [auto-proceed reason] step with no user choices
+- Proceed directly to next step after setup
+```
+
+**Use for:** Init steps, validation sequences
+
+### Pattern 4: Branching
+```markdown
+Display: "**Select:** [L] Load Existing [N] Create New [C] Continue"
+
+#### Menu Handling Logic:
+- IF L: Load existing document, then load, read entire file, then execute {stepForExisting}
+- IF N: Create new document, then load, read entire file, then execute {stepForNew}
+- IF C: Save content to {outputFile}, update frontmatter, check {condition}, then load appropriate step
+- IF Any other: help user, then [Redisplay Menu Options](#n-present-menu-options)
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- Branching options load different steps based on user choice
+```
+
+## Critical Rules
+
+### ❌ DON'T:
+- Omit handler section after Display
+- Include A/P in Step 1 (no content to refine)
+- Forget "redisplay menu" for non-C options
+- Miss "halt and wait" in EXECUTION RULES
+
+### ✅ DO:
+- Handler section immediately follows Display
+- "Halt and wait" in EXECUTION RULES
+- Non-C options specify "redisplay menu"
+- A/P only when appropriate for step type
+
+## Validation Checklist
+
+For every menu:
+- [ ] Display section present
+- [ ] Handler section immediately follows
+- [ ] EXECUTION RULES section present
+- [ ] "Halt and wait" instruction included
+- [ ] A/P options appropriate for step type
+- [ ] Non-C options redisplay menu
+- [ ] C option: save → update → load next
+- [ ] All file references use variables