bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.14

package/src/core/workflows/party-mode/instructions.md

@@ -1,183 +0,0 @@
-# Party Mode - Multi-Agent Discussion Instructions
-
-<critical>The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml</critical>
-<critical>This workflow orchestrates group discussions between all installed BMAD agents</critical>
-
-<workflow>
-
-<step n="1" goal="Load Agent Manifest and Configurations">
-  <action>Load the agent manifest CSV from {{agent_manifest}}</action>
-  <action>Parse CSV to extract all agent entries with their condensed information:</action>
-    - name (agent identifier)
-    - displayName (agent's persona name)
-    - title (formal position)
-    - icon (visual identifier)
-    - role (capabilities summary)
-    - identity (background/expertise)
-    - communicationStyle (how they communicate)
-    - principles (decision-making philosophy)
-    - module (source module)
-    - path (file location)
-
-<action>Build complete agent roster with merged personalities</action>
-<action>Store agent data for use in conversation orchestration</action>
-</step>
-
-<step n="2" goal="Initialize Party Mode">
-  <action>Announce party mode activation with enthusiasm</action>
-  <action>List all participating agents with their merged information:</action>
-  <format>
-    🎉 PARTY MODE ACTIVATED! 🎉
-    All agents are here for a group discussion!
-
-    Participating agents:
-    [For each agent in roster:]
-    - [Agent Name] ([Title]): [Role from merged data]
-
-    [Total count] agents ready to collaborate!
-
-    What would you like to discuss with the team?
-
-  </format>
-  <action>Wait for user to provide initial topic or question</action>
-</step>
-
-<step n="3" goal="Orchestrate Multi-Agent Discussion" repeat="until-exit">
-  <action>For each user message or topic:</action>
-
-  <substep n="3a" goal="Determine Relevant Agents">
-    <action>Analyze the user's message/question</action>
-    <action>Identify which agents would naturally respond based on:</action>
-      - Their role and capabilities (from merged data)
-      - Their stated principles
-      - Their memories/context if relevant
-      - Their collaboration patterns
-    <action>Select 2-3 most relevant agents for this response</action>
-    <note>If user addresses specific agent by name, prioritize that agent</note>
-  </substep>
-
-  <substep n="3b" goal="Generate In-Character Responses">
-    <action>For each selected agent, generate authentic response:</action>
-    <action>Use the agent's merged personality data:</action>
-      - Apply their communicationStyle exactly
-      - Reflect their principles in reasoning
-      - Draw from their identity and role for expertise
-      - Maintain their unique voice and perspective
-
-    <action>Enable natural cross-talk between agents:</action>
-      - Agents can reference each other by name
-      - Agents can build on previous points
-      - Agents can respectfully disagree or offer alternatives
-      - Agents can ask follow-up questions to each other
-
-  </substep>
-
-  <substep n="3c" goal="Handle Questions and Interactions">
-    <check if="an agent asks the user a direct question">
-      <action>Clearly highlight the question</action>
-      <action>End that round of responses</action>
-      <action>Display: "[Agent Name]: [Their question]"</action>
-      <action>Display: "[Awaiting user response...]"</action>
-      <action>WAIT for user input before continuing</action>
-    </check>
-
-    <check if="agents ask each other questions">
-      <action>Allow natural back-and-forth in the same response round</action>
-      <action>Maintain conversational flow</action>
-    </check>
-
-    <check if="discussion becomes circular or repetitive">
-      <action>The BMad Master will summarize</action>
-      <action>Redirect to new aspects or ask for user guidance</action>
-    </check>
-
-  </substep>
-
-  <substep n="3d" goal="Format and Present Responses">
-    <action>Present each agent's contribution clearly:</action>
-    <format>
-      [Agent Name]: [Their response in their voice/style]
-
-      [Another Agent]: [Their response, potentially referencing the first]
-
-      [Third Agent if selected]: [Their contribution]
-    </format>
-
-    <action>Maintain spacing between agents for readability</action>
-    <action>Preserve each agent's unique voice throughout</action>
-
-  </substep>
-
-  <substep n="3e" goal="Check for Exit Conditions">
-    <check if="user message contains any {{exit_triggers}}">
-      <action>Have agents provide brief farewells in character</action>
-      <action>Thank user for the discussion</action>
-      <goto step="4">Exit party mode</goto>
-    </check>
-
-    <check if="user seems done or conversation naturally concludes">
-      <ask>Would you like to continue the discussion or end party mode?</ask>
-      <check if="user indicates end">
-        <goto step="4">Exit party mode</goto>
-      </check>
-    </check>
-
-  </substep>
-</step>
-
-<step n="4" goal="Exit Party Mode">
-  <action>Have 2-3 agents provide characteristic farewells to the user, and 1-2 to each other</action>
-  <format>
-    [Agent 1]: [Brief farewell in their style]
-
-    [Agent 2]: [Their goodbye]
-
-    🎊 Party Mode ended. Thanks for the great discussion!
-
-  </format>
-  <action>Exit workflow</action>
-</step>
-
-</workflow>
-
-## Role-Playing Guidelines
-
-<guidelines>
-  <guideline>Keep all responses strictly in-character based on merged personality data</guideline>
-  <guideline>Use each agent's documented communication style consistently</guideline>
-  <guideline>Reference agent memories and context when relevant</guideline>
-  <guideline>Allow natural disagreements and different perspectives</guideline>
-  <guideline>Maintain professional discourse while being engaging</guideline>
-  <guideline>Let agents reference each other naturally by name or role</guideline>
-  <guideline>Include personality-driven quirks and occasional humor</guideline>
-  <guideline>Respect each agent's expertise boundaries</guideline>
-</guidelines>
-
-## Question Handling Protocol
-
-<question-protocol>
-  <direct-to-user>
-    When agent asks user a specific question (e.g., "What's your budget?"):
-    - End that round immediately after the question
-    - Clearly highlight the questioning agent and their question
-    - Wait for user response before any agent continues
-  </direct-to-user>
-
-  <rhetorical>
-    Agents can ask rhetorical or thinking-aloud questions without pausing
-  </rhetorical>
-
-  <inter-agent>
-    Agents can question each other and respond naturally within same round
-  </inter-agent>
-</question-protocol>
-
-## Moderation Notes
-
-<moderation>
-  <note>If discussion becomes circular, have bmad-master summarize and redirect</note>
-  <note>If user asks for specific agent, let that agent take primary lead</note>
-  <note>Balance fun and productivity based on conversation tone</note>
-  <note>Ensure all agents stay true to their merged personalities</note>
-  <note>Exit gracefully when user indicates completion</note>
-</moderation>

package/src/core/workflows/party-mode/workflow.yaml

@@ -1,28 +0,0 @@
-# Party Mode - Multi-Agent Group Discussion Workflow
-name: "party-mode"
-description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-author: "BMad"
-
-# Critical data sources - manifest and config overrides
-agent_manifest: "{project-root}/{bmad_folder}/_cfg/agent-manifest.csv"
-date: system-generated
-
-# This is an interactive action workflow - no template output
-template: false
-instructions: "{project-root}/{bmad_folder}/core/workflows/party-mode/instructions.md"
-
-# Exit conditions
-exit_triggers:
-  - "*exit"
-
-standalone: true
-
-web_bundle:
-  name: "party-mode"
-  description: "Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations"
-  author: "BMad"
-  instructions: "{bmad_folder}/core/workflows/party-mode/instructions.md"
-  agent_manifest: "{bmad_folder}/_cfg/agent-manifest.csv"
-  web_bundle_files:
-    - "{bmad_folder}/core/workflows/party-mode/instructions.md"
-    - "{bmad_folder}/_cfg/agent-manifest.csv"

package/src/modules/bmb/workflows/audit-workflow/checklist.md

@@ -1,142 +0,0 @@
-# Audit Workflow - Validation Checklist
-
-## Structure
-
-- [ ] workflow.yaml file loads without YAML syntax errors
-- [ ] instructions.md file exists and is properly formatted
-- [ ] template.md file exists (if document workflow) with valid markdown
-- [ ] All critical headers present in instructions (workflow engine reference, workflow.yaml reference)
-- [ ] Workflow type correctly identified (document/action/interactive/autonomous/meta)
-- [ ] All referenced files actually exist at specified paths
-- [ ] No placeholder text remains (like {TITLE}, {WORKFLOW_CODE}, TODO, etc.)
-
-## Standard Config Block
-
-- [ ] workflow.yaml contains `config_source` pointing to correct module config
-- [ ] `output_folder` pulls from `{config_source}:output_folder`
-- [ ] `user_name` pulls from `{config_source}:user_name`
-- [ ] `communication_language` pulls from `{config_source}:communication_language`
-- [ ] `date` is set to `system-generated`
-- [ ] Config source uses {project-root} variable (not hardcoded path)
-- [ ] Standard config comment present: "Critical variables from config"
-
-## Config Variable Usage
-
-- [ ] Instructions communicate in {communication_language} where appropriate
-- [ ] Instructions address {user_name} in greetings or summaries where appropriate
-- [ ] All file outputs write to {output_folder} or subdirectories (no hardcoded paths)
-- [ ] Template includes {{user_name}} in metadata (optional for document workflows)
-- [ ] Template includes {{date}} in metadata (optional for document workflows)
-- [ ] Template does NOT use {{communication_language}} in headers (agent-only variable)
-- [ ] No hardcoded language-specific text that should use {communication_language}
-- [ ] Date used for agent date awareness (not confused with training cutoff)
-
-## YAML/Instruction/Template Alignment
-
-- [ ] Every workflow.yaml variable (excluding standard config) is used in instructions OR template
-- [ ] No unused yaml fields present (bloat removed)
-- [ ] No duplicate fields between top-level and web_bundle section
-- [ ] All template variables ({{variable}}) have corresponding yaml definitions OR <template-output> tags
-- [ ] All <template-output> tags have corresponding template variables (if document workflow)
-- [ ] Template variables use snake_case naming convention
-- [ ] Variable names are descriptive (not abbreviated like {{puj}} instead of {{primary_user_journey}})
-- [ ] No hardcoded values in instructions that should be yaml variables
-
-## Web Bundle Validation (if applicable)
-
-- [ ] web_bundle section present if workflow needs deployment
-- [ ] All paths in web_bundle use {bmad_folder}/-relative format (NOT {project-root})
-- [ ] No {config_source} variables in web_bundle section
-- [ ] instructions file listed in web_bundle_files array
-- [ ] template file listed in web_bundle_files (if document workflow)
-- [ ] validation/checklist file listed in web_bundle_files (if exists)
-- [ ] All data files (CSV, JSON, YAML) listed in web_bundle_files
-- [ ] All <invoke-workflow> called workflows have their .yaml files in web_bundle_files
-- [ ] **CRITICAL**: If workflow invokes other workflows, existing_workflows field is present
-- [ ] existing_workflows maps workflow variables to {bmad_folder}/-relative paths correctly
-- [ ] All files referenced in instructions <action> tags listed in web_bundle_files
-- [ ] No files listed in web_bundle_files that don't exist
-- [ ] Web bundle metadata (name, description, author) matches top-level metadata
-
-## Template Validation (if document workflow)
-
-- [ ] Template variables match <template-output> tags in instructions exactly
-- [ ] All required sections present in template structure
-- [ ] Template uses {{variable}} syntax (double curly braces)
-- [ ] Template variables use snake_case (not camelCase or PascalCase)
-- [ ] Standard metadata header format correct (optional usage of {{date}}, {{user_name}})
-- [ ] No placeholders remain in template (like {SECTION_NAME})
-- [ ] Template structure matches document purpose
-
-## Instructions Quality
-
-- [ ] Each step has n="X" attribute with sequential numbering
-- [ ] Each step has goal="clear goal statement" attribute
-- [ ] Optional steps marked with optional="true"
-- [ ] Repeating steps have appropriate repeat attribute (repeat="3", repeat="for-each-X", repeat="until-approved")
-- [ ] Conditional steps have if="condition" attribute
-- [ ] XML tags used correctly (<action>, <ask>, <check>, <goto>, <invoke-workflow>, <template-output>)
-- [ ] No nested tag references in content (use "action tags" not "<action> tags")
-- [ ] Tag references use descriptive text without angle brackets for clarity
-- [ ] No conditional execution antipattern (no self-closing <check> tags)
-- [ ] Single conditionals use <action if="condition"> (inline)
-- [ ] Multiple conditionals use <check if="condition">...</check> (wrapper block with closing tag)
-- [ ] Steps are focused (single goal per step)
-- [ ] Instructions are specific with limits ("Write 1-2 paragraphs" not "Write about")
-- [ ] Examples provided where helpful
-- [ ] <template-output> tags save checkpoints for document workflows
-- [ ] Flow control is logical and clear
-
-## Bloat Detection
-
-- [ ] Bloat percentage under 10% (unused yaml fields / total fields)
-- [ ] No commented-out variables that should be removed
-- [ ] No duplicate metadata between sections
-- [ ] No variables defined but never referenced
-- [ ] No redundant configuration that duplicates web_bundle
-
-## Final Validation
-
-### Critical Issues (Must fix immediately)
-
-_List any critical issues found:_
-
-- Issue 1:
-- Issue 2:
-- Issue 3:
-
-### Important Issues (Should fix soon)
-
-_List any important issues found:_
-
-- Issue 1:
-- Issue 2:
-- Issue 3:
-
-### Cleanup Recommendations (Nice to have)
-
-_List any cleanup recommendations:_
-
-- Recommendation 1:
-- Recommendation 2:
-- Recommendation 3:
-
----
-
-## Audit Summary
-
-**Total Checks:**
-**Passed:** {total}
-**Failed:** {total}
-
-**Recommendation:**
-
-- Pass Rate ≥ 95%: Excellent - Ready for production
-- Pass Rate 85-94%: Good - Minor fixes needed
-- Pass Rate 70-84%: Fair - Important issues to address
-- Pass Rate < 70%: Poor - Significant work required
-
----
-
-**Audit Completed:** {{date}}
-**Auditor:** Audit Workflow (BMAD v6)