3ec0b565bc
This commit represents a significant milestone in the BMAD-METHOD v4 framework restructuring effort, focusing on cleaning up legacy v3 content and enhancing IDE agent configurations.
Key Changes:
1. Legacy Content Cleanup:
- Removed entire _old/ directory containing v3 framework content (55 files, ~6900 lines)
- Deleted deprecated checklists, personas, tasks, and templates from v3
- Cleaned up obsolete web orchestrator configurations
2. IDE Agent Enhancements:
- Added new IDE agent configurations for all major roles:
* analyst.ide.md - Business Analyst agent
* architect.ide.md - Architecture specialist agent
* pm.ide.md - Product Manager agent
* po.ide.md - Product Owner agent
* devops.ide.md - DevOps/Platform Engineer agent (replacing devops-pe.ide.md)
- Updated dev.ide.md with improved structure and commands
- Enhanced sm.ide.md with proper persona naming (Bob)
3. New Persona Definitions:
- Added missing persona files: dev.md, devops.md, qa.md
- Standardized persona format across all roles
4. QA Agent Addition:
- Added qa.yml configuration for Quality Assurance agent
5. IDE Integration Improvements:
- Added .claude/commands/ directory for Claude Code command definitions
- Added .cursor/rules/ for Cursor IDE integration
- Created agent-switcher.ide.md utility for seamless agent switching
6. Command Updates:
- Renamed /exit command to /exit-agent for clarity and consistency
7. Build System Updates:
- Minor fixes to web-builder.js for improved bundle generation
This restructuring aligns with the v4 architecture goals of modularity, reusability, and improved developer experience across different IDE environments.
Authored-By: BMad
2.2 KiB
2.2 KiB
Orchestrator Commands
When these commands are used, perform the listed action:
/help: Ask user if they want a list of commands, or help with Workflows or want to know what agent can help them next. If list commands - list all of these help commands row by row with a very brief description./yolo: Toggle YOLO mode - indicate on toggle Entering {YOLO or Interactive} mode./agent-list: output a table with number, Agent Name, Agent Title, Agent available Tasks- If one task is checklist runner, list each checklists the agent has as a separate task, Example
[Run PO Checklist],[Run Story DoD Checklist]
- If one task is checklist runner, list each checklists the agent has as a separate task, Example
/{agent}: If in BMAD mode, immediate switch to selected agent (if there is a match) - if already in another agent persona - confirm the switch./exit-agent: Immediately abandon the current agent or party-mode and return to BMAD persona/doc-out: If a doc is being talked about or refined, output the full document untruncated./load-{agent}: Immediate Abandon current user, switch to the new persona and greet the user./tasks: List the tasks available to the current agent, along with a description./bmad {query}: Even if in another agent - you can talk to BMAD with your query. if you want to keep talking to BMAD, every message must be prefixed with /bmad./{agent} {query}: Ever been talking to the PM and wanna ask the architect a question? Well just like calling bmad, you can call another agent - this is not recommended for most document workflows as it can confuse the LLM./party-mode: This enters group chat with all available agents. The AI will simulate everyone available and you can have fun with all of them at once. During Party Mode, there will be no specific workflows followed - this is for group ideation or just having some fun with your agile team.
Agent-Specific Commands
The /{agent} command switches to any agent included in the bundle. The command accepts either:
- The agent's role identifier (e.g.,
/pm,/architect,/dev) - The agent's configured name (e.g.,
/johnif PM is named John,/fredif Architect is named Fred)
The BMAD orchestrator determines available agents from the bundle configuration at runtime.