mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
138 lines
4.9 KiB
Markdown
138 lines
4.9 KiB
Markdown
# Module Brainstorming Context
|
|
|
|
_Context provided to brainstorming workflow when creating a new BMAD module_
|
|
|
|
## Session Focus
|
|
|
|
You are brainstorming ideas for a **complete BMAD module** - a self-contained package that extends the BMAD Method with specialized domain expertise and capabilities.
|
|
|
|
## What is a BMAD Module?
|
|
|
|
A module is a cohesive package that provides:
|
|
|
|
- **Domain Expertise**: Specialized knowledge in a specific area (RPG, DevOps, Content Creation, etc.)
|
|
- **Agent Team**: Multiple AI personas with complementary skills
|
|
- **Workflows**: Guided processes for common tasks in the domain
|
|
- **Templates**: Document structures for consistent outputs
|
|
- **Integration**: Components that work together seamlessly
|
|
|
|
## Brainstorming Goals
|
|
|
|
Explore and define:
|
|
|
|
### 1. Domain and Purpose
|
|
|
|
- **What domain/problem space?** (e.g., game development, marketing, personal productivity)
|
|
- **Who is the target user?** (developers, writers, managers, hobbyists)
|
|
- **What pain points does it solve?** (tedious tasks, missing structure, need for expertise)
|
|
- **What makes this domain exciting?** (creativity, efficiency, empowerment)
|
|
|
|
### 2. Agent Team Composition
|
|
|
|
- **How many agents?** (typically 3-7 for a module)
|
|
- **What roles/personas?** (architect, researcher, reviewer, specialist)
|
|
- **How do they collaborate?** (handoffs, reviews, ensemble work)
|
|
- **What personality theme?** (Star Trek crew, superhero team, fantasy party, professional squad)
|
|
|
|
### 3. Core Workflows
|
|
|
|
- **What documents need creating?** (plans, specs, reports, creative outputs)
|
|
- **What processes need automation?** (analysis, generation, review, deployment)
|
|
- **What workflows enable the vision?** (3-10 key workflows that define the module)
|
|
|
|
### 4. Value Proposition
|
|
|
|
- **What becomes easier?** (specific tasks that get 10x faster)
|
|
- **What becomes possible?** (new capabilities previously unavailable)
|
|
- **What becomes better?** (quality improvements, consistency gains)
|
|
|
|
## Creative Constraints
|
|
|
|
A good BMAD module should be:
|
|
|
|
- **Focused**: Serves a specific domain well (not generic)
|
|
- **Complete**: Provides end-to-end capabilities for that domain
|
|
- **Cohesive**: Agents and workflows complement each other
|
|
- **Fun**: Personality and creativity make it enjoyable to use
|
|
- **Practical**: Solves real problems, delivers real value
|
|
|
|
## Module Architecture Questions
|
|
|
|
1. **Module Identity**
|
|
- Module code (kebab-case, e.g., "rpg-toolkit")
|
|
- Module name (friendly, e.g., "RPG Toolkit")
|
|
- Module purpose (one sentence)
|
|
- Target audience
|
|
|
|
2. **Agent Lineup**
|
|
- Agent names and roles
|
|
- Communication styles and personalities
|
|
- Expertise areas
|
|
- Command sets (what each agent can do)
|
|
|
|
3. **Workflow Portfolio**
|
|
- Document generation workflows
|
|
- Action/automation workflows
|
|
- Analysis/research workflows
|
|
- Creative/ideation workflows
|
|
|
|
4. **Integration Points**
|
|
- How agents invoke workflows
|
|
- How workflows use templates
|
|
- How components pass data
|
|
- Dependencies on other modules
|
|
|
|
## Example Module Patterns
|
|
|
|
### Professional Domains
|
|
|
|
- **DevOps Suite**: Deploy, Monitor, Troubleshoot agents + deployment workflows
|
|
- **Marketing Engine**: Content, SEO, Analytics agents + campaign workflows
|
|
- **Legal Assistant**: Contract, Research, Review agents + document workflows
|
|
|
|
### Creative Domains
|
|
|
|
- **RPG Toolkit**: DM, NPC, Quest agents + adventure creation workflows
|
|
- **Story Crafter**: Plot, Character, World agents + writing workflows
|
|
- **Music Producer**: Composer, Arranger, Mixer agents + production workflows
|
|
|
|
### Personal Domains
|
|
|
|
- **Life Coach**: Planner, Tracker, Mentor agents + productivity workflows
|
|
- **Learning Companion**: Tutor, Quiz, Reviewer agents + study workflows
|
|
- **Health Guide**: Nutrition, Fitness, Wellness agents + tracking workflows
|
|
|
|
## Suggested Brainstorming Techniques
|
|
|
|
Particularly effective for module ideation:
|
|
|
|
1. **Domain Immersion**: Deep dive into target domain's problems
|
|
2. **Persona Mapping**: Who needs this and what do they struggle with?
|
|
3. **Workflow Mapping**: What processes exist today? How could they improve?
|
|
4. **Team Building**: What personalities would make a great team?
|
|
5. **Integration Thinking**: How do pieces connect and amplify each other?
|
|
|
|
## Key Questions to Answer
|
|
|
|
1. What domain expertise should this module embody?
|
|
2. What would users be able to do that they can't do now?
|
|
3. Who are the 3-7 agents and what are their personalities?
|
|
4. What are the 5-10 core workflows?
|
|
5. What makes this module delightful to use?
|
|
6. How is this different from existing tools?
|
|
7. What's the "killer feature" that makes this essential?
|
|
|
|
## Output Goals
|
|
|
|
Generate:
|
|
|
|
- **Module concept**: Clear vision and purpose
|
|
- **Agent roster**: Names, roles, personalities for each agent
|
|
- **Workflow list**: Core workflows with brief descriptions
|
|
- **Unique angle**: What makes this module special
|
|
- **Use cases**: 3-5 concrete scenarios where this module shines
|
|
|
|
---
|
|
|
|
_This focused context helps create cohesive, valuable BMAD modules_
|