random updates

2025-06-15 19:46:32 -05:00
parent b2a0725002
commit d59aa191fc
14 changed files with 294 additions and 470 deletions
--- a/expansion-packs/README.md
+++ b/expansion-packs/README.md
@@ -2,112 +2,154 @@

 ## Overview

-Expansion packs extend BMAD Method with specialized capabilities for specific use cases. They allow teams to add functionality without cluttering the core workflow.
+Expansion packs are the future of BMAD-METHOD - specialized, standalone agent teams that extend the framework far beyond traditional software development. Each expansion pack is a complete, self-contained ecosystem of agents, templates, tasks, and knowledge bases designed for specific domains, industries, or use cases.

-## Core BMAD Flow
+## Vision: Beyond Software Development

-The original BMAD Method follows a simple, proven flow:
+While the core BMAD-METHOD focuses on software development workflows, expansion packs unlock the full potential of agentic frameworks by providing specialized capabilities for:

-````text
-Analyst → PM → Architect → SM → Dev
-(Brief) → (PRD) → (Architecture) → (Stories) → (Implementation)
-```text
+### Industry-Specific Applications
+- **Medical & Healthcare**: Clinical workflow optimization, patient care coordination, medical research
+- **Entertainment & Media**: Content creation, production workflows, creative project management
+- **Finance & Banking**: Risk analysis, compliance workflows, financial planning
+- **Legal Services**: Document review, case management, regulatory compliance
+- **Education**: Curriculum development, assessment design, learning experience optimization

-This core flow remains clean and focused on getting from business requirements to working software.
+### Technical Specializations
+- **Specific Tech Stacks**: Django+React, MEAN stack, Serverless AWS, etc.
+- **DevOps & Infrastructure**: Kubernetes orchestration, CI/CD pipelines, cloud architecture
+- **Data Engineering**: ETL pipelines, ML model deployment, data governance
+- **Cybersecurity**: Threat analysis, security auditing, incident response

-## Why Expansion Packs?
+### Creative & Interactive Applications
+- **Interactive Role-Playing**: Campaign management, character development, narrative design
+- **Game Development**: Level design, character creation, game mechanics
+- **Content Creation**: Video production, podcast workflows, social media management
+- **Design Systems**: Brand management, UI/UX workflows, design token systems

-As BMAD has evolved, we've identified specialized needs that don't fit every project:
+## Expansion Pack Architecture

- Infrastructure and DevOps workflows
- UX/UI design processes
- Data engineering pipelines
- Security and compliance workflows
- Mobile development patterns
- Real World assistance and workflows without AI Agents development in mind
-
-Rather than complicate the core method, expansion packs let you "opt-in" to additional capabilities.
-
-## Available Expansion Packs
-
-### 1. Infrastructure & DevOps
-
- **Purpose**: Cloud infrastructure design and platform engineering
- **Adds**: DevOps agent, infrastructure templates, validation checklists
- **Use When**: You need to design and implement cloud infrastructure
-
-### 2. UX/Design (Coming Soon)
-
- **Purpose**: User experience and interface design workflows
- **Adds**: Design Architect agent, UI component templates
- **Use When**: You need detailed UI/UX design processes
-
-### 3. Data Engineering (Planned)
-
- **Purpose**: Data pipeline and analytics infrastructure
- **Adds**: Data Engineer agent, ETL templates, data architecture patterns
- **Use When**: You're building data-intensive applications
-
-## Structure of an Expansion Pack
-
-Each expansion pack contains:
+Each expansion pack is a complete, standalone system that follows BMAD conventions:

 ```text
 expansion-pack-name/
-├── README.md           # Overview and usage instructions
-├── manifest.yml        # Installation configuration
-├── agents/            # Agent configurations (.yml)
-├── personas/          # Persona definitions (.md)
-├── ide-agents/        # IDE-specific agents (.ide.md)
-├── templates/         # Document templates (.md)
-├── tasks/            # Specialized tasks (.md)
-└── checklists/       # Validation checklists (.md)
-````
+├── README.md                 # Pack overview and usage instructions
+├── manifest.yml             # Pack metadata and configuration
+├── agents/                  # Specialized agent definitions
+│   ├── domain-expert.md
+│   ├── specialist-role.md
+│   └── coordinator.md
+├── templates/               # Domain-specific document templates
+│   ├── industry-doc.md
+│   └── workflow-spec.md
+├── tasks/                   # Specialized automation tasks
+│   ├── domain-process.md
+│   └── validation-check.md
+├── data/                    # Domain knowledge base
+│   ├── industry-kb.md
+│   ├── best-practices.md
+│   └── regulations.md
+├── checklists/             # Quality assurance checklists
+│   └── compliance-check.md
+├── workflows/              # Domain-specific workflows
+│   └── industry-process.yml
+└── team-config.yml         # Team bundle configuration
+```

-## Installing an Expansion Pack
+## Key Principles

-### Method 1: NPM Script
+### 1. Standalone Independence
+- Each expansion pack works independently of the core BMAD system
+- Can be used without any software development context
+- Complete with its own agents, knowledge, and workflows

-````bash
-npm run install:expansion <pack-name>
-```text
+### 2. Domain Expertise
+- Deep specialization in specific industries or use cases
+- Expert-level knowledge embedded in agents and templates
+- Industry-specific terminology, processes, and best practices

-### Method 2: Direct Script
+### 3. Consistent Framework
+- Follows BMAD architectural patterns and conventions
+- Compatible with existing tooling and build systems
+- Maintains quality and structure standards

-```bash
-node tools/install-expansion-pack.js <pack-name>
-````
+### 4. Flexible Application
+- Some packs may be technical, others completely non-technical
+- Scalable from single-agent specialists to complex multi-agent teams
+- Adaptable to different user environments (web UI, IDE, etc.)

-### Method 3: Manual
+## Example Expansion Packs

-1. Copy files according to manifest.yml
-2. Update team configurations as needed
-3. Rebuild bundles with `npm run build`
+### Medical Practice Management
+- **Agents**: Medical Director, Practice Manager, Compliance Officer, Patient Coordinator
+- **Templates**: Treatment protocols, compliance documentation, patient intake forms
+- **Workflows**: Patient onboarding, treatment planning, regulatory reporting
+- **Knowledge Base**: Medical regulations, best practices, industry standards

-## Creating Your Own Expansion Pack
+### Interactive Storytelling
+- **Agents**: Narrative Designer, Character Developer, World Builder, Campaign Master
+- **Templates**: Character sheets, world documentation, campaign notes
+- **Workflows**: Story development, character arcs, world building
+- **Knowledge Base**: Storytelling techniques, genre conventions, narrative structures

-1. Create a new folder under `expansion-packs/`
-2. Add your specialized agents, templates, and tasks
-3. Create a manifest.yml defining installation mappings
-4. Write a README explaining purpose and usage
-5. Test installation process
+### Fintech Compliance
+- **Agents**: Compliance Officer, Risk Analyst, Regulatory Expert, Audit Specialist
+- **Templates**: Compliance reports, risk assessments, audit documentation
+- **Workflows**: Regulatory review, compliance monitoring, audit preparation
+- **Knowledge Base**: Financial regulations, compliance frameworks, audit standards

-## Best Practices
+## Development Status

-1. **Keep Core Simple**: Don't add to core what could be an expansion
-2. **Clear Purpose**: Each pack should solve a specific need
-3. **Self-Contained**: Packs should work independently when possible
-4. **Document Well**: Clear README and usage examples
-5. **Version Compatibility**: Note which BMAD version the pack requires
+**Current Status**: Conceptual framework established, awaiting implementation
+
+**Roadmap**:
+1. **Phase 1**: Core expansion pack architecture and tooling
+2. **Phase 2**: First expansion packs (Medical, Entertainment, Interactive RPG)
+3. **Phase 3**: Community-contributed expansion packs
+4. **Phase 4**: Marketplace and distribution system
+
+## Creating Expansion Packs
+
+### Planning Your Pack
+1. **Define Domain**: Clear scope and target use case
+2. **Identify Roles**: What specialist agents are needed?
+3. **Map Workflows**: What processes need to be supported?
+4. **Gather Knowledge**: What domain expertise must be embedded?
+
+### Development Process
+1. **Pack Structure**: Follow the standard expansion pack architecture
+2. **Agent Development**: Create specialized agents with domain expertise
+3. **Template Creation**: Develop industry-specific document templates
+4. **Knowledge Integration**: Embed best practices and domain knowledge
+5. **Testing & Validation**: Ensure quality and effectiveness
+
+### Quality Standards
+- **Domain Accuracy**: Expert-level knowledge and terminology
+- **Practical Utility**: Solves real problems in the target domain
+- **User Experience**: Clear, intuitive interaction patterns
+- **Documentation**: Comprehensive usage guides and examples

 ## Future Vision

-We envision a library of expansion packs for various industries and use cases:
+Expansion packs will transform BMAD-METHOD from a software development framework into a universal agentic platform capable of supporting any specialized domain or industry. The goal is to create a rich ecosystem where experts can package their knowledge into reusable, intelligent agent teams.

- Healthcare compliance workflows
- Financial services security patterns
- E-commerce optimization flows
- Gaming development pipelines
- IoT device management
+**Long-term Goals**:
+- Hundreds of specialized expansion packs covering diverse domains
+- Community marketplace for sharing and distributing packs
+- Integration with industry-specific tools and platforms
+- AI-powered pack recommendations based on user needs

-The goal is to keep BMAD's core simple while allowing infinite extensibility through modular expansion packs.
+## Contributing
+
+**Note**: Expansion pack development is not yet available. This README documents the planned architecture and vision. Follow the project for updates on when expansion pack development will be open.
+
+**Future Contribution Areas**:
+- Domain expertise and knowledge base development
+- Specialized agent design and persona development
+- Industry-specific template and workflow creation
+- Testing and validation of expansion packs
+- Documentation and user experience improvements
+
+---
+
+*Expansion packs represent the next evolution of BMAD-METHOD - transforming it from a software development tool into a comprehensive agentic framework capable of supporting any specialized domain or workflow.*
--- a/expansion-packs/infrastructure-devops/tasks/create-doc.md
+++ b/expansion-packs/infrastructure-devops/tasks/create-doc.md
@@ -0,0 +1,74 @@
+# Create Document from Template Task
+
+## Purpose
+
+- Generate documents from any specified template following embedded instructions from the perspective of the selected agent persona
+
+## Instructions
+
+### 1. Identify Template and Context
+
+- Determine which template to use (user-provided or list available for selection to user)
+
+  - Agent-specific templates are listed in the agent's dependencies under `templates`. For each template listed, consider it a document the agent can create. So if an agent has:
+
+    @{example}
+    dependencies:
+    templates: - prd-tmpl - architecture-tmpl
+    @{/example}
+
+    You would offer to create "PRD" and "Architecture" documents when the user asks what you can help with.
+
+- Gather all relevant inputs, or ask for them, or else rely on user providing necessary details to complete the document
+- Understand the document purpose and target audience
+
+### 2. Determine Interaction Mode
+
+Confirm with the user their preferred interaction style:
+
+- **Incremental:** Work through chunks of the document.
+- **YOLO Mode:** Draft complete document making reasonable assumptions in one shot. (Can be entered also after starting incremental by just typing /yolo)
+
+### 3. Execute Template
+
+- Load specified template from `templates#*` or the /templates directory
+- Follow ALL embedded LLM instructions within the template
+- Process template markup according to `utils#template-format` conventions
+
+### 4. Template Processing Rules
+
+#### CRITICAL: Never display template markup, LLM instructions, or examples to users
+
+- Replace all {{placeholders}} with actual content
+- Execute all [[LLM: instructions]] internally
+- Process `<<REPEAT>>` sections as needed
+- Evaluate ^^CONDITION^^ blocks and include only if applicable
+- Use @{examples} for guidance but never output them
+
+### 5. Content Generation
+
+- **Incremental Mode**: Present each major section for review before proceeding
+- **YOLO Mode**: Generate all sections, then review complete document with user
+- Apply any elicitation protocols specified in template
+- Incorporate user feedback and iterate as needed
+
+### 6. Validation
+
+If template specifies a checklist:
+
+- Run the appropriate checklist against completed document
+- Document completion status for each item
+- Address any deficiencies found
+- Present validation summary to user
+
+### 7. Final Presentation
+
+- Present clean, formatted content only
+- Ensure all sections are complete
+- DO NOT truncate or summarize content
+- Begin directly with document content (no preamble)
+- Include any handoff prompts specified in template
+
+## Important Notes
+
+- Template markup is for AI processing only - never expose to users