hash file change checking integrated

This commit is contained in:
Brian Madison
2025-09-30 21:20:13 -05:00
parent c42cd48421
commit 05a3b4f3f1
316 changed files with 354 additions and 38125 deletions

View File

@@ -1,79 +0,0 @@
# BMAD Init - System Initialization Instructions
<workflow>
<step n="1" goal="Welcome and Status Check">
<action>Display welcome banner with BMAD branding</action>
<action>Check for BMAD installation at {project-root}/bmad</action>
<check>If installation found:</check>
<action>Display current version from {project-root}/bmad/_cfg/manifest.yaml</action>
<action>Show installation date and status</action>
<check>If not found:</check>
<action>Display warning that BMAD is not installed</action>
<action>Suggest running the installer first</action>
<action>Exit workflow</action>
<action>Display formatted status summary:
╔════════════════════════════════════════╗
║ BMAD INITIALIZATION ║
╚════════════════════════════════════════╝
Status: [Installed/Not Found]
Location: {project-root}/bmad
Version: [from manifest]
Installed: [date from manifest]
</action>
</step>
<step n="2" goal="Present Initialization Options">
<action>Display available initialization and maintenance tasks</action>
<ask>Select an initialization task:
1. Customize Installed Agents and Agent Party (Coming Soon)
- Assign new names and personas to agents
- Create runtime agent variants
- NOTE: This can all be done manually, but doing it through here will be easier and also update the party-mode manifest
2. Verify Installation (Coming Soon)
- Check all files are properly installed
- Validate configurations
3. Exit
Please select an option (1-3).
</ask>
</step>
<step n="3" goal="Process User Selection">
<check>If user selected "1":</check>
<action>Display message: ⚠️ Installed Agent Auto Customization is coming soon.</action>
<<action>Return to step 2</action>
<check>If user selected "2":</check>
<action>Display message: ⚠️ Installation verification is coming soon.</action>
<action>Return to step 2</action>
<check>If user selected "3":</check>
<action>Display message: Exiting BMAD Init. Thank you!</action>
<goto step="5">Exit workflow</goto>
</step>
<step n="4" goal="Post-Task Options">
<action>Display completion status of the executed task</action>
<ask>Task completed successfully!
Would you like to perform another initialization task? (y/n):</ask>
<check>If user responds "y":</check>
<goto step="2">Return to menu</goto>
<check>If user responds "n":</check>
<goto step="5">Exit workflow</goto>
</step>
<step n="5" goal="Exit Workflow">
<action>Display farewell message</action>
<action>Suggest user start a new context or clear context if needed</action>
<action>Exit workflow</action>
</step>
</workflow>

View File

@@ -1,14 +0,0 @@
# BMAD Init - System Initialization Workflow
name: "bmad-init"
description: "BMAD system initialization and maintenance workflow for agent manifest generation and system configuration"
author: "BMad"
# Critical variables
config_source: "{project-root}/bmad/_cfg/manifest.yaml"
date: system-generated
# This is an action workflow - no template output
template: false
instructions: "{project-root}/src/core/workflows/bmad-init/instructions.md"
web_bundle: false

View File

@@ -1,181 +0,0 @@
# Party Mode - Multi-Agent Discussion Instructions
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</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 from {{manifest}}</action>
<action>Parse XML to extract all agent entries with their condensed information:</action>
- id (file path)
- name
- title
- role (single sentence with capabilities)
- style (communication style)
- principles
- memories (if present)
- collaborators (key collaborators if any)
<action>For each agent found in manifest:</action>
<check>Look for config override at {{agent_configs}}[module]-[agent-name].md</check>
<check>If config override exists:</check>
<action>Load the override configuration</action>
<action>MERGE override data with manifest data (overrides take precedence):</action> - Override role replaces manifest role if present - Override style replaces manifest style if present - Override principles replace manifest principles if present - Override memories replace or append to manifest memories - Any additional persona elements from override are added
<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 communication style exactly
- Reflect their principles in reasoning
- Reference their memories if contextually relevant
- 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:</check>
<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>If agents ask each other questions:</check>
<action>Allow natural back-and-forth in the same response round</action>
<action>Maintain conversational flow</action>
<check>If discussion becomes circular or repetitive:</check>
<action>The BMad Master will summarize</action>
<action>Redirect to new aspects or ask for user guidance</action>
</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}}:</check>
<action>Have agents provide brief farewells in character</action>
<action>Thank user for the discussion</action>
<goto step="4">Exit party mode</goto>
<check>If user seems done or conversation naturally concludes:</check>
<ask>Would you like to continue the discussion or end party mode?</ask>
<check>If user indicates end:</check>
<goto step="4">Exit party mode</goto>
</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>

View File

@@ -1,26 +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
manifest: "{project-root}/bmad/_cfg/agent-party.xml"
agent_configs: "{project-root}/bmad/_cfg/agents/"
date: system-generated
# This is an interactive action workflow - no template output
template: false
instructions: "{project-root}/src/core/workflows/party-mode/instructions.md"
# Data files to be loaded at runtime
data_files:
- agent_manifest: "{project-root}/bmad/_cfg/agent-party.xml"
- agent_overrides: "{project-root}/bmad/_cfg/agents/*.md"
# Exit conditions
exit_triggers:
- "*exit"
- "end party mode"
- "stop party mode"
web_bundle: false