ros/BMAD-METHOD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: clarified contributions and guiding principles to align ideals for contribution to BMad Method

Browse Source
This commit is contained in:
Brian Madison
2025-06-22 22:08:21 -05:00
parent c19772498a
commit febe7e149d
7 changed files with 689 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
expansion-packs/expansion-creator/tasks/generate-expansion-pack.md
View File

@@ -18,7 +18,7 @@ Every expansion pack MUST include a custom BMAD orchestrator agent with sophisti
1. **Create Planning Document First**: Before any implementation, create a comprehensive plan for user approval
2. **Agent Architecture Standards**: Use YAML-in-Markdown structure with activation instructions, personas, and command systems
3. **Character Consistency**: Every agent must have a persistent persona with name, communication style, and numbered options protocol
3. **Character Consistency**: Every agent must have a persistent persona with name, communication style, and numbered options protocol similar to `expansion-packs/bmad-2d-phaser-game-dev/agents/game-designer.md`
4. **Custom Themed Orchestrator**: The orchestrator should embody the domain theme (e.g., Office Manager for medical, Project Lead for tech) for better user experience
5. **Core Utilities Required**: ALWAYS include these core files in every expansion pack:
- `tasks/create-doc.md` - Document creation from templates
@@ -26,8 +26,8 @@ Every expansion pack MUST include a custom BMAD orchestrator agent with sophisti
- `utils/template-format.md` - Template markup conventions
- `utils/workflow-management.md` - Workflow orchestration
6. **Team and Workflow Requirements**: If pack has >1 agent, MUST include:
- At least one team configuration in `agent-teams/`
- At least one workflow in `workflows/`
- At least one team configuration in `expansion-packs/{new-expansion}/agent-teams/`
- At least one workflow in `expansion-packs/{new-expansion}workflows/`
7. **Template Sophistication**: Implement LLM instruction embedding with `[[LLM: guidance]]`, conditional content, and variable systems
8. **Workflow Orchestration**: Include decision trees, handoff protocols, and validation loops
9. **Quality Assurance Integration**: Multi-level checklists with star ratings and ready/not-ready frameworks
@@ -1018,11 +1018,3 @@ Embedded knowledge (automatic):
- [ ] Template conditional content tested with different scenarios
- [ ] Workflow decision trees validated with sample use cases
- [ ] Character interactions tested for consistency and professional authenticity
```
```
```
```